Well said, thanks!

Thanks very much for excerpting that!

Reparations aren’t just a cash payment – the article lists five different aspects of reparations, and it’s very compatible with investing in Black communities. There’s debate iover who should be eligible but it’s not an unsolvable problem. And sure some people will use it as an excuse to declare racism’s over, but the same was true when Obama got elected … so that’s not a reason not to do it!

In terms of support in general, do you support the 1988 decision by the US to pay reparations to Japanese-Americans who had been sent to internment camps?

Great writeup! A couple thoughts:

First & foremost, which is somewhat glossed over, is the notion that ordinary people will have the knowledge or interest in deploying their own Personal Data Servers. This isn’t really touched on from what I’ve seen in their documentation, despite it being touted as such a major benefit of the architecture.

Very true. There’s a line buried in their white paper that “we expect that most users will sign up for an account on a shared PDS run by a professional hosting provider – either Bluesky Social PBC, or another company” but they very much do tout it as a major benefit. It’s certainly true that the ability to move your data around is a very good thing, and something the fediverse is bad at today, so from a positioning perspective it makes sense to focus on this; their claims that this gives the user power are, um, exaggerated.

due to the high volumes of data involved, there are likely to be fewer Relays deployed instead of many.

Yeah I was in in a discussion where a Bluesky developer suggested that non-profits might run their own Relays … seems unlikely to me, both because of the volume and because of the risk of potentially relaying content that’s legal in whatever jurisdiction the PDS is in but not in the Relay’s jurisdication. Of course Relays don’t have to be for the full network, so we might see more smaller-scoped Relays (although I’m not sure how that differs from a Feed Generator), but if BlueSky and a few others provide the only full-network Relay, that’s a pretty powerful position for them to be in.

Also in that conversation the said that AppViews are likely to be even more resource-intensive than Relays, and so anybody developing an AppView might as well have a Relay as well, so there’s likely to be the same kind of power concentration.

That said I think it’s very good that Relays explicitly appear in their architecture. Relays are also critical for smaller or less-connected instances in today’s fediverse, but don’t get a lot of attention.

Arguably this may make the AuthTransfer network no more decentralized (they go back & forth on describing their approach as decentralized and distributed) than the ActivityPub network is.

Yep. They’ve split the functions of the ActivityPub instance, but it seems to me that they’ve just shifted the power imbalances around, and potentially magnified them.

There was an interesting pair of polls last summer about reactions to Threads and Tumblr. 66% of the respondents were either opposed to or alarmed by Threads federating, and only 10% were supportive. By contrast, only 15% were opposed to or alarmed by Tumblr, and 39% were supportive. It’s just one data point but still interesting!

https://mastodon.social/@mcc/110663712542031369

Right. And that’s why I’m on blahaj.zone!

For many thought it’s not that simple: they’re okay with Meta housing hate groups as long as it doesn’t directly lead to users on their instances being harassed. And it wouldn’t surprise me that if harassment starts happening it’ll still turn out not to be that simple for them because there are a lot more non-harassing accounts than harassing accounts

Totally agree. Back in June I wrote about the reasons the FediPact was good strategy and started it with

Most importantly, it counters the gaslighting that resistance is futile. The segment of the fediverse that wants to reject Meta is clearly large enough that it will survive no matter what the big Mastodon instances and pundits do.

Agreed that figuring out the right action is important! It’s clear from the conversation so far that a lot of instances are going to defederate, and a lot of instances are going to federate, so any strategy needs to take that into account.

I talked with a lot of people about this when I wrote Should the Fediverse welcome its new surveillance-capitalism overlords? Opinions differ! and don’t think it’s the case that we share the same goals. Some people see increasing the size of the ActivityPub network as a goal in and of itself (and generally support federation); others are in the fediverse because they want nothing to do with Facebook or Meta (so unsurprisingly support defederation). And some people have a goal of communicating with people on Threads – friends, relatives, celebrities, etc; others don’t. So again, these different goals are something to take into account.

Wanting to stay federated DOES NOT mean the user wants to help Meta or thinks that Meta is here for our benefit.

That’s correct, but many of the people I’ve seen arguing in favor of federation do seem to think Meta’s looking for a win/win situation where the fediverse benefits as much or more than Meta. And conversely many would argue that wanting to stay federated means the user is helping Meta whether they want to or not.

Thanks, it’s a good point!

It depends if I’ve turned on “approve followers” – upvote if you agree!

No, followers-only posts are not public – upvote if you agree!

Yes, followers-only posts are public – upvote if you agree!

You’re right … but tech has a lot of lobbying power and they are very very very strongly against a strong privacy bill, or even a bill that would regulate algorithms. So it’s easier for legislators to pass something like KOSA – or pass a weak privacy bill that will actually make the situation worse by getting rid of laws like California’s – and claim they’re doing something.

yeah it’s really disappointing.

Totally agree that we need a good privacy bill – and if the proposed ADPPA consumer privacy moves forward again this year, we’ll need to get involved on that to push to strengthen it (because last year’s version had huge loopholes, including some that left LGBTQ+ people’s personal data at risk).

It turns out that crossposting to Lemmy works better from Lemmy communities. So, a Lemmy community is useful. Since I had already crated the kbin magazine and there’s no way to delete magazines (!), looks like we’ll experiment to see whether or not having two of them makes sense. Here’s the Lemmy community I created, I’m using it for now to cross-post from other communities so that there’s a single place to go for everything. [email protected]

I don’t trust them either, and they’re very likely to move ahead with federation anyhow. It still means something that they’re changing the story that they’re telling.

Nobody’s talking about taking the choice away from others. Some instances are saying they’ll federate with Threads, you’re free to move your account there. Or as you say, people who want to hang out with the bully can download the Threads app right now!

That’s incorrect. Followers-only posts (and local-only posts on instances that have them) aren’t public. Profiles that don’t make public and unlisted posts aren’t discoverable. And, as Threat modeling Meta, the fediverse, and privacy discusses, there are plenty of things that could be done to reduce the amount of data that’s public.

Also, that’s only one of the many reasons people oppose federating with Meta.

That’s right, as the article says

And from the perspective of the “free fediverse” that’s not welcoming Meta, the new positioning that ActivityPub integration is “a long way out” is encouraging. OK, it’s not as good as “when hell freezes over,” but it’s a heckuva lot better than “soon.”