Prosecution is selective. That’s how the system began to break into todays shit show - globally.

Early legal days, less people and less opportunity to be selective. Now, the too-busy excuse is used to bias targeting for self gain - not for the people’s/societies benefit.

These days only what those in power want prosecuted, or some official wanting to make a name for themselves from a polarising case, gets progression.

When laws are entirely subjectively applied, there are no laws. Only pretend.

Can confirm. Damus doesn’t like. Maybe because it’s .mov?

https://github.com/OpenBazaar/openbazaar3-rust

This could be of interest. https://github.com/blakejakopovic/nostr-spam-detection

Worth noting that spam or flood attacks don’t just come in the form of kind 1/42. You need protection against other non-content focused kinds too.

Good question..

It’s almost always CORs. You basically need to add “Access-Control-Allow-Origin: *” to the headers.

https://github.com/nostr-protocol/nips/blob/master/05.md#allowing-access-from-javascript-apps

Draft, but check out. https://github.com/nostr-protocol/nips/pull/158

Here is the source code. The version #[1]​ linked is the standalone html with a couple less features. Works fine, but less assistance to load your relays from your browser extension or kind 10002 events.

#[2]

You can add them to the bootstrap list and you’re good to go.

With the mutiny broadcast relay and your relays, it should have pretty solid coverage - nothing will be perfect.

May not matter now, but as we scale, apps should only need to query your relays for your content. If it’s marked as deleted on them, then you’ve covered the largest base.

Side note is I’m having a hard time finding even 150 reliable relays that are online and stable. Broadcasting to 1,750+ (which I’ve seen) and having 80% fail isn’t much of an improvement.

The Nostr Event Deletion tool I posted a week ago now supports loading relays from your browser extension and kind 10002 events. The only catch is now you need to run it locally - as ported it to svelte, and I don’t know how to compile a single html file.

Full source code available for both versions. https://github.com/blakejakopovic/nostr_delete

Also, if you were concerned about your notes, you can download an archive from what my relay has seen here. https://nostrgraph.net/archive

One day out of the blue (no-pun) you may be blocked. Best to share valuable content redundantly.

I haven’t found that to be the case.

Most of the well known or major relays have 12GB+, which is pretty much most events since maybe December.

It could be client app UI limiting perhaps.

Some smaller relays and even some larger have gone offline since, or are not functioning as well anymore. If you broadcast to a bunch, there shouldn’t be any issues.

It’s definitely been talked about. It’s just not easy to implement in SwiftUI. That’s my preference too.

This Nostr debug tool is really neat. Wouldn’t enter my private key into the hosted demo - but it’s open source. Has a nice query UI too.

https://nostrdebug.com/query

Awesome 😎

Agreed. One of the first ways creators build their communities are a discord or telegram channel.

As they grow they promote (often unpaid) moderators to help prevent unwanted content and manage bad actors.

I’m not sure we have the protocol level support for moderations needed yet. I know private groups has mod events defined - however unsure it’s enough.

And likely these communities will centralise around a relay or even purpose build micro relay - and I think it can then filter and manage content better too.

I’d be interested in seeing how you approached the crawler code too. I’m prototyping something similar to take in a relay list and a query and process results. Effectively like a crawler - but conscious about causing excess reload load, reusing relay connections, throttling requests, etc.

I haven’t seen any specific crawlers that exist yet - but I’ve heard of a couple being worked on.