I need to be this birb
Luxas
_@end.the.fed.wtf
npub16jdf...33sv
Developer behind Nymchat.app, Nosflare.com, NostrMedia.com, NostrAddress.com and βΏitcoin node runner and miner since 894996
π


This #nostr relay project from a few months ago has gone with little notice, but I think it's still a dope relay implementation. It's the reverse version of Blastr. You can't publish notes to it. But it REQs from as many listed online relays as possible using the nostr.watch API.
You can use it with wss://unostr.site
Or build your own using a Cloudflare worker:

GitHub
GitHub - Spl0itable/unostr: A reverse Nostr relay that ONLY requests events from all online relays
A reverse Nostr relay that ONLY requests events from all online relays - Spl0itable/unostr
Nostr is dope.
View quoted note β
#Nostr I think I'll be tinkering around with some more strict rate limiting measures in #Nosflare relay that stores the hash of the content of each note's json. In a similar way I have it check for duplicates already on #Anonostr but this would apply relay wide.
This way bursts of spam notes that repeat the same thing, regardless if disposable npubs are used, can be stopped quickly at the relay level. And it would be quick to adapt if the spammer adapts. Of course, will have a filtering logic available for any single word or phrases you'd want still allowed. But might be useful to block X thing once repeated Y times within a given time frame.
I'm fully aware that a spammer could iterate through each note with completely unique content to bypass. And that's why I'm thinking the next best feature might be to have a minimum created_at requirement to publish to the relay. When an EVENT message is received it goes into a queue and the author's pubkey is checked against another relay for its oldest created_at event. If it is less than X time old, it gets dropped.
Could be something relay implementations collab on to help the community. Some standard that let's relays share this data and make it easily REQable. Thoughts? #AskNostr
No longer a GM. They've switched up their tactic and are now parroting what you've posted as either the URL or hashtag. I think they're following me too, as my notes have been directly targeted. Good thing WoT hides these for me.


#Linux


People like to bag on "verified" #nostr addresses (nip-05) as being dumb. And there might be a valid argument for individuals. But I like that I can know @Proton Wallet is legit simply because they've verified an official domain.
Can't wait!

π³


Fortunately, for anyone running #Nosflare they can easily block the ReplyGuy message π

GitHub
GitHub - Spl0itable/nosflare: A serverless Nostr relay through Cloudflare Workers and Durable Objects
A serverless Nostr relay through Cloudflare Workers and Durable Objects - Spl0itable/nosflare
New #nostr relay idea... when spam is detected, it takes the EVENT message and redirects it back to the author.
People keep mentioning the #Nostr elite. I'm convinced some of the #Nostriarchy are Feds anyways. Probably good to distance.
Feels π


π³... π
View quoted note β
