this post was submitted on 12 Nov 2023
66 points (100.0% liked)
Technology
37707 readers
398 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
They chose not to after researching options. Pretty sure they decides account portability was a key feature needed and AP doesn''t do this. As in taking your account and all your posts and data witj you to a new server. I assume there is a technical reason why this would be very difficult to add to AP/Mastodon otherwise they could have just added it themselves.
Yeah the not being able to fully move your account and all its history is one of the biggest shortcomings of AP for me. I hope they shore that up eventually.
100% agree, without it, the decentralization aspect is severely weakened
It's nothing to do with that, they made the AT protocol because is structured in a way that ensures that bluesky (the company) will always control the network. They wouldn't be able to keep control with ActivityPub, it's the same reason Threads will never implement it.
All the stuff about account portability is a distraction. Think about it: where would one move an account to anyway? Another BS node? Why? Unlike Mastodon instances there is no functional difference.
You clearly haven't read the docs
Here's a doc for ya: https://rys.io/en/167.html
This line is self contradicting
3rd party feeds and recommendations and discovery already exists. They are also not dependent on the continued existence or openness of the bluesky servers. You can control your own experience and it's easy to find and switch between feeds. Having more subscribers to your feed doesn't make you more powerful in the context of network effects. If people stop looking your feed they'll dump it.
Also, node operators have full control of what they forward to clients. They can absolutely apply moderation filters, and this is one of the expected means for such nodes to market themselves to their communities - "we have default feeds and moderation which suits your community".
Nonsense, the network uses relay servers which acts as open CDN servers and the firehose feed is open AND 3rd party hosted feed builders already exists (and they're open source so you can copy them), you don't need to waste duplicate work on building datasets. This network is cooperative. It has absolutely no winner-takes-all effects, it explicitly encourages division of labor and mix-and-matching multiple 3rd party services.
Then use web-DID which already is fully decentralized
Jack is not involved with bluesky anymore, he's in nostr land now. He doesn't have majority on the board and isn't influencing development.
Moderation tools like this is in the works, it's not complete yet. Mute/block filters already exists, and label services for moderation are being worked on
A whole lot of directly false nonsense and irrelevant arguments and ignorance of what the devs are working on