Completely agree, but there’s absolutely zero reason an entrepreneurial Bitcoin developer can’t fork one of the several popular open-sourced Bluesky clients and integrate zaps.
In the other direction, there’s no reason a nostr developer can’t integrate the Starter Packs that Bluesky has for user discovery.
You know the Bluesky/AT protocol world better than me
But maybe it’s just the way I’m seeing it be discussed as more direct focus on social apps.
Whereas nostr has a bit of an everything app approach (that’s not uh…quite realized and developed yet…if ever 😬)
So for ATP perhaps it’s less technical and more just what builders are focused on? Whereas some in nostr I feel like aggressive want to pursue things other than social apps and talk a big game of nostr in everything…
I think you hit the nail on the head. It’s all talk. Is there a single non-social app for nostr that has more than a few hundred regular users and doesn’t have a clunky UI?
try forking a bluesky client and see if you get any traction
There are multiple successful third party clients that were built on or used the code of the official or other third party clients, but reimagined the UI.
I’m not a programmer, I wouldn’t know how to do it, but the right person/team with a good idea and a slick take on the UI could easily get traction with a new client. Especially this early in the network’s growth.
Bluesky has a huge SWer community whose minds would be blown by zaps if they came to a platform where they already felt comfortable and safe.
How easy is it to integrate Zaps with a federated model? Is the server hosting the zaps now acting as a money transmitter? Do they have an obligation to obey OFAC?
All above my pay grade, but I know there’s no reason the protocol couldn’t support it.
Also, Bluesky’s federation ≠ mastodon’s federation.
Very easy, most already have the rails. It's an Apple policy issue, mainly. X could turn on zaps but instead they limit tips to tipping profiles for policy reasons. Nostr isn't nearly as reliant on Apple.
