Because what Twitter really needs right now is less engagement.

If they really do shut off API access I’ll go into partial link aggregator withdrawal. My Lemmy instance still isn’t upgraded to the latest versions which are compatible with apps, so I don’t browse on my phone.

I think a difference between email and ActivityPub-based social media is there’s arguably less of a need to have federation between any two servers. If you can’t email the government, your sister living abroad, or a client, that’s a big problem. But if you can’t follow a cat pictures account or your friend’s constant stream of baseball rants because the servers don’t federate it’s not quite the same.

If Meta becomes ActivityPub interoperable instances may or may not federate with them. Either way it’s not necessarily going to change my social media experience.

Having used both, while the market implications of NACS are still unclear it sure is the more ergonomic of the two standards. Those CCS2 DC connectors are just too large and unwieldy.

There’s many different ways DID could be implemented on top of ActivityPub. I don’t think full content replication (what you’re mentioning) is likely as that’s a fundamentally different style of protocol.

But I can imagine signing in to a different instance with my ID, at which point I subscribe to all my communities from this instance and get notifications if someone replies to one of my comments etc. Just as if I had created an account on this instance and had posted from there. It just means “your” instance can go down and you can continue future interactions mostly uninterrupted from another instance.

And it’s more useful in the case of microblogging, where with DID you can publish posts from any instance and your followers will see them. No need for a manual account migration or anything.

YunoHost is a tool which aims to solve the problem of (relatively small scale) self-hosting for people. I use it to host my Mastodon and Lemmy instances and it was very easy. I haven’t dealt with email but that’s also something it supports.

It’s a pretty great platform, although unfortunately it’s currently unable to upgrade Lemmy past 0.16.7 which is a bit of a pain… So it’s hard to recommend it for Lemmy right now.

100% agreed with both. Especially DIDs just need to happen on all ActivityPub platforms. It will not only free users from being locked to an instance, but it will also allow instances to be much more flexible in scaling their capacity. Lemmy.ml is overloaded because they have too many users, and anyone who signed up there can no longer use their account. DID would allow them to immediately use their account from any small or large instance with spare capacity without changing the experience. The same would go for Mastodon.

Beehaw only defederated from Lemmy.world because of the currently limited moderation tools in the software. This is not going to be a problem forever.

I hope people can find communities both on large instances (Beehaw, Lemmy.world) as well on as very small niche instances. Discoverability is a bit a problem but I think over time we will find communities we like, and participate in them. What instance they are hosted on is not all that important.

Huh. Guess I won’t be using Uber’s apps then. Anytime I’m a paying customer I do not want to see ads shoved in my face. Good thing there’s competition.