While there's plenty about AT Protocol/Bluesky I find un-ideal, in this case I believe Paul is referring to the aspect of the protocol that allows you to build your own algorithm to curate posts.
For example, there's a 3rd party Bluesky web client called Skyline that allows you to curate your feed like so: 
I think it's great to allow users themselves to tune their feeds the way they want, and I'm sure is something we'll be seeing in nostr clients too.
#history #ancientgreece
https://classicalwisdom.substack.com/p/12-ancient-greek-terms-that-should
Well the Iranian government can’t do anything if an Iranian person living in the US says something they don’t like.
Are they using it from Iran, or are they posting in Farsi but from outside of Iran?
Just because i thought it’d be hilarious, here’s a bridged nostr profile of Paul Frazees Bsky profile: #[1] nostr:note17ynepnueffzfff37eyahjjffdw95gyndyt7pdrvpwu4k9mvdkq4qh3k7n9
“alf mini cluster” lmao
So #[0] posted a blog post about bluesky that ruffled some feathers: https://fiatjaf.com/ab1127fb.html
This triggered a long skeet stream reply from bluesky developer Paul Frazee: https://staging.bsky.app/profile/pfrazee.com/post/3jv72j3fp6g2r
This then caused me to write up some thoughts:
The world of decentralized protocols is gaining momentum, and it's exciting to see projects like Nostr and Bluesky at the forefront. Many of us have dedicated years to developing these protocols, and now they're capturing global interest. I've been tracking various decentralized social media protocols for a long time, and if you're interested, you can find my comprehensive database of open social media protocol projects here: https://airtable.com/shri7e7EHoTi0cEjO
Nostr, at_protocol, and other projects take inspiration from Secure Scuttlebutt, which I had the pleasure of working on alongside talented individuals like @pfrazee and @jay. Nostr is a slightly modified version of Scuttlebutt, while at_protocol represents a more significant reimagining. At_protocol borrows ideas from the IPFS ecosystem and W3C DID standards, while Nostr incorporates concepts from Bitcoin technology (not a blockchain or cryptocurrency project). Both projects have received substantial support from #[1] , who funds them but doesn't control their direction.
Nostr began as a humble side project, growing organically as developers adopted it. In contrast, Bluesky started with significant press and a high-profile search for a team lead, taking years to evolve from an idea to a funded project. Bluesky's community experienced challenges that led to a split, and the original community renamed itself https://dsocialcommons.org/. Nostr, on the other hand, never encountered such issues, with developers contributing to the project independently.
The two projects represent different approaches to open source development: the cathedral model (Bluesky) and the bazaar model (Nostr). Both have seen success, but I must express my disappointment with Bluesky's choice to follow the cathedral model. Despite my frustration, I have great admiration for the team behind Bluesky and the work they're doing. However, Bluesky employees maintain full control over the at_protocol, leaving little room for external contributors.
In contrast, Nostr provides an open platform for contributions, enabling me to create an app (nos.social) and write specifications that are openly debated: https://github.com/nostr-protocol/nips/pull/457. Bluesky's code is indeed open source, but their development process is not. This is reminiscent of how Safari's WebKit or Android operate as open source projects without truly embracing the open source development methodology.
Recently, I expressed concerns about Bluesky as it currently operates as a single unified network. Friends advised me to take a step back and give the team time. I experimented with their Indigo PDS server and found it promising. I believe that the at_protocol will eventually become an open, multi-server protocol. The people behind Bluesky have a long history of working on open protocols and are not developing this technology to create a new, closed ecosystem.
On a personal note, I feel a stronger social connection to Bluesky's early adopter community but appreciate Nostr's openness for contributions. I could potentially create an at_protocol client, but making substantial contributions to the Bluesky protocol seems reserved for employees and select advisors. Therefore, I choose to invest my time and effort in open projects. I firmly believe in Conway's law, which states that the structure of the organization building a technology will shape the technology itself.
I believe @fiatjaf might be overly critical of Bluesky. He had the luxury of working in obscurity without the pressure of media attention while figuring things out. In contrast, Bluesky faces high expectations and the responsibility to "replace Twitter." The stress that the Bluesky team endures while trying to develop their project under the watchful eyes of many likely contributed to their adoption of the cathedral model of open source. I empathize with the challenges they face in this environment.
Much of the internet was built using the bazaar model, consisting of small pieces loosely joined. This approach gave us the web and numerous other systems we use today. Bluesky's design-driven model is more meticulously architected, but it reminds me of Java and XML (no offense intended).
I believe that these networks can interoperate. I already communicate between the fediverse and Nostr daily, and while it's not perfect, it mostly works. I'm optimistic that we'll achieve similar interoperability with at_protocol once the system becomes more open. It is essential to recognize the strengths and weaknesses of both approaches and to appreciate the incredible work and progress made in both projects. As the world of decentralized protocols continues to grow, I remain hopeful for a future that embraces collaboration and openness.
I wanted to write a thoughtful reply, but instead all I can think about is "skeet stream" 😂
#CleanEnergy #infrastructure
https://electrek.co/2023/05/04/us-largest-clean-energy-infrastructure-project-sunzia/
There already is somewhat of a hacky Nostr-Bluesky bridge I've been using. For example, here's Bluesky CEO Jay Graber's profile on nostr:
nostr:npub1fnduppkq0yksf8pk85n7lrxlh8wej7y8lj063qaq4ypkp90qkm2qzgqhhn
and here's how it's done:
nostr:note1y090cmd666cz6s9eczaledzmc4lduasq6w2taj5vd8udlgwnkv0qh7kamn
A good write up by nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 . Open protocols like Nostr and the ability for users of one client to view o another will bring society closer together. Relays make it an actual safe space for society. A proper decentralised system will reduce the extremism that plagues the US and globally.
https://fiatjaf.com/ab1127fb.html
Being in a a bubble of one ideology is super dangerous. Centralised system expect it. Even if it was never intended by the founders, gov’t will intervene to ensure they reap. AT protocol has to remain independent from Bluesky. This said with good intentions so that it works as the vision originally was.
A proper decentralised system like Nostr will reduce the extremism that plagues the US and globally.
I was thinking about this the other day, that the "ideology bubble" problem is an area where the concept of "follow topics vs follow people" may have some strengths.
Fundamentally, people use Twitter/Mastodon/Nostr/Bluesky/etc because they want to find and follow people who post about the topics they're interested in.
When the user experience is designed around following people, what tends to happen is we say "I like what this person says about this topic I'm interested in, I'll follow them". That person we follow will then naturally reshare posts from other people who post about that topic, but also with the same views on that topic.
This inevitably creates the feedback loop that creates ideology bubbles in our feed. If you instead follow the topic itself, your feed will (in theory) be anyone who posts about that topic, regardless of viewpoint on it.
I'm sure it's more complex than that, but I'm interested to experiment further on the concept, hence the whole Agora thing!
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 here's bsky team member Paul Frazee's response to your blogpost on Bluesky, if you're curious
Nope but i wouldn’t be surprised if the new 4Runner will resemble the new tacoma front
"The Alhambra Decree was an edict issued on 31 March 1492, by the joint Catholic Monarchs of Spain (Isabella I of Castile and Ferdinand II of Aragon) ordering the expulsion of practicing Jews from the Crowns of Castile and Aragon and its territories and possessions by 31 July of that year."
2024 Tacoma truck leaked, I'm liking the more aggressive looks!#cars #carporn
Expulsions of Jews in Europe from 1100 to 1600#mapporn #history
#google #smarthome
