That’s exactly my point, though.

It absolutely does. Think of lemmy like of email – your mail server has all the email you received.

Looking at the resource usage of mine, a tiny cheap VPS for $4/mo would be enough, sans the image store. But it’s not a hard requirement unless you expect to have lots of local communities posting pictures.

Lemmy’s issue is that it’s non-trivial to deploy and oftentimes painful to upgrade.

SLACC doesn’t support sending stuff like DNS servers.

It does

I took a look at the current traffic and you’re absolutely correct, lemmy (as of 0.19) has a proper schema with everything covered!

But lemmy doesn’t use “plain json”, it annotates some fields with the schema, just not all of them, which makes it a mess. You either do json-ld proper, or you don’t do it at all.

no Federation with instances that use altered versions or proprietary versions of AP.

It’s especially funny given (the last time I checked) neither kbin nor lemmy actually followed the spec properly. They ignore the jsonld requirements and resort to field names, that, by the spec, should be dropped.

Edit: lemmy is actually good now!

isn’t threads already several times larger than the whole of the “fediverse”?

I wouldn’t quite call Lemmy’s protocol much friendly either. I’m trying to implement it and it’s a bit of a mess, honestly. There’s absolutely no documentation, private database specifics leaking into the public interfaces, and an absolutely horrendous authentication scheme.

The codebase is actually vastly more readable. I’m going to take it for a spin tomorrow and see how well it behaves, but so far it sounds like a much better deal deployment-wide for small instances.

This one was on page 3 of lemmy.world, heh. Rolling out the update that tries to scrape all pages proper right now.

I think they have several times more users than all mastodon instances combined, though?