If you’re trying to build an application, you follow https://atproto.com/guides/applications
If you’re looking to run the bluesky application, you need to run the codebases in https://github.com/bluesky-social.
For PDS is that true? If bsky.app shuts down, will my PDS be able to function as an independent instance incl the web frontend etc.?
It's the kind of thing where it's preferable that either everybody switch at once, or that new applications with different "lexicon" (post types / social media format) picks a new default from the start.
Is there a way to clone the app and make this easy to find as a button to switch?
(unfamiliar with the licensing and the app in general, some things I have seen make me excited that it's possible to be uncensored and decentralized, then things like this come up and I wonder if I should put time into it or something else to promote)
There's already third party clients, account hosting servers, etc, as well as different apps building on the same system (and which can use the same accounts and data store!) like blogs and more. Most devs are trying to coordinate their custom extensions so it doesn't cause conflict.
If it weren't coordinated we'd easily end up in the same place as Mastodon with their spurious server blocks where large parts of conversations are broken for most users.
Will my self-hosted account be able to talk directly to other self-hosted BlueSky accounts?
So anyone can label/mislabel/ban/block anyone else, but everyone can chose whose labels/mislabels/bans/blocks to follow
It comes from the people who don't know what an algorithm is but heard that Twitter has it and it's making them doomscroll so it's bad
(which is not to defend Twitter or other social media's algorithms, but to say that some people seem to have a blind hatred of them entirely due to misconceptions)
It's easy to forget there's a gray area between "unsorted feed of all posts" and "nothing but insane rage-bait to maximize ad views".
For example many definitions include the requirement that an algorithm has to terminate for every input. And I suspect that there are probably some bugs lurking somewhere in the HN codebase that make it go into the occasional infinite loop. So technically it's not an algorithm by definition.
(And even weirder, because I just suspect it might have those bugs, but I don't know for sure, I have to admit that I don't know whether HN is powered by an algorithm.)
I agree with you that for practical definitions we can go by a definition that's essentially: 'by algorithm we just mean "computer program", but we want to focus on the abstract things it's doing, and not details of the concrete implementation.'
The formal definition of algorithm doesn't really require that a human can inspect them, nor understand nor explain, or does it?
> (Which in some contexts is a legal requirement.)
That's another can of worms. Which contexts are you talking about?
Instead of having an explicit algorithm to do the work of surfacing ragebait posts, that work is done by the users themselves.
What is notable, though, is that things don't necessarily have to be that way, in my experience, the Polish Mastodon community does far less of this than the English one.
Like when people get a random post or video served to them they found interesting they'll say "the algo decided I should see this today"
Content creators will discuss what they need to create for "the algo" to like and promote them.
btw: The Malgorithm does actually exist, and ironically is the name of a electronic music device that applies bit-crushing (undersampling and/or bit resolution reduction) effect to audio signals, that is, it mostly makes the signal sound worse although it can be used creatively, which however occurs very rarely in pop music.
That's the only kind of algorithm people have been exposed to, so they hate the term.
At the time everyone was complaining that Facebook was just "people posting their lunches" and from that PoV I thought it was a great addition to promote the things people found important in their lives instead of the noise.
Of course that didn't last long.
"And to be extra clear, "only show posts from people I follow, in chronological order" is an algorithm."
Apparently people understand different things by "algorithm". I also use the general one and not "algorithm" as a special algorithm that tries to find things I might like based on my past interactions, but mainly tailored to keep my engagement high so I watch more ads"
I would like the possibility of creating and tweaking my own algorithm for my feed.
People here are wilfully ignoring the proper context and meaning of the term as used, even though no one has any trouble understanding what is meant. You even spelt it out perfectly, demonstrating that there isn't any genuine miscommunication happening:
> "algorithm" as a special algorithm that tries to find things I might like based on my past interactions, but mainly tailored to keep my engagement high so I watch more ads".
I do think the internet would be a better place with more openness about those magic black boxes, even if it's just an ability to tweak it yourself without having to do some arcane incantations and rituals (ever gotten your YouTube recommendations completely fucked? How do you unfuck them?).
> I would like the possibility of creating and tweaking my own algorithm for my feed.
This would be really useful, and I think actually should be a right - like data portability. However it doesn't address the issue with the default view not being linear, and hence breaking the utility of such services as a public or community notice board.
> "And to be extra clear, "only show posts from people I follow, in chronological order" is an algorithm."
An algorithm is being used to serve content in that context, but content is not being removed, substituted, inserted or filtered by an algorithm in (the platonic version) of displaying a linear chronological feed. The are the issues which 'the algorithm' has been criticised for in the modern context. If we can acknowledge that's the intended usage here then we can move beyond semantics.
What happened on Facebook in 2012 is that Facebooks product changed from being one that served the affordance 'connecting people', to one that effectively divided people and charged to connect them in more limited ways. The impact of that one change (on FB and mirrored on other services) in creating the sensitisation and polarisation which followed, as well as removing the one major utility of social networks beyond pure entertainment, cannot be overstated.
One of the most important algorithms, google search, has become crap. Social media algorithms have become crap.
Average people hate “the algorithm” because it was a trusted friend(ly tool) ands it has become crap and betrayed them!
If we, technologists, want people to love and use algorithms, we have a duty to avoid making them become horrible or useless for people.
These people are just winging for followers IMO.
The traits required to become a billionaire are not the traits required to run a social network. This should be obvious by now. Zaphod Beeblebrox had no actual power for a reason.
Second biggest is that while a PDS does decentralize the data, I belive bsky.app is still the place providing the 'frontend' that makes it all work.
ICANN is rather centralized. This is the biggest concern I have with ATProto, I would have expected it to work over P2P i.e. IPNS, or even some sort of a blockchain rather than a centralized web server.
One could start their own DNS server with different records than the ICANN ones, thus ignoring their authority.
As long as that possibility exists, it’s fine.
There are many alternatives to (ICANN) DNS, but since none have support built into major browsers, they end up being a pain to use, which hampers adoption.
The most successful is probably the Onion network and that's far from mainstream.
It’s usually the force of large, powerful (or early) organizations.
Realistically I’m okay with a single overwhelming popular entity as long as I, as an individual, can choose have my alternative.
Thank you. ATProtocol is really cool, but I share some concerns about the centralized resolution of identities to custom servers. If I understand Bluesky correctly:
When you follow users on Bluesky (even those on a hosted custom server), atprotocol allows you to follow them by a "URL" (DID:web) but by default you're following them by their DID:PLC, a kind of Decentralized Id that is resolved via an equivalent to a "name server" (see: https://github.com/did-method-plc/did-method-plc).
You give that name server a DID json representing a user you want to follow or are following, it will tell you the IP of the (custom atproto) server where that user's posts and replies are. By default Bluesky apps only know about PLC nameservers that are in Bluesky's registry.
And so even if I'm using custom hosting if Bluesky PLC nameserver delists my DID (or my server?) most bluesky users will be unable to find me.
Bluesky is theoretically interested in moving this nameserver under a nonprofit consortium structure but no one is working on it, and BlueSky for years hasn't gotten around to it.
My questions are:
1. Is that right, or are there any promising nascent efforts to create a nameserver registry under a consortium structure?
2. Is it fair to ask users, potential users and developers to take it as an article of faith that BlueSky will fully support and partner with such a consortium (since it hasn't helped set one up already in the years of its development) and steer ATProto's development without self-interest? What about in light of Bluesky features that have not been "backported" to ATproto?
3. Once Bluesky has a large enough userbase (far beyond those that joined just for the decentralization) and is a private company, are its incentives aligned with increasing centralization to lock those users in or decentralization to allow them to leave?
1. Basically, yeah. That said, I still think it may be a bit early to do this. A consortium would be useful if it was meaningfully independent of bsky, so you need to grow and gain interest first. Otherwise the “independent group” would be run by the same people, which is pretty meaningless. Plus, working on that means les time for working on other things. I would expect to see this happen once there’s another non-toy atproto application, and for representatives from it to be involved too. Before then feels premature to me, but I can appreciate others may feel differently.
2. I do. The team has continually set out a vision, and then executed on it, over and over. Including following through on things that actively reduce their control over things. Tons of folks asked a similar question previously: “they’re saying that you’ll be able to host your own PDS someday, but do you trust them to actually ship that and not just say they’re gonna a do it and put it off forever and keep control?” And then they shipped it.
3. Any application has semantics built on top of the underlying protocol: that’s what an application is, in some meaningful sense. But I do agree that without independent governance for atproto, doing things like that could stifle other users of atproto, sure. We’re back in the same realm as 1, imho. I’m following the devs of various other apps and none of them have expressed that they think bsky is hoarding the goods so far, at least.
I also enjoyed Brian Newbold 's post from early August taking inventory of how Bluesky is doing so far at being decentralizable, and what's remaining,
https://bnewbold.net/2024/atproto_progress/
There's some wildly negative often wildly in my view inaccurate posts down below slinging all kinds of things. So much of it is so wildly off base.
Atproto dev has a ton of strong wins already, and there's been a massive influx of dev interest in the past few weeks. Really looking forward to seeing this ecosystem bloom. I feel like we are at an inflection point.
For those of you who are interested in solving this my first suggestion is to read the Scuttlebot docs which are still up at: https://scuttlebot.io/
Sometimes I think about a retro Scuttlebot revival. If you want to set sail on this kind of project, contact info is in my bio.
AT Protocol works like the Web, where each user is a website and each application is a search engine. The apps crawl the network of hosts and aggregate activity. We have over 100 outside hosts and at least 3 aggregating apps out there. It’s a different model than ActivityPub, which is more akin to email.
We never said no algorithm. I don’t know where that meme comes from. We have an open system for algorithms, which we and 3p devs can operate. We have a default algorithm for every user called Discover. It was one of our main concerns to have an answer to algorithms in a decentralized network.
For DID PLC, the likely solution is to move the registry into a nonprofit which will maintain it, similar to ICANN. We also support the Web DID method, and if folks like this remain concerned we’re open to other DID methods. It’s important, but roughly similar to DNS or TLS issuers; supporting infra to the application network.