Haven't watched the video yet, but will. Generally, the problem with this expanded definition of Fediverse to include #Bluesky and everone who interacts via 'decentralized' social media is that, while Fediverse has not always meant just ActivityPub, it has come to be pretty synonymous in general usage. And, lots of the literature and marketing descriptions of the Fediverse assume this meaning.
more...
The Fediverse is a range of different open source softwares, all based on the #activitypub and federated by this protocol which has been designed to allow a federation of independent and totally autonomous instances with full control by their administrators. That's called "decentralisation".
So, #Threads is not in the Fediverse.
#BlueSky may become interoperable with the Fediverse and may be considered with gentleness but it will never become a part of the Fediverse.
@bsky.app@pfrazee.com @mike @dot_social @liaizon
Ok, technically it's a not a full-network one - I added ~2000 known self-hosted PDSes there, but *without* Bluesky-run ones. Which means it has like 2 orders of magnitude less traffic than a full one… But if you're self-hosting a PDS, you should see your records streaming through there, if you either send a requestCrawl there or my PDS indexer has found you.
Ok, technically it's a not a full-network one - I added ~2000 known self-hosted PDSes there, but *without* Bluesky-run ones. Which means it has like 2 orders of magnitude less traffic than a full one… But if you're self-hosting a PDS, you should see your records streaming through there, if you either send a requestCrawl there or my PDS indexer has found you.
Note, this currently uses ~200 kbit/s traffic and ~200 MB disk space, Munin stats here: https://relay.feeds.blue/munin/
Like Christine, I think the future of the fediverse will look quite different to the current Mastodon-dominated network, and more like the user experience offered by BS;
https://dustycloud.org/blog/how-decentralized-is-bluesky/
The raw materials already exist to build this evolution of the verse. The question is, how do we pull it all together?
(6/6)
The current adoption landscape ( #rss, #bluesky, #mastodon) highlights various technical possibilities but doesnt span whats possible, nor what is needed.
These three datapoints define a plane of possibilities but the actual space is probably much bigger.
Like Christine, I think the future of the fediverse will look quite different to the current Mastodon-dominated network, and more like the user experience offered by BS;
https://dustycloud.org/blog/how-decentralized-is-bluesky/
The raw materials already exist to build this evolution of the verse. The question is, how do we pull it all together?
(6/6)
Ideally an AP 2.0 would include a formal mechanism for protocol extensions. One that learns from the experiences of the FEP process.
This article sets out to compare ActivityPub and ATProto, but what it really compares is Mastodon and BlueSky;
It is useful however as a 'user story' about the failure modes of the existing, Mastodon-dominated fediverse.
(1/?)
Kann ich Bluesky als Domain sperren, wenn ich
bsky.brid.gy
sperre?
Ich will Bluesky komplett sperren als Server.
Edit: was die Sperrung von bsky.brid.gy anscheinend schon mal nicht macht: einen bereits in meinem Feed befindlichen, gebridten Beitrag verschwinden lassen😩
- @rudyfraser.com announced today that Blacksy feeds and moderation service are now powered by our own atproto relay -- and it's an independent implementation, not using Bluesky's reference code. It's really worth reading the thread, which has a great analogy for how a relay enables custom feeds.
@edavis.dev has configured deer.social (a third-party app) to to point to a self-hosted bsky appview which reads from a self-hosted relay which subscribes to a self-hosted PDS which is where this -- as he says, "Bluesky independent from Bluesky".
@bnewbold published A Full-Network Relay for $34 a Month, updating his post from last summer. The network size has increased by close to an order of magnitude since his first post; the cost of a realy
#FreeOurFeedsis donating a $50K to the AT Community Fund to support the #IndieSky working group. The notes from last week's Ahoy IndieSky Europe give a sense of the energy here -- and also link to a bunch of other projects that sure look decentralized to me and discusses the prospects of Eurosky.
Of course, like I said in the article,
""Decentralization" means different things to different people. As the links in the Appendix highlight, people who are focusing on the (very real) concentration of power in the ATmosphere today, or the potentially-centralizing architecture of AT, find it more useful to describe Bluesky as centralized."
And the power concentration -- or "operational centralization" as Bluesky folks were calling it at the ATmosphere Conference -- is still very real. Bluesky still runs almost all of the infrastructure for the ATmosphere, and it's by far the most popular app, and most other apps (as well as Bluesky) use the Bluesky AppView, Relay, and labeler.
Then again, that's clearly in the process of changing, and it'll be interesting to see how it looks six months or a year from now.
@laurenshof @fediversereport @cyrus @cwebber @rysiek @jonny @possibledog @oblomov @rwg @Kye
So Eric here is now running a forked version of https://bsky.app at https://deer.social, which loads data from a self-hosted full-network #Bluesky AppView, streaming from a self-hosted relay. Basically, "bluesky independent* from bluesky"
(*) the one completely centralized point remains the https://plc.directory DID identity server, unless you use a did:web: ID
They are a little confused though, claiming that Bluesky is part of the #fediverse mitigates this.