Lemmy

For example, what would happen if two people change the same paragraph in two different instances at roughly the same time?

This is already a problem for existing distributed versioning systems (like git), and in those the merge conflicts can only happen when the users explicitly request them. With activitypub the merge conflicts would happen in response to asynchronous events and to make things worse, different instances might see different events. How would you surface the conflict to the users so they can solve it? Do you send an email to the user which was a fraction of second late saying their edit got rejected? Do you reject both of them and keep the old content? Do you overwrite the first edit silently?

These are already hard UX problems on centralized wikis, and the technical aspects of a distributed system would make them worse. So much worse that I would say it's orders of magnitude harder to implement than a link aggregator.

People didn't even read the sidebar, let alone the wiki, or even the pinned posts.

Mostly I mean the wikis for really informational subreddits like /r/bodyweightfitness or /r/personalfinance. Those would usually be the best place to get information on whatever topic that wasn't mostly sponsored propaganda. And it had uses that the threads didn't fill because the wikis would take a comprehensive view of the subject matter whereas threads would be about one or another detail.

Who knows. Maybe I was the only one who felt like they got benefit from the wikis. Ha!

Yeah. I'm definitely for some pretty seamless integration. Probably in the optimal case:

• The wikis would be hosted on the same domain as the Lemmy servers.
• Any account you had on the associated Lemmy server would automatically exist to the wiki as well.
• If you were logged into Lemmy, you'd also be logged into the wiki.
• Only mods would be able to enable wikis but the process of doing so would be trivially easy.
• I'd personally say that it makes the most sense to just have the mods link the associated wiki from the sidebar rather than creating new special interface features to add a link outside the sidebar or whatever. (Unless some kind of plugin infrastructure that would allow that already exists.)

But all that can be done without putting any wiki-specific code into the Lemmy or Lemmy-UI source repositories, which I think is preferable for the same reason you wouldn't add flight simulator code to a spreadsheet application. (Ok, maybe a bad example, but you get my point.)

Edit: And I'll admit there are both upsides and downsides to my approach here. One downside would be that some Lemmy instances would offer attached wikis and others wouldn't. It's possible it also just wouldn't catch on at all and nobody would enable attached wikis as a feature if it was a whole separate step to setting up "Lemmy".

You're welcome.

I stumbled upon it myself not so long ago so I don't have any clue about how it all fits together. But on first sight it looks like a bunch of stuff is already in fedi we just don't know about it and assume Lemmy/kbim/mastodon is all there is.