But do we need some kind of SSO layer with DID verification? All I need to prove my identity anywhere, technically, is my private+public keypair. As long as I hold on to this keypair, distribute it between apps/computers, back it up, I could log in anywhere on a federated platform and use it.

I hope we’re going to see key-based decentralized identity on ActivityPub at some point… Having accounts tied to instances is just not very robust or scalable.

What they really mean is: Polite to them, the people with the means of easily inflicting deadly violence upon others.

Gun ownership is just another expression of the deep selfishness ingrained in American culture.

Their first album indubitably is my favorite, obviously.

Most of the Koopa kids were named after musicians

• Wendy O. Williams from the Plasmatics
• Iggy Pop from Iggy Pop & The Stooges
• Roy Orbison, the songwriter and rock & roll legend
• Lemmy Kilmister from Motörhead
• Ludwig van Beethoven, obviously

Someone should tell Retsuko about this kind of service.

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’m no expert but I think we’re looking at parts of the vehicle which were outside the pressure hull. Those parts would not have been subjected to such extreme forces when the hull failed.

Most bits of a DSV are actually outside of the pressure hull, just look at the designs of Trieste or Limiting Factor. This is to maximize the space available to human passengers inside the relatively small (and very expensive to construct) hull.

Yeah, this happened to Mastodon (aka the microblogging part of Fedi) also. I was on Mastodon on-and-off for years before the Twitter exodus, and it was a very different place back then. I can see why people miss the overall community on a platform before it became popular, but then I feel like ActivityPub gives us the tools to shape the communities we want, so we have to engage with it and be more selective than we were before.

I mean obviously “Taxation without Representation” is one of the foundational injustices which led to the declaration of independence, so I’m in favor for letting non-citizen residents vote. But if the state constitution says voting is only for citizens then maybe the state constitution needs to be amended…

A few states do have provisions for letting non-citizens vote in local elections: https://ballotpedia.org/Laws_permitting_noncitizens_to_vote_in_the_United_States

I think some people reacted a bit too quickly to that sublemmy appearing though… Give admins some time to evaluate and resolve the situation before impulsively defederating an entire 6000-user instance.

We continue to inch closer to full-blown corporatocracy. We’ve all watched and read enough cyberpunk to see where that leads.

I hope it really works. Muscular dystrophy is such a bag of dicks. Poor kids.

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.

Great news. I think we’re still not quite there yet with cultivated meat, but it has great promise. Cultivated meat has the potential to be cheaper, far more environmentally friendly, obviously more ethical, and maybe even healthier. I hope it reaches full scale production with all these benefits in my lifetime.

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.

The Fediverse is still a strange concept to a lot of people. They assume only email is federated and the rest of the web is sites with only internally facing channels of communication.

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.