That may have been the intention but I doubt it ever worked as effectively as they claimed it would. Besides, it will probably cost at least 1 AI data-center of carbon emissions to continuously surveil all these people with TPMS sensors, so the argument could be made that you’re actually reducing carbon pollution at this point by removing yours.

Anything you post on the internet is public knowledge forever. End of discussion. Most people won’t care at all, in most cases almost nobody or perhaps even literally nobody will ever even see it, but the harder you try to hide it, the more the Streisand Effect will magnify it until eventually everyone knows about it.

Anyone telling you they’ll delete your data from the internet without clarifying that it is in fact impossible, is at worst deliberately lying to you usually for their own benefit, and at best making a promise they literally have zero ability to keep.

I would hope that Fediverse services will never lie to you and tell you your data is deleted, because it can’t be.

I’m going down the rabbit hole and people are forced to queue up for what I’m assuming is the equivalent of a serial key?

Not quite. A serial key is permanent, it lasts forever, although some software did try to use online and update services to identify bad serials this was trivial to block, because it’s essentially trying to backpedal a valid key into an invalid one. It only needs to be valid once, then you make sure to block anything that invalidates it afterwards (usually blocking the update servers at the DNS level), job done.

That’s different from a token. Tokens use something along the lines of at least rolling-code type security, similar to how your car keys or garage door opener keep generating new codes so someone with a scanner can’t just record the code it uses once and then have that be copied and replayed over and over again indefinitely. The trick with a token like this is that you need to keep updating it or it becomes invalid after some timeframe or number of uses. Hence the online activation. That’s required to get your next token or set of tokens.

They would be. That’s why you don’t tell them. If you’re treating your insurance company as your friend not an adversary, you probably don’t understand how their profits grow year over year.

I’ve been driving for 30 years. Do you want to guess how many times that’s happened to me?

Meanwhile, I’ve apparently been living in a totalitarian surveillance state for at least a few years now, and you know how many times that’s happened to me? I’ll give you a hint, it’s more than the number of times I’ve run over a nail causing me to drive around on low tire pressure without knowing it.

Despite our governments (well, one of our governments) the Canadian and American people still care for and look out for one another.

I’ll drink a cuba libre to that!

These are described as “subprocessors”, so generally, this means that Persona is (potentially) sending any data they receive to these companies/platforms.

I agree that quadlets are pretty ugly but I’m not sure that’s the ini style’s fault. In general I find yaml incredibly frustrating to understand, but toml/ini style is pretty fluent to me. Maybe just a preference, IDK.

Systemd killed my father, but it’s okay because he was Darth Vader anyway.

I think ActivityPub is closer to the right answer than ATProto, and ActivityPub’s issues (though many, as the author notes) are more manageable in the long run. I think the article makes a good analysis of the fundamental differences, but is a bit glib in referring to Piefed’s topics and discussion merging as a “joyful mess”. It’s not a mess at all. It’s making order out of the chaos, and it’s the right way to build on top of ActivityPub into something that is actually fluid enough for users to actually use.

Mailing lists were built on top of federated email in much the same way, and they formed enduring, resilient, well-structured communities, some that continue to this day (the LKML being perhaps the most notorious)

I think ATProto makes creating enduring communities too difficult, and BlackSky illustrates that perfectly. The author’s criticism of ActivityPub, on the other hand, seems to be that it makes creating communities too easy, and this results in a “mess”. I disagree, I think the mess is a necessary and inevitable part of having community. Communities are messy. They fracture and schism, they rejoin and reshape themselves. That’s normal. It is the responsibility of the software to make sense of the mess and make it presentable, and with ActivityPub, that is not only possible, it is happening. Piefed is the present example. I expect there will be more examples, and a wider variety of them, as the ecosystem continues to develop.

I think the biggest thing that ActivityPub still needs is better portability, for both users and communities, to allow moving servers more seamlessly. The “Personal Data Server” of Bluesky is not a bad concept, although I don’t love their implementation. I think ActivityPub can find a way to handle portability even better, but it doesn’t seem like it’s been a priority, and that’s fine. But it will need to happen eventually.