A Look at Bluesky
juliette.page
A Look at Bluesky
1–10 of 143 posts
Re: A Look at Bluesky
#2Thanks for sharing. I think Bluesky is pretty interesting (got my invite from Twitter :) )
Re: A Look at Bluesky
#3I'm not 100% sold on ATProto, but the fact that my identity and content can live separately from an instance is an insanely huge advantage over ActivityPub. I do not want to run my own Mastodon server (though I do) but I also don't want to use someone else's server and put my account at the mercy of the operator. It's maddening to think about how I could build a following or amass a ton of quality posts, only for the server to shut down or pull a Twitter. I simply can't stand the thought of it.
If ActivityPub wants to keep riding the wave it has now they should start investigating ways to support this. I think more and more people are getting fed up with centralized platforms / not owning their data.
Re: A Look at Bluesky
#4[dead]
Re: A Look at Bluesky
#5Right now everyone on Bluesky is on centralized instances run by the devs, and are subject to widespread censorship by same.
I know of no way at this time to run one's own instance or federate.
Re: A Look at Bluesky
#6Right now everyone on Bluesky is on centralized instances run by the devs, and are subject to widespread censorship by same. I know of no way at this time to run one's own instance or federate.
Why does this constantly come up as some kind of gotcha? The protocol is under active development, and Bluesky serves as a reference implementation.
Re: A Look at Bluesky
#7Right now everyone on Bluesky is on centralized instances run by the devs, and are subject to widespread censorship by same. I know of no way at this time to run one's own instance or federate.
Why does this constantly come up as some kind of gotcha? The protocol is under active development, and Bluesky serves as a reference implementation.
It comes up because right now Bluesky functions exactly like a worse Twitter (also centralized).
It has to be better somehow, and the whole selling point is decentralization to sidestep the possibility of recreating the current Twitter fiasco.
That goal is not yet achieved, which means it's below parity.
Re: A Look at Bluesky
#8With the current Twitter debacle, I think self-hosting my "notes about interesting things" (aka tweets) in a way it is accessible via the web, activitypub, bluesky and RSS might be the best way.
Is anybody already doing this? It shouldn't too be hard. Just throw all the notes into a directory and add some code which replies to the different types of requests.
I guess the best way to get ones tweets out of Twitter is the "Download an archive of your data" thingy in the settings?
Re: A Look at Bluesky
#9I'm not sure what to make of this actual submission;
> A problem with the system of having a domain as a username is that people can claim it who don’t have access to that username.
That was a bug, and is not generally speaking, the case. You must have the ability to alter the DNS records for the domain you wish to claim.
> However, that means interactions, such as user likes, blocks, follows, etc are all public. With no means to make them private. Which could lead to harassment!
It could also lead to the enlightenment of man, if we're just making random claims without explaining ourselves...
> But runs into the problem of algorithms being hijacked to show inappropriate/offensive/bigoted content.
Posts on the AT Proto can be labeled by whatever labeling service you prefer, including Bluesky itself. You can then use your preferred labeling to filter out labels you don't want, or subscribe to a feed that does that for you.
> But also it’s a group of overly complicated specifications that could’ve just been extensions to the ActivityPub protocol rather than a whole new protocol!
I don't think, "AT Proto is too complex, use ActivityPub instead" is a reasonable claim at all. The problem is a complex one, and AT Proto in particular is not even out yet.
Honestly, I can barely understand this "article". It's just a bunch of oversimplified (and sometimes outright wrong) statements about what AT Proto is, coupled with painfully misunderstood declarations that border on the illegible.
Re: A Look at Bluesky
#10Earlier quoted context omitted.
Why does this constantly come up as some kind of gotcha? The protocol is under active development, and Bluesky serves as a reference implementation.
It comes up because right now Bluesky functions exactly like a worse Twitter (also centralized). It has to be better somehow, and the whole selling point is decentralization to sidestep the possibility of recreating the current Twitter fiasco. That goal is not yet achieved, which means it's below parity.
Bluesky doesn't function at all, it's not public yet, over and over again the people working on it repeat this fact.