We only publish the nostr:npub14h23jzlyvumks4rvrz6ktk36dxfyru8qdf679k7q8uvxv0gm0vnsyqe2sh events to one relay. If you don't like it, don't connect to the relay and mute the account. These reports aren't being spammed, you're client is seeking them out. We do not publish these to anybody else's relays.
A major problem is Amethyst is not using the Web Of Trust model instead is searching for anybody regardless of your connection to them and highlighting the labels both as replies and new posts. These are type 1984 events, they're labels not replies.
The misconstrued anger towards you is unfortunate. I get that its seen as spam because that event is rendered even though thats not what you intended.
Energy better spent towards the llm reply bots without known creators. Solve that problem and we solve the "reportinator problem"
Its okay if others don't understand and get offended at "replies" from a reporting bot. Only a matter of time until someone releases some sort of reportinator army akin to the happy new years reply army with "the" as its list of flagged words.
Automated reporting will happen one way or another. Report classification need only to make sense to the builder of the bot.
Beyond rate exclusive relays, rate limiting and IP blocking, theres nothing anyone can do to stop comments on your posts.
Guess its just difficult to anticipate the consequences of system built with censorship resistance as its foremost principle.
CREATE NOTES, STACK SATS & #BLOOM
Been thinking about how to navigate stuff like that structure for nips on github is to rigid to navigate and gives off a vibe that you need understand a majority of the content before you can get started on your own project.
(1) should probably move to a knowledge base format (wiki-like, wikifreedia) with (2) modular articles: being able to compose a new article from other article fragments/section. my spec for that is a blend of the long form content and lists
hyperlinked, composable, remixable.
- Describe your client by composing fragments of implemented nips, pointing to the original content.
- Apply a transformation to the nip44 definition - you don't need/care to write the original definiton, but you want your readers to read it alongside the implementations in different clients.
If a fragment comes from an existing article, you can navigate to the source within the KB
Over β
These are the rules. We didn't make them.
I like segment, section, component. Maybe partial, partition.
Then for [0,1] you prepend "normalized"
More #tunestr π€
Wow! now thats a steal if i've ever seen one π
LESSGOOO
Statuses in Amethyst make me feel like I'm being subliminally signaled π»
small text, dark font. A thought comes to mind and i ask where did it come from? Look at the screen i see the text.
Looking at you nostr:npub1m64hnkh6rs47fd9x6wk2zdtmdj4qkazt734d22d94ery9zzhne5qw9uaks ππΆβπ«οΈ
Thank you for your insight Mr. Rogers
"who's feet could disembowl you in a single hop"
You've been so kind and patient reading our notes with your phone upside down! We should be more considerate to you π€£
Whoops nostrudel and coracle π€£
snort and coracle, edited cropped and edited for clarity π
