It depends on relay response, sometimes relay give a very slow response

Agree, better separate them in different icon/menu

Yes. On client level, like Amethyst, it makes the notes hidden. In relay level, depends on the relay owner, some relay like nostr.mom currently has spam filter and also periodically review spam report to filter and delete the spam content from the relay. Cc #[2]

I have seen similar spam message. They make multiple account with different random number of invoice. A bit hard pattern to detect automatically. The only clue is the account doesn't have profile and follows. Cc #[2]

Thank you, for your relay implementation sir 🙂

Successfully, running nostr-rs-relay (by #[0]) locally on my phone using Termux.

Installation in Termux:

# pkg install rust protobuf

# git clone https://github.com/scsibug/nostr-rs-relay

# cd nostr-rs-relay

# cargo build -r

We can also easily backup and broadcast nostr event using https://nostr-broadcast.pages.dev/ (by #[1])

It depends on nostr client, how they fetch their data. In Amethyst, i think it fetch data simultanously from relays who have "read data" setting.

Yup, you've got the good relay. You can add most paid relay even if you don't pay them to read data but cannot post on them.

Better to have several (3-4 maybe) paid relay. If i have to choose one then nostr.wine imho. They have filter.nostr.wine while other paid relay didn't have yet. You can check their docs:

https://nostr-wine.github.io/filter-relay/

The latest one is quite good, especially CDN image caching. Vitor set up his own server to resize and cache profile picture

Yes, maybe they need to polish and handle many other things.

Also, imho, probably due to issue of guarantee of event deletion itself. Some relay maybe can ignore the request of event deletion (pretending that event was deleted but only mark it as 'deleted' in database). 😅

More efficient data fetching will be implemented in many nostr client. Currently, Gossip nostr client (by #[2]) seems more efficient.

stacker.news or vida.page also fully support zap (NIP-57) implementation. I have tried both of them.

You can still get zap or tip. The difference is only on public zap notification on notes. Not a problem even if WOS doesn't implement it.

Don't, this is trap 😆

12 relay.

Global read from:

- paid relay

- nostr.mom (have spam filter, lesser spam now according to owner #[2] )

- filter.nostr.wine (include friends of friends feed, expand global with web of trust, by #[3] )

Special Relay:

- nproxy.zerologin.co (proxy relay to connect many relay in single websocket connection, can be used as broadcast relay)

Lol, i'll do my best 😅

Yes, i have seen this on nostr.mom . I am using amethyst to send the report. Its ok, but you need some follow-up manually to make sure i don't make wrong report 😅

Yeah, I think so, only based on tagged relay and only works for tagged public relay. Devs need some workaround to add "popular public relay" probably such that zap response can be more visible 😅

Seems the solution, #[7] also implement it like that based on https://github.com/jb55/cln-nostr-zapper/blob/master/index.js