New Portuguese word for you nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku

Reply to this note

Please Login to reply.

Discussion

i'm debugging a http SSE subscription mechanism at the moment. almost got it working. events are now being delivered and all, just not sure about whether it's properly removing listeners

so i've been posting events to wss://test.mleku.dev to trigger subscription deliveries. i had to add a new "whitelist" feature to the relay because omg the amount of clients sending events and then not responding to auth, it was a constant stream of bullshit i couldn't see any of the messages i was sending to it.

I opened a issue there about a blacklist feature without using the owner mute list

I don’t know if make sense, but when I think about a public relay this feature came in my mind

yeah, because it's a public list. same with follow lists. i'm not gonna bother myself with that at this point, if a relay is public readable a lot of social graph can be inferred in analysis. concealing this would require a specification for privileged forms of these lists that can only be read by the authors and the relay

also, muted npubs of malicious persons don't even care about it, except in as far as they have been designated malicious by someone.