Adding reference to HN submission of this article. Discussion thus far has 233 comments.

I maintain some lists too, PR’s welcome:

• Server Apps
• Clients
• Developer Resources

Have a look at #flohmarkt, federated decentral classified ad software using #activitypub: https://codeberg.org/grindhold/flohmarkt By @[email protected]

That second comment by goplayoutside says it well: “Maybe the modest technical hurdles are a feature, not a bug.”

I think it is a feature, and the same is true for Mastodon and the Fediverse as a whole, imho.

Pavilion had early plans to create a plugin, and applied for a NLnet grant. When that wasn’t accepted they put their plans in the freezer. It is only recently, after The Muskening™ that they picked up on it again.

See this post on the Discourse Meta forum about the plans.

Indeed. “Sense of community” is an aspect where additional socio-technical support native to the Fediverse can be quite helpful. We have the basics now. There’s work to add Groups support, but community is more than just groups. It has intricate and meaningful relationships between many other groups and people. Just like in real life.

Apart from that The Pavilion cooperative has announced they work on a Discourse forum plugin for the Fediverse. And also I got word from the Flarum maintainer that they have plans to add support (but there’s been silence after that).

Update: Here’s a thread on Flarum’s ongoing work: https://discuss.flarum.org/d/31943-federation-extension

Ah, that is due to the particular app that is being used, called Bovine. @[email protected] (also not directly browser-accessible) wrote:

🚨🚨🚨 DON’T! This suggestion leads to Spaghetti Architecture.

First, Client to Server specifies how to one client talks to one server. This change is about one Client (in a browser) talking to a lot of servers, breaking the Servers talk to Servers, a Client talks to the Server it’s a client of, pattern.

Second, this change allows clients (in browsers) to circumvent blocking. If you block a server domain, you don’t want the clients to fallback to getting the information directly from you.

So please, do not implement this change; and if you have this type of CORS header set, consider removing them.

Top-level toot: https://social.oberhauser.space/@obale/110058041568721745

For readers the follow-up to the same toot is relevant as well. First reply is “Don’t do this”.

Much appreciated, thank you very much. Esp. the attention to having good docs is a delight in the otherwise under-documented maze of fedi development.

With Gitea Ltd sudden incorporation, the soft fork of Gitea launched as Forgejo (which is what Codeberg now runs on) most of the forge federation efforts have shifted in that direction, as it offers the highest guarantees of remaining to the public benefit. Gitea has received a NLnet grant to add federation support, but it is unknown to what extent they are actively working towards implementing its goals. Those interested to learn more can join the Forge Federation general chatroom on Matrix.

Yes, I think people should skip to the “We have to keep going” section of the article to put the previous text in better context.

Thank you for your participation in the FEP process. I am really happy to see this finalized, and also that Fediverse Enhancement Proposals is picking up steam to bring more standardization to the Fediverse.

I have happy news in that regard. We have migrated the watchlists to the Delightful Project on Codeberg. And they are rendered on the Delightful Club website.

Bit weird. An anonymous Google Doc, a screenshot of a toot saying “this is legit” and no other references. Could at least provide the URL to that toot.

Besides someone opting in, I hope that the person being quote-tooted also receives notification of that and maybe even notiications of all replies on the quote toot. This so it isn’t a mechanism to “talk behind someone’s back” which by leaving someone unaware makes it more suited tool for abuse.

SSPL is source-available, and not open source. There was lotsa discussion about the SSPL license, which was created by MongoDB, and it is a complex matter with all kinds of judicial angles. In summary it mainly benefits Mongo most of all, whose ‘open source passion’ is marketing-speak mostly. I forgot a lot of ins and outs, but just dug up a random find about downsides (2 parts) and impact.

A pity (for me) is the SSPL licensing, probably chosen because of the use of MongoDB. When using an alternative (maybe FerretDB) it could be Apache 2.0, which was the originally intented I heard (and still mentioned on the website).

What kind of attention, you ask? Well, read here… https://mastodon.social/@atomicpoet/109742115695898174 … the billionaire VC kind of attention.

And someone might write the article: “Of course the Fediverse is threatened by the attention of the attention economy”. Don’t overly focus on whether Mastodon has attention-grabbing engagement features or not. It is an app, folks, just one app on the Fediverse. If you look around you already see how corporate interests are encroaching our space, testing the waters. And they won’t always be single endpoints that you simple defederate with a single block action. Think of cloudflare for instance. Some corporate takeover and EEE scenario’s were recently discussed on HN.