Bluesky's model of decentralization continues to be "we'll get to it one day, trust me bro."

[rysiek@mstdn.social]

Bluesky's model of decentralization continues to be "we'll get to it one day, trust me bro."

[quinn@social.circl.lu]

@rysiek They have bigger problems. Have you seen how fucked their culture is? It's like watching overcrowded chickens peck each other to death.

[quinn@social.circl.lu]

@rysiek you cannot decentralize your way out of bsky's kneejerk culture of bonding over hating people.

[rysiek@mstdn.social]

I eagerly await people to start explaining to me how that's not true, actshcualleyh, because you can kajigger the whatchamacallit and run your own BDSM.

[rysiek@mstdn.social]

@quinn I'd argue you can. Smaller communities can change and improve their culture much easier than huge platforms.

[quinn@social.circl.lu]

@rysiek You're walking into an abattoir and trying to set up a tea room. You're fighting a founder effect and an interface culture of Twitter at its worst. Just the founder effect on its own is basically cursed. This is "they only moved the headstones" territory.

[rysiek@mstdn.social]

Do folks still remember that Bluesky Social PBC is a VC-funded company, and one of the biggest investors is Blockchain Capital?
https://bsky.social/about/blog/10-24-2024-series-a

[rysiek@mstdn.social]

@quinn I did not say it's easy. And I am not even going to try.

[mastodonmigration@mastodon.online]

@rysiek @quinn

Feel like you are both right.

[rysiek@mstdn.social]

@mastodonmigration @quinn we are forcefully agreeing I think.

[rysiek@mstdn.social]

I do hope fedi is going to be ready for Bluesky migration once it starts. Because it's going to, eventually.
https://bsky.app/profile/kozufox.bsky.social/post/3m2k5pf63ks2h

[ploum@mamot.fr]

@rysiek : people believe anything. I mean, Ripple (xrp) is still one of the biggest cryptocurrency out there while being totally centralized and 80% of its token in the hand of a few founders.

In fact, people want "centralised decentralisation" (I mean, they invented "permissonned blockchains" to centralize something which had the only pros of being decentralized with lot of disadvantages).

Talked about this 2 years ago: https://ploum.net/2023-03-03-bluesky.html

[oblomov@sociale.network]

@rysiek the next post in the thread is what I've been wondering since the beginning

https://bsky.app/profile/kozufox.bsky.social/post/3m2k5shwggc2h

(Alternatively, a solid frontend to SSB.)

[jdp23@neuromatch.social]

Rudy's late 2023 posts talk about why he saw ATProto as a better basis for what he wants to accomplish for Blacksky than Mastodon. I don't think anything that's happened since then has changed his opinion ... instead he's gotten a better understanding of some of the strengths of the fedi model and either come up with complementary ways of doing things: local-only posts, context-sensitve community-focused moderation using AT's building blocks and custom software. There are links at the end of the first section of https://privacy.thenexus.today/what-solidarity-looks-like/

@rysiek agreed that it would be great for fedi to prepare for a wave of newcomers and possibly returnees. I'm about to do a post askingn for suggestions on this in terms of the upcoming Media Liberation Day on November 5 and there's probably a lot of overlap -- I'll drop a link here once it's ready. Specifically from a Bluesky perspective though ...

What do you think people here should do to get ready for a wave -- and to make a wave more likely?

@oblomov

[rysiek@mstdn.social]

@jdp23 I would like to see a retrospective of what went wrong last time and build on that.

Things that I would single out would be: racism, tensions with and hostility towards newcomers due to social norms on fedi that were opaque to them, on-boarding issues. Maybe some infrastructure issues although these seemed to have been handled pretty well I think?

Some of the stuff is partially sorted. We have some starter packs, for example, which help with on-boarding.

@oblomov

[rysiek@mstdn.social]

@jdp23 one thing I'd think about is having a an open conversation about which instances are accepting newcomers, which would prefer not to – and expose that information *beforehand* to people who might want to join in a wave.

It's one thing to deal with the regular trickle of new users, it's something different to deal with a wave.

Maybe talk to people about emergency volunteering in moderation teams, for example in case of a wave. That sort of thing.

@oblomov

[rysiek@mstdn.social]

@jdp23 basically, looking at where tensions were being created and planning around that to minimize these tensions when a wave hits.

@oblomov

[jdp23@neuromatch.social]

Agreed on all of those, great points! I think of the hostility to newcomers and opaque social norms as separate but related. Helping newcomers understand norms here as part of onboarding is really important; so is encouraging people who are here to be less hostile (even when defending worthwhile norms, which is sometimes the case), and setting expectations for newcomers that "yeah there are jerks here just like anywhere else and here's what you can do about it."

Starter packs can be useful if people can find them, which is likely to be non-trivial in general. (Although the starter packs we currently have are non-consensual so there's a risk of an explosion if they start to become a vector for harassment or even unwanted follows, at this point I'm not sure about what to do on that front except hope for the best.)

@rysiek @oblomov

[rysiek@mstdn.social]

@jdp23 @oblomov well, we can have consensual starter packs, simply by asking people before we add them.

There's always some opportunity to be malicious, but the same way we have certain well-curated instance lists, we can have well-curated starter pack lists, and these could have rules around consent to being on them.