@jb55 question about noteguard: I have strfry behind a reverse proxy and every IP seems to show up as localhost which means IP-based rate-limiting doesn't work. Is there some way to use the X-Forwarded-For for rate-limiting?
nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3qamnwvaz7tmwdaehgu3wwa5kuegpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43q3ttcfs how has Damus relay eliminated reply guy? Just IP based rate limiting?
Anybody have any nice code snippets for strfry policy plugins? Prefer code that can be statically compiled with no dependencies.
#asknostr #opensource #strfry #relays
nostr:nprofile1qqsrmpp2lmx4u2fl9zmxy7fnwp9rlwxwz5a2j8tep2c376n494z2gtgpzamhxue69uhkxun9v968ytnwdaehgu3wwa5kuegprpmhxue69uhhwetvvdhk6efwdehhxarj9emkjmn9qyt8wumn8ghj76twvfhhstnwdaehgu3wwa5kueg6jsgtg how come nostr.wine is so expensive? It's a cool service but hard to justify ~$10 / month when most relays are already free.
Totally forgot about these guys. One of the most creative bands from back in the day. "Banshee Beat," "Fireworks," and "For Reverend Green" were also really good.
Is there a way for a pubkey to be "trusted" under a web of trust framework with few or no followers? If not this seems to risk an effective shadow ban on huge numbers of people. #asknostr
Not sure but why are you using cron inside a container? Usually the job orchestration happens outside of the that (could even just have regular OS cron run the container)
Thought: web of trust heuristics are the only reliable way for nostr to combat spam, and so the network will gravitate towards a collection of isolated cliques. How is this wrong? #asknostr #spam
nostr:nprofile1qqsqgc0uhmxycvm5gwvn944c7yfxnnxm0nyh8tt62zhrvtd3xkj8fhgprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqgcwaehxw309ahx7umywf5hvefwv9c8qtmjv4kxz7gpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7s3al0v nostr:nprofile1qqs8sxs4yuz47axp7uprpugrs3sfkdz5379tdg9xe2n5qfvz070a4egprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqg4waehxw309aex2mrp0yhx6mmnw3ezuur4vgzaq60d do you all have any tips for improving initial feed load time in Ditto? I noticed it's slowed down for me a bit on my server and am wondering if it's DB related (or possibly has to do with two firehoses that are always syncing in the background)?
It'd be a long shot, but curious if the operator of the reply guys made any opsec fails that might make them identifiable #spam #osint #opsec #asknostr
nostr:nprofile1qqsqgc0uhmxycvm5gwvn944c7yfxnnxm0nyh8tt62zhrvtd3xkj8fhgprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqgcwaehxw309ahx7umywf5hvefwv9c8qtmjv4kxz7gpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7s3al0v you ever had issues with Prometheus just stopping scraping Ditto metrics? I stopped Ditto, updated to recommended deno and latest Ditto, restarted Ditto and all metrics stopped (was working fine before).
I'm not sure a mechanism that relies on making BTC transactions is great because the UX would be very bad (and near unusable for normies).
I feel like there are probably some other heuristics you could apply to npubs (looking at follows is just one) to determine their credibility without requiring any user action. Stuff like "age of oldest event" or "count of times blocked by credible npubs" could do a lot.
Notes by stove5 | export