So was 0.18.0. In fact I think the next few releases will all be like this.

(just cheekily testing to make sure federation didn't break between updates)

Sure why not. Plenty of us have single user instances.

There are "questions about sex" and there are "men/women of reddit/lemmy, what's the sexiest sex you ever sexed" being repeated every other day like on r/askreddit. I assume nobody would reject the occasional insightful sex questions.

I believe, with Authorized Fetch (what Mastodon calls secure mode) blocking intermediaries won't be needed, as instances will have to cryptographically "authorize" themselves to receive/send data, and you can just say "no" to any requests coming from threads.net, acting basically as a "defederation enforcement mode".

I could be wrong though, haven't caught up on the exact details.

That's the eventual goal.

Or, well, something like it.

Microservices aren't a silver bullet. There's likely quite a lot that can be done until we need to split some parts out, and once that happens I expect that federation would be the thing to split out as that's one of the more "active" parts of the app compared to logins and whatnot.

It's generally more like "Steve's 10 eur/mo cloud server in which they run ten other things next to Lemmy, which is written by two devs and barely held together by duct tape and prayers"

But that doesn't change the overall point.

With how unreliable tallying votes over federation is, we're kinda get vote fuzzing "for free" right now.

https://www.youtube.com/watch?v=IP-rGJKSZ3s

Your server sent the subscription request to the community's server, but the acknowledgement never made it through amidst the chaos of federation. You're still subscribed.

Alpine is completely separate by RHEL by a country mile (hell, it doesn't even use glibc). You're probably thinking of Rocky

That's gonna end up a shitshow and a half, no matter which side you're on

If this comment is federating then I started hosting my first service -- Lemmy itself.