NFL teams can't use Bluesky
theverge.com
theverge.com
I'd love to know why they needed a custom contract in the first place. My company doesn't have a "deal" with Twitter but we still post there.
No one is afraid here, they are just businessmen doing business.
Buy why? What control do they need beyond normal copyright? And what does the NFL gain from not being able to reach tens of millions of Bluesky users?
Money. Content partners pay to have NFL content on their platforms, NFL content is highly valuable, so the NFL doesn't want anyone else to monetize it without the NFL getting their cut.
That is a lot of words to just say: money.
I suspect it has to do with the permission to share highlights from the match in their official accounts. Probably those videos belong to the broadcasters and not to the teams themselves. One of the links from the article [1] says that the agreement provides X users with highlights such as touchdowns.
This does not mean that not being able to create an account on a different network is a dumb restriction, even if it's for sharing news or pictures of the team on special days and not videos from the games.
[1] https://deadline.com/2024/04/nfl-x-twitter-renew-content-par...
https://deadline.com/2024/04/nfl-x-twitter-renew-content-par...
[^0]: https://exhibitions.ushmm.org/propaganda/german-radio-the-pe...
But my guess is Twitter and sites like that pay for the NFL to be on their site. Since Bluesky is decentralized, no place or one to extort $ from.
There are also 3rd party algorithms, moderation, and interfaces you can mix and match
https://www.theverge.com/2023/10/23/23928550/posse-posting-a...
Do you think WhiteWind fits into the POSSE model because your content lives in your ATProto database?
If I understand what's going on with WhiteWind it's taking advantage of another dimension of federation which the "fediverse" doesn't address, which is identity. It seems it's a blog service that is linked to my ATProto account that anyone can use so long as they have one.
I'll make the case that the fediverse style of federation has a low level of trust for this sort of things. If I log on to a service that uses Facebook or Bluesky or whatever for identity, there's always the risk that the people who run the service can let somebody else log in. I've got some trust in mastodon.social but plenty of small server administrators in the fediverse have demonstrated that they can't be trusted.
https://github.com/whtwnd/whitewind-blog/tree/main/lexicons/...
I believe each user gets a dedicated sqlite database, or at least a dedicated repo. I recall reading somewhere about the implementation moving to use sqlite
Of course it is all hidden from view, there is a merkle tree involved, and you probably want to use a higher level client than SQL
This talks about why SQLite and not Postgres
https://github.com/bluesky-social/atproto/discussions/2287
Repository spec:
https://atproto.com/specs/repository
Small program to export:
https://github.com/bluesky-social/cookbook/tree/main/go-repo...
https://github.com/mary-ext/atproto-scraping
The number seems to double every few months. It's about as decentralized as Mastodon with its handful of servers controlling most of the network and a long tail of small and single user independent instances. The only difference is recovering from bluesky's official instance (bsky.app) dying is you would have to connect to a different Bluesky instance or convert your PDS data into a website, or port it to some other social media software like Mastodon. I wouldn't be surprised if there are already projects underway to make it possible.