Clients don't respect our privilege.

Relay.tools fixes this? (if clients can see the forest for the trees)

Reply to this note

Please Login to reply.

Discussion

We really need clients to embrace relay.tools, not really the other way around, imo.

It's the same problem if they do, but I think it becomes a whole lot more solvable when clients can manage a flexible relay structure that respects their design choices.

Yes, much easier, but relay.tools is also a client and it also doesn't let me see my stuff. Even more rigid than the others.

It's only a client if it's used like one.

Otherwise it's just the scalable backend of a virtual Nostr application.

i hear ya on the tyrrany lol. i thought there would be more flexible clients by now. after i rescue the relays from this mystery client induced high load average and finish relay settings ill do another round of dev on clients, and try to nudge amethyst back on track with global views that broke again.

Ooohh... There's a mystery client in town?

there's a new mystery in town that's for sure.. lol, im trying to track it down, out of curiosity, whatever it is, it causes higher load on the relays.. I can scale up, but I also would like to know why I'm needing to.. it was more suddenly than gradually, so that's why I assume it's a client, or some new scraper, or etc..

What format are the subscription ids in? It might give a clue as to what client for nostr library it is

the sub id is literally just a "2" everytime lol