Cris_Color@lemmy.world
on 01 Sep 00:40
nextcollapse
Thats a super cool visualization! This might make a really cool post for !dataisbeautiful@lemmy.world! Maybe a screenshot with a seperate link to the site
Actually there is a legal definition, a Public Benefit Corporation has statutes in its articles of incorporation which legally commit the company to pursue a set purpose which supersedes the fiduciary responsibility of the corporation to shareholders. This is important because it provides some degree of legal protection from activist shareholders suing the company for making spending or policy decisions which don't directly maximize shareholder value. The body of law around this issue is still relatively murky, but some defense is better than none at all.
For example, shareholders could attempt to sue BlueSky into increasing advertising placement or data sales functionality intothe core platform to increase company revenues, but if that is at odds with their stated public benefit purpose the legal team for BluSky would have grounds to attempt to dismiss the suit on the grounds that the shareholders purchase the shares under the explicit understanding that these functions would be subordinated to the public benefit goals of the platform.
No almost all of that is misconception. Shareholders can sue normal companies and âPBCâ for not maximizing shareholder value. PBC are still legally required to cater to shareholders interests. Legal scholars say that PBCs do not provide any protection against shareholders suing and data shows it does not stop profit maximizing behavior. Its pure marketing.
General_Effort@lemmy.world
on 01 Sep 09:44
collapse
Be strong now. Mastodon is a gGmbH. Thatâs the German version and translates to public benefit limited liability corporation.
Yes but we like mastodon because theyâre open and if they fuck up we can move away at any time. Bluesky is completely closed except the protocol and the network is fully centralized. Theyâre just waiting until they have enough marketshare to enshitify.
pineapplelover@lemmy.dbzer0.com
on 01 Sep 06:21
nextcollapse
Not at all. The issue with Blueskyâs âfederationâ is, you canât really set it up at home, you need thousands of dollars and itâs not really accessible.
Search up âMastodon instancesâ and then âBluesky instancesâ you see like thousands for Mastodon and only the official one for Bluesky. Itâs marketing gimmick for the mainstream normies who want to pretend they have freedom but in reality theyâre just jumping on the train with the billionaire who runs it.
Search up âMastodon instancesâ and then âBluesky instancesâ
Bluesky has a different architecture, there are no âinstancesâ, itâs PDSs, relays and AppViews, all of which can be and are already being self-hosted.
theyâre just jumping on the train with the billionaire who runs it
If you mean Dorsey, he has had nothing to do with Bluesky for well over a year now because he resented them implementing moderation tools
Tollana1234567@lemmy.today
on 01 Sep 06:41
nextcollapse
bluesky is twitter without the nazification by musk.
hal_5700X@sh.itjust.works
on 01 Sep 07:14
nextcollapse
Itâs Dorsey era twitter. Full of crazies.
ICastFist@programming.dev
on 01 Sep 15:22
collapse
[Edit: I see the problem, even with a self-hosted instance of 1, when you comment on posts in other instances that data is no longer held on your server, so you don't own it and can't control it directly, is that right?]
So as I understand it the big "advantage" of ATProtocol is the account portability via DID, however this is at the sacrifice of actually hosting an ATProtocol being extremely data heavy.
This has made me very curious about self-hosting ActivityPub (meaning an instance of 1 user), it would seem like focusing development on a client that makes it as close to as easy to self-host an instance as it is to join one would solve the issue of accountability portability, as you literally own all the data and rights when you self host. The Major challenge I see there is security, where experienced admins for larger instances should have some level of cybersecuroty expertise while the average use may have little to none. But then focusing group effort on auto-updating the client and the default settings of the client to maximize security would solve that issue it would seem?
So what am I missing? Other than hosting costs, what else is deferring a self-hosted-first development approach for the Fediverse?
Is it actually that AP development fundamentally believe moderation should be handled at the admin/instance level, and self-hosting makes moderation more difficult and less directly authority based?
Publicly shared blacklists and whitelists would seem the natural fit for a self-hosted-first network, akin to adblock and horizontal.
Edit: I see the problem, even with a self-hosted instance of 1, when you comment on posts in other instances that data is no longer held on your server, so you donât own it and canât control it directly, is that right?
The âproblemâ is also going the other way around. If a large instance is sharing data with your single user instance, they ultimately cannot control what you do with it.
The same is true if you just scrape the website.
ICastFist@programming.dev
on 01 Sep 15:30
collapse
Isnât that a non-problem? I mean, afaik, you cannot control any data after itâs sent. If I send you an email with an attachment, I cannot stop you from forwarding it to everyone you know, nor can I stop you from editing it before forwarding. I guess it becomes a problem of reliability, then, which is only a problem if the original source is unavailable - which is not that uncommon in the fediverse.
It is a "problem" if your goal is full ownership and control over your user interactions and data footprint. ATProtocol in principle achieves this, you can delete or move your account and all your user interactions will be deleted or follow you (meaning edit permissions, full access to all the posts/comments, follows, updoots, etc.). The cost of this is a very high data load for the host, though I'm still not clear on exactly why it is so much more data intensive, is it the size of lookup instructions between hosts in addition to the actual markdown?
General_Effort@lemmy.world
on 02 Sep 13:20
collapse
[Edit: I see the problem, even with a self-hosted instance of 1, when you comment on posts in other instances that data is no longer held on your server, so you donât own it and canât control it directly, is that right?]
Not quite. Itâs more like Bluesky works, but also not quite.
First, a note on the idea of âyourâ data. The law gives people rights over certain data. For example, copyright gives people rights over certain content, which translates to rights over data encoding that content. You may think of a movie as being yours because you have the file on your device. The copyright holder still considers it their data and will therefore demand control over your device through DRM.
Rights over data always means rights over what other people do with their computers and devices. Unfortunately, Fediverse users are not very tech-savvy. They demand more rights and regulations and then condemn Big Tech for the predictable consequences. They pull on one end of the string and blame dark powers when the other end moves.
The European GDPR also creates rights over certain data. You have GDPR rights over all data that is directly or indirectly related to you. For example, if I write about the current French President, then Emmanuel Macron has GDPR rights over that data, even if I donât mention him by name. Of course, his rights will be limited by freedom of information. Also, these rights are rarely recognized outside of Europe.
What legal rights you have over data depends on your location. Copyright is internationally recognized, but its precise reach depends on location; eg the US has Fair Use. Even at a specific location, those rights depend on context, with a lot of gray area. This cannot be implemented technically.
With Lemmy itâs like this: When a user on an instance subscribes to a community, all (recent-ish) posts and comments in that community are downloaded to that instance. Users on that instance are served from their own instance.
Generally, a Fediverse instance keeps a copy of whatever data its local users might need. If your instance was the only source for some data, then every user in the whole world needing it would have to access your server every time they want it. Every user whether registered or unregistered would hit your server every time they reload. If a server buckles under the strain, you just get missing data. It just wouldnât scale.
Bluesky has Personal Data Servers (PDSs) for that role. Those are the definitive store of some userâs data. This can be self-hosted easily. The data from all users is aggregated by a ârelayâ, If a PDS is like a personal web server, then a relay is like a search engine. Thatâs the one that you canât self-host; takes big time capital expenditure.
I donât think the Fediverse has a solution for this. Imagine Mastodon or Lemmy with 100M+ users. How do you find stuff? Well, making a crawler and search engine for the Fediverse would be simple. But that would also take major capital expenditure.
The Bluesky relay combines all activity into the âfirehoseâ. Anyone can write apps that get data from the firehose and present them to users. When Bluesky blocked Mississippi, that meant that the official Bluesky App did that. Other Apps still work in that state.
Final bit: When you self-host, you need to be your own legal department. When you use a service, you are shielded to some degree. Eg when you infringe copyright, a social media service will usually just take it down. If you infringe copyright on your web server, or even via torrent, you may get a pretty hefty bill.
Fedi-users cheer when Meta gets sued or settled with a huge fine. Well, good luck running your own Facebook server. Fedi-users mostly arenât very tech-savvy but when it gets to law, they are positively delusional.
threaded - newest
Thats a super cool visualization! This might make a really cool post for !dataisbeautiful@lemmy.world! Maybe a screenshot with a seperate link to the site
Thanks for posting this! đ
Everytime I see bluesky PBC I have to resist the urge to rant. There is no such thing as a public benefit corporation. Its just marketing BS.
Actually there is a legal definition, a Public Benefit Corporation has statutes in its articles of incorporation which legally commit the company to pursue a set purpose which supersedes the fiduciary responsibility of the corporation to shareholders. This is important because it provides some degree of legal protection from activist shareholders suing the company for making spending or policy decisions which don't directly maximize shareholder value. The body of law around this issue is still relatively murky, but some defense is better than none at all.
For example, shareholders could attempt to sue BlueSky into increasing advertising placement or data sales functionality intothe core platform to increase company revenues, but if that is at odds with their stated public benefit purpose the legal team for BluSky would have grounds to attempt to dismiss the suit on the grounds that the shareholders purchase the shares under the explicit understanding that these functions would be subordinated to the public benefit goals of the platform.
No almost all of that is misconception. Shareholders can sue normal companies and âPBCâ for not maximizing shareholder value. PBC are still legally required to cater to shareholders interests. Legal scholars say that PBCs do not provide any protection against shareholders suing and data shows it does not stop profit maximizing behavior. Its pure marketing.
Be strong now. Mastodon is a gGmbH. Thatâs the German version and translates to public benefit limited liability corporation.
Yes but we like mastodon because theyâre open and if they fuck up we can move away at any time. Bluesky is completely closed except the protocol and the network is fully centralized. Theyâre just waiting until they have enough marketshare to enshitify.
Not at all. The issue with Blueskyâs âfederationâ is, you canât really set it up at home, you need thousands of dollars and itâs not really accessible.
Search up âMastodon instancesâ and then âBluesky instancesâ you see like thousands for Mastodon and only the official one for Bluesky. Itâs marketing gimmick for the mainstream normies who want to pretend they have freedom but in reality theyâre just jumping on the train with the billionaire who runs it.
IMO, setting it up at home is not the bar for decentralization. I donât think itâs even practical to run your own self-hosted fediverse server.
I think we can get just about all the same benefits of decentralization at the scale of the city.
Thatâs exactly where I set the bar.
Same here.
What makes it impractical? The modelâs been working here for years.
no you donât
Bluesky has a different architecture, there are no âinstancesâ, itâs PDSs, relays and AppViews, all of which can be and are already being self-hosted.
If you mean Dorsey, he has had nothing to do with Bluesky for well over a year now because he resented them implementing moderation tools
bluesky is twitter without the nazification by musk.
Itâs Dorsey era twitter. Full of crazies.
Give it timeâŚ
[Edit: I see the problem, even with a self-hosted instance of 1, when you comment on posts in other instances that data is no longer held on your server, so you don't own it and can't control it directly, is that right?]
So as I understand it the big "advantage" of ATProtocol is the account portability via DID, however this is at the sacrifice of actually hosting an ATProtocol being extremely data heavy.
This has made me very curious about self-hosting ActivityPub (meaning an instance of 1 user), it would seem like focusing development on a client that makes it as close to as easy to self-host an instance as it is to join one would solve the issue of accountability portability, as you literally own all the data and rights when you self host. The Major challenge I see there is security, where experienced admins for larger instances should have some level of cybersecuroty expertise while the average use may have little to none. But then focusing group effort on auto-updating the client and the default settings of the client to maximize security would solve that issue it would seem?
So what am I missing? Other than hosting costs, what else is deferring a self-hosted-first development approach for the Fediverse?
Is it actually that AP development fundamentally believe moderation should be handled at the admin/instance level, and self-hosting makes moderation more difficult and less directly authority based?
Publicly shared blacklists and whitelists would seem the natural fit for a self-hosted-first network, akin to adblock and horizontal.
The âproblemâ is also going the other way around. If a large instance is sharing data with your single user instance, they ultimately cannot control what you do with it.
The same is true if you just scrape the website.
Isnât that a non-problem? I mean, afaik, you cannot control any data after itâs sent. If I send you an email with an attachment, I cannot stop you from forwarding it to everyone you know, nor can I stop you from editing it before forwarding. I guess it becomes a problem of reliability, then, which is only a problem if the original source is unavailable - which is not that uncommon in the fediverse.
It is a "problem" if your goal is full ownership and control over your user interactions and data footprint. ATProtocol in principle achieves this, you can delete or move your account and all your user interactions will be deleted or follow you (meaning edit permissions, full access to all the posts/comments, follows, updoots, etc.). The cost of this is a very high data load for the host, though I'm still not clear on exactly why it is so much more data intensive, is it the size of lookup instructions between hosts in addition to the actual markdown?
Not quite. Itâs more like Bluesky works, but also not quite.
First, a note on the idea of âyourâ data. The law gives people rights over certain data. For example, copyright gives people rights over certain content, which translates to rights over data encoding that content. You may think of a movie as being yours because you have the file on your device. The copyright holder still considers it their data and will therefore demand control over your device through DRM.
Rights over data always means rights over what other people do with their computers and devices. Unfortunately, Fediverse users are not very tech-savvy. They demand more rights and regulations and then condemn Big Tech for the predictable consequences. They pull on one end of the string and blame dark powers when the other end moves.
The European GDPR also creates rights over certain data. You have GDPR rights over all data that is directly or indirectly related to you. For example, if I write about the current French President, then Emmanuel Macron has GDPR rights over that data, even if I donât mention him by name. Of course, his rights will be limited by freedom of information. Also, these rights are rarely recognized outside of Europe.
What legal rights you have over data depends on your location. Copyright is internationally recognized, but its precise reach depends on location; eg the US has Fair Use. Even at a specific location, those rights depend on context, with a lot of gray area. This cannot be implemented technically.
With Lemmy itâs like this: When a user on an instance subscribes to a community, all (recent-ish) posts and comments in that community are downloaded to that instance. Users on that instance are served from their own instance.
Generally, a Fediverse instance keeps a copy of whatever data its local users might need. If your instance was the only source for some data, then every user in the whole world needing it would have to access your server every time they want it. Every user whether registered or unregistered would hit your server every time they reload. If a server buckles under the strain, you just get missing data. It just wouldnât scale.
Bluesky has Personal Data Servers (PDSs) for that role. Those are the definitive store of some userâs data. This can be self-hosted easily. The data from all users is aggregated by a ârelayâ, If a PDS is like a personal web server, then a relay is like a search engine. Thatâs the one that you canât self-host; takes big time capital expenditure.
I donât think the Fediverse has a solution for this. Imagine Mastodon or Lemmy with 100M+ users. How do you find stuff? Well, making a crawler and search engine for the Fediverse would be simple. But that would also take major capital expenditure.
The Bluesky relay combines all activity into the âfirehoseâ. Anyone can write apps that get data from the firehose and present them to users. When Bluesky blocked Mississippi, that meant that the official Bluesky App did that. Other Apps still work in that state.
Final bit: When you self-host, you need to be your own legal department. When you use a service, you are shielded to some degree. Eg when you infringe copyright, a social media service will usually just take it down. If you infringe copyright on your web server, or even via torrent, you may get a pretty hefty bill.
Fedi-users cheer when Meta gets sued or settled with a huge fine. Well, good luck running your own Facebook server. Fedi-users mostly arenât very tech-savvy but when it gets to law, they are positively delusional.
europe.pub/post/4092620
Post about Bluesky decentralization.
vger.to/europe.pub/post/4092620
Those sevens are weird, what a weird font