So much for the claims I read that it would be a more open platform. I can’t see how this possibly benefits the users.
The product is not open source and it is mainly controlled by a company through its servers and proprietary components. They own it. Even if they use some open protocols. They are about as open as OpenAI — they are not.
This is technically incorrect (the best kind of incorrect?). Bluesky is open source, with the exception of the discover feed algorithm, which they claim must remain secret to prevent it being manipulated. There are open-source replacements for that feed available, so it’s open enough that it is theoretically possible to spin up a Bluesky replacement, albeit impossibly expensive.
Coming at it from another angle though, the product in any commercial social media product is you, so in that sense you’re right: the product is not open source. Either way, open source code is not some panacea that erases all risk of commodifying its users. Bluesky is a great example because while it is open source, that in absolutely no way prevents them from tracking their users.
you’re right that this is likely to be used for tracking crap, but i wouldn’t write off the concept as only for that
for example, home assistant has https://my.home-assistant.io/ where you can set your home assistant URL and doc links (etc) link there, and then that site in turn automatically redirects to the correct place on your local home assistant
this could be used similarly by the fediverse: imagine my.join-lemmy.org where lemmy instances you’re not logged into redirected you to, which then in turn redirects to your home instance… that way, links across the web to lemmy would automatically redirect to your home instance
perhaps it’s not something that’s worth the trade off - centralising in some ways - but in federated platforms on the web it’s far from a write-off
So much for the claims I read that it would be a more open platform. I can’t see how this possibly benefits the users.
The product is
not open source and itis mainly controlled by a company through its servers and proprietary components. They own it. Even if they use some open protocols. They are about as open as OpenAI — they are not.This is technically incorrect (the best kind of incorrect?). Bluesky is open source, with the exception of the discover feed algorithm, which they claim must remain secret to prevent it being manipulated. There are open-source replacements for that feed available, so it’s open enough that it is theoretically possible to spin up a Bluesky replacement, albeit impossibly expensive.
Coming at it from another angle though, the product in any commercial social media product is you, so in that sense you’re right: the product is not open source. Either way, open source code is not some panacea that erases all risk of commodifying its users. Bluesky is a great example because while it is open source, that in absolutely no way prevents them from tracking their users.
Actually, you can host the App bit yourself, and piggyback off bluesky’s relay until another one pops up.
you’re right that this is likely to be used for tracking crap, but i wouldn’t write off the concept as only for that
for example, home assistant has https://my.home-assistant.io/ where you can set your home assistant URL and doc links (etc) link there, and then that site in turn automatically redirects to the correct place on your local home assistant
this could be used similarly by the fediverse: imagine my.join-lemmy.org where lemmy instances you’re not logged into redirected you to, which then in turn redirects to your home instance… that way, links across the web to lemmy would automatically redirect to your home instance
perhaps it’s not something that’s worth the trade off - centralising in some ways - but in federated platforms on the web it’s far from a write-off
They don’t need to redirect to click track. They could very easily do that on the front end and you wouldn’t even know it was being done.
Or we could start using ap:// links https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md