mleku on Nostr: i went to a lot of extra steps of work to build an objectively faster library ...
i went to a lot of extra steps of work to build an objectively faster library implementation than what he used and i was in the process of building a simple 2 level WoT whitelist for nip-42 based auth access control
what was different that UTXO did was he just made it work without auth
the clients are all very inconsistent in their parsing of the text of the NIP-42 spec and even just three days ago nostrudel broke the auth flow that was previously working with #realy
so, yeah
not allowing people to post who aren't in some distance of the social graph from designated lists of npubs is really simple
making it work with clients, with auth, and making it with an efficient json codec
i did a lot of work to make all that happen
but it helped him at that time during the replyguy fiasco
i literally don't get spam on my wss://mleku.realy.lol because it only listens to my follows and follows of my follows and whoever i mute is blacklisted from publishing events... as clients have finally got a bit more sophisticated, i can see these other shits that are publishing (and some do, some don't) with their bot spam "news" and other nonsense
my solution works better, but i've had no augmentation to my funding so i can defer my fiat mining work to do it better, but my work is better
anyway, you will all see, because what i'm building is for serious business, not just addressing a hot topic at a brief period of crisis due to a dumbass, predictable failure of the design of a dumbass protocol and the use of shitty, hardly ever updating, dumb relays
what was different that UTXO did was he just made it work without auth
the clients are all very inconsistent in their parsing of the text of the NIP-42 spec and even just three days ago nostrudel broke the auth flow that was previously working with #realy
so, yeah
not allowing people to post who aren't in some distance of the social graph from designated lists of npubs is really simple
making it work with clients, with auth, and making it with an efficient json codec
i did a lot of work to make all that happen
but it helped him at that time during the replyguy fiasco
i literally don't get spam on my wss://mleku.realy.lol because it only listens to my follows and follows of my follows and whoever i mute is blacklisted from publishing events... as clients have finally got a bit more sophisticated, i can see these other shits that are publishing (and some do, some don't) with their bot spam "news" and other nonsense
my solution works better, but i've had no augmentation to my funding so i can defer my fiat mining work to do it better, but my work is better
anyway, you will all see, because what i'm building is for serious business, not just addressing a hot topic at a brief period of crisis due to a dumbass, predictable failure of the design of a dumbass protocol and the use of shitty, hardly ever updating, dumb relays