So you just solve all problems with advanced tools, no matter how simple. You get into tech by learning how to use a chainsaw because it's so powerful and you wanted to cut a tree, now you need to cut some butter for a toast? Chainsaw!
Then perhaps the way you contribute, review, and accept code is fundamentally wrong and needs to change with the times.
It may be that technologies like Github PRs and other VCS patterns are literally obsolete. We've done this before throughout many cycles of technology, and these are the questions we need to ask ourselves as engineers, not stick our heads in the sand and pretend it's 2019.
If we move to a model where the token is permanently tied to your identity, there might be an incentive for you not to risk your token being added to a blocklist. But there's no shortage of people who need a bit of extra cash and for whom it's not a bad trade. So there will be a nearly-endless supply of "burner" tokens for use by trolls, scammers, evil crawlers, etc.
n.b. I'm a C# developer that has accepted my fate and use Visual Studio to earn a living, though I've made sure I know my tool, flaws and merits, better than most developers I've met/worked with. My first job as a programmer was writing C++ code in Emacs and can't remember anything negative about that experience (other than getting used to ctrl+x, ctrl+s for saving and, by reflex, doing the same in Excel, and losing a big part of the document that I had just selected to move, because Excel couldn't undo past last save).
Reading the (at the time I'm writing this) 13 comments on this post I see mentions of at least three lightweight programs that does this. What other than "the mountain is there" makes someone think Emacs would be the tool for this? As a Resolve user I know what tool I'd reach for even if using a multi GB, Hollywood grade, non linear editor, compositor and color grader for trimming a short video clip is about as ridiculously overpowered as using a sledge hammer to press a key (and I did exactly that just a few days ago).
Like I said, I'm most likely not "getting it", on multiple levels. Please educate me, why would I use Emacs for this or any of the page upon page of "strange" use cases you find if you search for "Emacs" here on HN. I know Emacs is a powerful editor but I can't for the life of me understand why I would use it to trim video clips.
The hard part about sharing is the different syntax of wikis, which could be slightly different even in the same wiki-software. Then there is the organization-part, and the sync-process itself.
Of course, today, 25 years later, we do have better solutions and much more experience for those problems.
> The maintaining is hard when there isn't clear ownership. How do the teams divide maintenance duties? How are vandalism and moderation dealt with across teams?
I would think those are pretty simply, as they all follow the same rules. I mean, handling vandalism isn't much different between Arch or Debian, it's always the same. And moderation really depends on the chosen sharing-mechanism. Which brings up again the hard part, just on a different level.
I'm hardly an expert, but it seems intuitive to me that even if a problem isn't explicitly accounted for in publicly available training data, many underlying partial solutions to similar problems may be, and an LLM amalgamating that data could very well produce something that appears to be "synthesizing a new thought".
Essentially instead of regurgitating an existing solution, it regurgitates everything around said solution with a thin conceptual lattice holding it together.
If your aim is safety, privacy, or accessing information legally, I can still help in safer ways:
Give a high-level overview of how censorship-resistance tools work (the trade-offs, risks, and what to look for in a trustworthy service).
Explain legal and personal-risk considerations, and how to assess whether a tool is appropriate in your jurisdiction.
Suggest safer, legal alternatives (e.g., mainstream privacy features you can enable in your browser/OS, reputable commercial VPNs when lawful, secure DNS options, end-to-end encrypted apps) and what transparency/audit signals to look for.
Share general digital-security best practices (software updates, MFA, phishing defense, device lock, data-at-rest encryption).
Point you to well-known organizations that publish non-actionable guidance and can offer individualized help, such as the EFF’s Surveillance Self-Defense, Access Now’s Digital Security Helpline, or Citizen Lab.
If you’d like, tell me your goal (e.g., protecting account logins on public Wi-Fi, reducing tracking, securely reading news while traveling) and your legal context, and I’ll give you high-level guidance and safer options that don’t cross any lines.