I do think pain can help. It's a chicken and egg problem.

It would have to be a server run by a client with cryptographic keys for sending notifications to the app. For implementation, see

https://github.com/coracle-social/nps
https://github.com/coracle-social/npb

Epistemology is the other big one, and it's the road to the others

So who reported this and how reliable is it? Man I wish this would go somewhere but it seems so bogged down at this point

But I don't want the callback server to see the events!

Sure, it's a chicken/egg thing, I have not problem with us getting hammered with traffic. We're probably just going to fail a few more times before everything is up to snuff

I'll RFC this too. The original version is here:

https://github.com/nostr-protocol/nips/pull/2194

The main difference between the two versions is mine uses encryption to keep content hidden from the callback server and any other intermediaries until it reaches the user.

I honestly like the simplicity of Vitor's version better, but I think it could be a liability for push servers to be handling potentially access-controlled events in cleartext.

Plus, this architecture really only makes sense for getting events out of relays that implement access control, since for normal ones you can just use REQ or negentropy.

Thoughts?

@nevent1qvz...

Yes, also very true

Nostr isn't ready for an influx like this first of all. Relays would fall down, and how would clients handle posts with 30k likes? We need to figure out caching and aggregation strategies that are better than just checking all relays. And unfortunately this is hard to do without centralization. There are lots of unsolved problems, decentralization is hard.

😂

Shop class as slopcraft

Slop class as soulcraft