It’s just a nod to the fact that I didn’t go into this project wanting to deal with zero-copy issues - it was decided for me by the library that I needed. Most of the time I do in fact slap Deserialize on a bunch of static types.

I did in the end, of course, but I encountered the two consequences separately and it wasn’t obvious at first.

This is one scenario I proposed when we were last having this discussion: https://thomask.sdf.org/blog/2023/07/07/if-i-was-meta-and-wanted-to-make-fedi-implode.html

I was comparing frozen diced veggies a couple of years back (in Australia) and noticed that the store-brand version was approximately 1/3 broccoli stems by volume, which certainly explained the cost difference.

Sitting there watching with satisfaction as MSDOS 6.22 DEFRAG.EXE did its thing.

Previous years:

• 2021
• 2020
• 2019

I continue to be a little disappointed how brief these have become since 2019, given how exhaustive the questions are.

They’re certainly thinking about it, going by this post: https://lemmy.sdf.org/post/173597?scrollToComments=true

Lots of previous discussion on this thread: https://lemmy.sdf.org/post/578847

No idea if it’s relevant in this case but at least once I had to clear both browser cache and the cookies/site data to get Lemmy rendering right after an update.

Happily no, all okay here on web UI. e.g. 10 hours, 7 days, 15 days and 19 days on https://lemmy.sdf.org/c/anonradio

Ask yourself, in three years from now will you be thinking “it’s so nice how Meta lets me follow and interact with their enormous userbase for free, without advertising, using my own open source server and frontend”?

Remember that’s the basic expectation today for a participant in the fediverse. If this feels implausible, doing anything else is very incompatible with the fediverse’s existing values.

The problem isn’t just that it’s Meta, it’s any situation where a much larger actor comes in with different motivations. Today we have a small number of users whose servers are almost exclusively run on a “community service” model. Meta is an advertising business. They are much bigger and will define the fediverse if allowed in. If we allow them to connect, it should be much later after organic growth which means we can assimilate them properly and deflect any bad behaviour.

What might happen if Meta throws their weight around? I can predict at least three outcomes

• Proprietary variations to ActivityPub, probably starting with something that seems “understandable” like moderation reasons.
• Certain new features get centralised on Meta’s servers only (e.g. search) claiming that it’s for efficiency in the distributed environment.
• Claiming spam problems, require individual instance operators or their users to verify themselves with Meta to enable federation.

The question in my mind is whether their intention is to destroy the competition, or keep the fediverse alive as a way to claim that they are not a technical monopoly that needs to be broken up by regulators, in the same way that Google provides most of the funding for Firefox.

One approach I’m personally fond of is actor-style async programming with tokio. It’s easy to mingle timers with receiving messages from channels, which is quite powerful. This post by Alice Rhyl is a good description of the idea: https://ryhl.io/blog/actors-with-tokio/