Catodon is a new Sharkey/Misskey fork.

List of servers (pretty small): https://catodon.fediverse.observer/list

Well, for me it is different from twitter/mastodon because there is a reasonable post lenght restriction 5000 characters, and misskey is one of the best UI of the fediverse. So it is better, there is a good balance between thread/microblog.

Once they support well thread, i will probably crosspost lot content from them here. News, scientifics, political…and it will ease up my work as a community animator. I can relay content for news but that’s lot work.

For me, here, we miss 2 things :

• a rss reader
• microblog support

@zenbeater

Thank you very much. Yet another instance of very constructive feedback. This is the #Fediverse at its best.

I did spend some thoughts on the name.

1. It should not clash with the big existing professional network(s).
2. The name should convey, what it is.
3. It should be reasonably catchy.

Of course I'm happy to read other, maybe better options.

@julian @evan @njvack @dgfitch @skinnylatte @tankgrrl @Viss @ai6yr @mayintoronto

Wow that is just brilliant. I love how the SFO *airport museum* staff just went off and figured out how to track items (and planes visiting the airport!) and everything in a low-cost scalable way that totally plugs into the Fediverse. Neat! :fediverse:

@sfomuseum

@jaz@toot.wales Great, the CFP for the track is now open!

https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp

Attorney Cindy Cohn talks to Jon Stewart about her new book, “Privacy’s Defender: My Thirty-Year Fight Against Digital Surveillance,” and her work as executive director of the Electronic Frontier Foundation, which is the world’s biggest and oldest digital rights organization. She recounts the fight against sweeping government surveillance after ⁹⁄₁₁, her reservations about internet regulations backfiring if placed in the wrong hands, and why the solution to these problems is a combination of comprehensive privacy law, revised business models of giant tech companies who make money off of user data, and more platform choices for individuals. “A world where there are five big media companies that decide everything that we see and how we see it… the answer isn’t to try to take a dictator and make them a better dictator. The answer is to get rid of the dictators and make them less important.”

She mentions Mastodon and Jon doesn’t understand how reddit is curating his experience. It’s a good piece because they’re such opposites, but both have great intentions.

The #CFP for the Fediverse & Social Web track at COSCUP 2026 (Taipei, Aug 8–9) is now open! If you’re working on #ActivityPub, the #fediverse, or anything in the open social web space, we’d love to hear from you. The deadline is May 9. #COSCUP is free to attend.

👉 https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp

(Boosts appreciated!)

#SocialWeb #fedidev

Here’s an interesting thought experiment.

Way back in the 1980s and 90s, Usenet was a sorta-federated discussion forum (using the NNTP protocol) that was very popular. It still exists and is distributing 400 million messages each day (mostly spam and trash as far as I can tell). Hard numbers are difficult to come by but it seems like Usenet is capable of significantly higher throughput. Why is that?

The big thing holding ActivityPub back is the fan-out. You know the story - someone with 50,000 followers causes their instance to send up to 50,000 HTTP POSTs every time they click the little spinny star or reply to something.

It’s basically a hub-and-spoke network topology. Except everyone takes turns being the hub, ideally, but not much in practice. And in this topology, the hubs are where the strain and bottlenecks are.

Back in the 1980s they had computers literally 1000 times slower than ours and network links to match. So how did they do this? With a peer to peer network topology! When a new post is made, they don’t send it to everyone they just send it to a handful of other servers. Those servers in turn forward the post on to a handful of other peers, and so on, until the whole network receives the post. No individual server is a single point of failure and none has to bear the full brunt of orchestrating it all.

Let’s do a picture. A creates a post and sends it to B and D.

A ─ B ─ C  
 \      /  
   ─ D ─  

B sends it on to C.

Meanwhile D sends it on the C also but C already has it so does nothing more. IRL this would be a much larger mesh. Who peers with who can be a mixture of manual selection and random spiciness.

Posts can arrive out of order so each server would need to wait until the dependencies between posts are resolved before making them available to clients. That’s a bit tricky.

In the ActivityPub-over-NNTP idea, each NNTP post would be a thin wrapper around a data structure containing the HTTP headers (with signature and digest) and JSON that a normal HTTP POSTed Activity would have. Servers would use NNTP to distribute the activities and upon receiving one they’d POST it to their own /inbox to run the usual ActivityPub processing that their AP instance does.

{  
  "headers": {  
    "Signature": "...",  
    "Digest": "...",  
    "Date": "..."  
  },  
  "activity": { ... normal ActivityPub JSON ... }  
}  

In this way there is no need to rewrite ActivityPub semantics as only the transport layer changes. Our existing inbox logic remains intact.

NNTP comes with a lot of historical baggage so we’d probably need to evolve the protocol a bit. Maybe use HTTP requests (even http2 streams?) instead of the original line-oriented text protocol using raw TCP sockets. But you get the idea.

Thoughts?

Yes, I think that’s part of NNTP already. Each post has a list of the servers it has traveled through so when considering where to forward the post on to a server can check if it’s already been there. That would help somewhat but still there would be quite a few times when a server discards posts.

I haven’t gotten deep enough into this yet but I’m sure there have been protocol improvements since NNTP that address this. Gossip protocols have been experimented with since the early 2000s. For example, rather than servers saying to others “I have this post, do you want it?” they might say “the most recent post I have in the fediverse@lemmy.world community is #5” and another server which only has posts #1 and #2 would respond “cool, give me posts #3, #4 and #5”.

Good point.

PieFed Application Actions

This plugin is designed to execute actions when a user’s application to a PieFed instance is ready for admin review.

Features

Currently, the only feature is sending an email to specified email addresses when an application is ready for review. The email is sent using the same from email address as the PieFed instance itself for all its other emails.

Most excellent! Going to give this a go for my instance on next bump!

Thanks Snoopy!

eewww

This story is from March 9th. The Bluesky my butt app announcement was around March 29th.