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.

The House GOP leadership pulled both FISA bills!

Instead, a four-month extension is attached to the NDAA – unless it gets removed. Dozens of civil rights and racial justice groups oppose extending FISA in the NDAA.

If you agree, call your Senators TODAY and with a simple ask: “DO NOT put 702 in the NDAA.”.

(The Congressional switchboard is at (202) 224-3121, or you can use the Senate directory to find their direct number and web contact form.)

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.

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. !bad_internet_bills@lemmy.sdf.org

Thank you very much, that’s a great point – I’ll update the post to include it!

Not sure about the hashtags, good question. There will also be separate posts on Mastodon – here’s an early example, guaging awareness – and it’ll be interesting to see what gets traction where

Very good point, thanks much!

It used to be a slang term people trying to sound hip would use, but that was many decades ago – 1930s or 1950s I think.

Thanks!

Yeah, the current thinking is just to have the one magazine for now unless people have good reasons why that won’t work. Of course a lot depends on whether there are any active bugs federating between the two systems but I think right now things are copacetic.

It’s a great point. This kind of legislative activism is frequently done in public on Twitter, Facebook, etc. as well so the risks are low in general but it’s still something to make people aware of. It’s a real contrast with anything that’s direct action, where the fediverse is a non-starter.

Those are solid requirements to be listed on joinlemmy.org and I would also add another one about moderation policies prohibiting racism, sexism, anti-LGBTQ+ bigotry, Islamophobia, etc. Otherwise, if a user joins an instance that the “official” page recommends and discovers it’s racists / sexist / etc, they’ll see it as a problem with #lemmy as a whole, as opposed to just one bad instance.

And as we’ve seen on Mastodon, if a Black user goes to a site where racism is tolerated and quickly encounters racist sh*t, they leave and tell their friends; ditto for trans, queer, Muslim, etc. users having bad initial experiences. Once that happens a bunch of times the reputation becomes hard to shake. Much better to steer people to sites where they’re less likely to have a bad experience!