The roles & identities of the Trust & Safety team on nostr are public. Always have been.

Nothing forbids people from creating Nostr event kinds with code in them. Kind 5392 could be HTML code, 5393 CSS, and 5394 JavaScript. Then a Nostr-native browser can simply render events as if they were files on a regular webpage. The only difference is that now they can be stored in any existing relay.

Do you want to truly decentralize the web? Kill DNS.

Being unaware that anyone can see who you're talking to in nostr DM is very disturbing and extremely dangerous.

The term 'Encrypted DM' is misleading many people.

If your app utilize Nostr DM, it is crucial to display a warning.

You didn't really think about that before saying.

"Innovation" by keeping everything restricted.

The entire point of using a standard is to not have to learn a new set of formats for every new service you're connecting to (e.g. APIs).

That’s because Apple sees zapping as paying for digital content that’s consumed inside the app.

I assure you Apple couldn’t care less about Bitcoin.

In other words Apple doesn’t really care that we’re instructing users on how to evade their 30% commission.

It only cares that when “content” is “purchased” AND “consumed” inside the app, they get 30% of it.

Correct, we have a disclaimer inside our iOS app (so does Netflix) that alert the user they can buy a membership on our website and we never had a problem with Apple.

As long as the "purchase" of the content happens outside of Damus, they will have no problem with it.

What would Steve Jobs think or do?

SimpleX is based around queues. Instead of pushing everything to a relay and have it stay there forever, you push messages into a queue that eventually gets consumed by the person you’re sending the messages to. They exist on the relay temporarily and they are encrypted. Cool part is that there are no long-term “addresses” or “pubkeys” to send the message to, so spam is much harder.

I think nostr could learn a lot from this protocol, I believe we can use something like this to strengthen use cases on the nostr side. I am building a SimpleX rust library to learn the protocol further, and will be looking into how we can leverage it in our apps.

What about the EU banning the walled garden? Forcing Apple to allow side loading ? This should change things

This would imply that displaying note zaps is not allowed, because i have no control over what third party service people use for sending zaps in response to reactions. You do have to go outside of the app to set this up… definitely gray area. Not sure how app reviewers would interpret it.

this. nostr is just bad for private stuff. nostr DMs were a mistake. We can do better and leverage protocols more suited to private comms to protect peoples privacy at a level that would piss off the NSA. nostr:note1mvx4a2g6dw4kanemrech059vu6hx4d3jtghcu746l7934jk9j85skqtmkh

Yeah, I don’t think that this will get you banned. Massive applications in the App Store have work arounds. Spotify won’t even let you sign up through their iOS application. You’d think Apple, as a direct competitor in music streaming, would have thrown the gauntlet down. They didn’t.

I highly doubt they’re going do anything about this. It has nothing to do with your application.

Banned for what