If you own a lot of domains and want to cut the costā¦
- Become a āresellerā to get lowest prices - even if you donāt actually resell. I use ResellerClub.com
- Donāt pay for private registration. Instead put in āwebmasterā for your name and then use a PO Box or some other legit address to avoid doxing yourself.
Are there benchmarks for the time it takes to do PoW?
I ask because it sounds like youāre saying that the same level of difficulty would be a negligible delay for a bot on a fast server, but take an unacceptably long time for a human using a web browser.
In that case bots will have an advantage over many real users.
Generally agree, definitely like the way youāre thinking. Two thoughts thoughā¦
Having an LN paywall on the relay recreates the problem I was trying to avoidā¦ Iām not sure itās legal to require payment to report content problems. e.g. a copyright holder shouldnāt have to pay someone whoās violating their copyright. But PoW isnāt payment, which is why that might work.
But then there the problem that PoW is really slow in browsers (see screenshot below). It canāt take a full minute for browser-based users but be instantaneous for bots on servers. That makes no sense. 
How do you do rebills with Lightning? Itās a critical question for more than relays.
When I brought up the topic of Lightning for porn sites the site ownersā response was ābut weād lose rebills and rebills are the bulk of our incomeāā¦
Potentially dumb questionā¦ Is the Lightning network basically proof-of-stake?
Hereās more on Nostr Kidsā¦
https://www.boppow.com/coming-soon-01-2
But #[4]ā & I are working on content moderation that, in the long run should make things a lot safer for kids.
A better comparison is the key to your house. Passwords typically need a username as well. Keys donāt. āPrivate keyā isnāt very sexy. But every nsec starts with nsec, so not too hard to remember.
Thereās actually a Nostr Kids initiative.
But yeah, š for #nsfw!
"May the 4th be with you"ā¦
Episcopalian response: "And also with youā¦"
I looked at spam.nostr.bandā¦ I see existing strategies (e.g. "follower networks") plus NIP-69 (user-specified moderators ā feed filtering) as solving the spam issue for users - except perhaps in their "global feed".
Public relays have a big spam problem. You've devised some strategies for that, I'm sure others have as well - but that's beyond my personal area of interest or expertise. (Though I am curious to hear what works.)
Paid relays will have a problem with moderation report spam since it's a catch 22ā¦ If they make it so only paid members can file moderation reports, then they have a legal problem. If they make it so anyone can file a moderation report then they have a potential spam problem. They can start by ignoring reports about content that's not on their relay. But they can still be spammed. Which is why I'm so glad nostr:npub1ktw5qzt7f5ztrft0kwm9lsw34tef9xknplvy936ddzuepp6yf9dsjrmrvj mentioned PoW as a possible solution and want to understand that better.
Beyond that - I would look for unusual patterns of reports. First, take out the reports from people (and bots) you trust to one degree or another, thenā¦
- Are there a high number of reports about the same piece of content?
- Are there a high number of reports from the same IP? (use /64 for IPv6)
- Are there a high number of reports from the same pubkey?
- Is the report from a new pubkey?
I monitor for (non-Nostr-related) attacks on my server now. Everything from SQL injection to blog comment spam. It's all IP-based. I look for "bad neighborhoods", so if there are too many IPs with infractions in the same subnet, I block the entire subnet. (More easily done with IPv4 than v6.)
I think pubkey age is a great metric. I see Primal has that data. You probably do as well. That's valuable data! I'd love an API that could be hit to query on the age of suspicious pubkeys. In exchange relay owners could probably give you hashes of IP addresses without compromising privacy laws - so you could answer the question of whether pubkeys are coming from the same IP (without knowing the IP).
nostr:npub1pu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqswtfch didn't handle either case well, but it's at an earlier stage of development - so that's somewhat expected.
nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg did the search properly, but I couldn't test how it looks in the feed since I can't figure out how to login (I seem to be locked into a read-only demo mode or something)ā¦
#[5]ā Nostur had the same results as Damusā¦ Displayed `nevent` properly on the feed, but failed on searchā¦ 
#[4]ā Damus is half thereā¦
`nevent` is displayed properly in the feedā¦ but you canāt search on `nevent`ā¦ 
nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 Snort seems to fully support `nevent`ā¦
The `nevent` is rendered properly in the feedā¦
And it works great in search as wellā¦
Supporting `nevent` seems to be a work in progress with nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk nostr:npub1wnwwcv0a8wx0m9stck34ajlwhzuua68ts8mw3kjvspn42dcfyjxs4n95l8 ā¦
Searches work greatā¦
And when I went to reply, it worked greatā¦
But in the normal timeline it still just shows the `nevent` value - it doesn't render like it shouldā¦
Doing a test to see how different clients handle `nevent` (spec'd in NIP-19)ā¦ Both how they render it in kind 1 events and whether they handle it properly when you put it in as a search. Here's the nevent for the note this note is in reply to. It contains a relay hint of wss://relay.s3x.social - which should be all the clients need to find the note and display it. Let's see which clients handle it correctlyā¦
Interestingā¦ Sounds like a solution that would help relay owners deal with floods of bad reports.
Iām not a crypto guy and donāt really understand how the PoW part of Nostr (NIP-13) works. Can a relay owner turn that on for just moderation reports? The idea is it slows down the reporting, right? Is POW done for every relay they send to? What happens if they use a blaster relay? How does the relay tell the user PoW is required and what level of difficulty?
Iād be happy to add that to NIP-69 if I can get my head around how it works.
Again - weāre more on the same page than you might think.
Please read the latest commit to the PR. Weāre on the same page. Nothing is centralized.
https://github.com/nostr-protocol/nips/pull/457/commits/724e05e762a634e501bdcf6cbefaa91f99b1903b
In fact Rabble had me look over Blueskyās content moderation model and my comment was that it sucks because it assumes a central moderation team that āresolvesā reports. (No one can definitively resolve anything in a decentralized environment.)
Regarding spam. Iām expecting DDOS style attacks by haters who want to silence people. (Iāve already had death threats on Nostr. This is personal for me.) Those DDOS attacks are possible now (especially for getting someone muted on Amethyst). Itās one reason why Iām pushing for a complete reboot of the content moderation tools.
NIP-69 now clearly states that clients should only act on reports by āpeopleā designated as moderators by the user. What that means is DDOS attacks are of little value. Theyāre like shouting into a void - no oneās listening. Theyāre only really a problem for relays, not end users.
Nostr clients need more support for `a` tags & `naddr` / `nevent` / `nprofile` IDs with embedded relay info. Theyāre incredibly powerful. Situations like in the pic shouldnāt happen. 
Thanks for your answer. Among other things it seems to explain bitcoinersā seemingly strange (to me) obsession with inflation. Your competitor is run by a system where there is reward for inflation, so itās something you folks are acutely aware of).
It also gives me insight into why you guys think seem to think fiat is a Ponzi scheme, when Iāve always felt people pushing crypto as an investment had an Ponzi-like aspect to their argument. (Iām 110% in on crypto for commerce- itās the investment angle Iām seriously skeptical of). That gives me additional points to think aboutā¦