Nostr Web Client

Damus is a native iOS app.

Damus tech stack is nostr + lightning + iOS + other stuff.

If iOS refuses to comply with the lightning + nostr combo, there isnt much you can do, because that part of the Damus tech stack is owned and controlled by Apple Inc.

Are these corporate properties and decentralised protocols compatible? I think it’s hard to bridge.

It’s a major headache for Will, and 14 days isn’t much time to plan a new strategy and get it implemented.

I’m not convinced by Apple’s view about zaps, but trying to define / legally categorise zaps produces a lot of contradictions and 14 days isn’t much time for Will et al. to change Apple’s view whilst also creating a fallback position for the app.

CosmoCrixter 2y ago

I understand your position, but I'd rather use Nostr on Iris in a web browser on iphone (or use Android or desktop) and send zaps that way to enjoy the full functionality of Nostr. It seems like capitulating to me to say "okay, we won't express value on a system that was designed to allow us to express value."

Reply to this note

Please Login to reply.

Discussion

⚡️🌱🌙 2y ago

But Damus isn’t nostr.

Damus is just one nostr app… on iOS.

nostr apps should be available on iOS, there’s a lot of value in that, but they will have to be built on iOS terms and conditions.

Will has to choose his future development strategy between zaps and iOS. But either way he can still have a zap free iOS implementation 15 days from now.

Damus has had a fork imposed on it, it might split and continue both paths.

CosmoCrixter 2y ago

What you are saying makes good sense. I guess a decent intermediary step towards full Nostr functionality on iphone could be the hobbled zapless version. And users can find out that users on other platforms can express value freely and openly, and be sad, and perhaps push apple to change their silly ways.