nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s Have you had a chance to look into some of the materials that I’ve shared? I don’t expect that these alone will convince you that #UFO are real but I’m curious if you still strongly believe that they are BS or if you think that there could be more than meets the eye?
evidence is always poor, including the link you sent me. I will believe it once I see evidence that isn't blurry blobs. we also need radar data to do proper analysis. that is almost never provided.
will fix!
Just renewed nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 purple with nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm GO and it was seamless.
awesome :D
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s does Damus support NIP-17 ? nostr:note14sl7ju2vtfvu3s0pdcpfg52vv6mvqfkqz90luy8np3v3zecm7mtsvwz2yh
not yet
It hasn’t worked for me in over a month. Back to nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955
it has never worked for me :( notifications never load
There was no data in this link
That stupid reply-guy is starting to seriously bother me. I don't read replays anymore. That's a thread for onboarding. We must act nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqpr9mhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmnt9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7eyerqr nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3qamnwvaz7tmwdaehgu3wwa5kuegpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43q3ttcfs - can't we blacklist an IP range?
You have too many relays
can’t help with that
nyc is an experience
he was at one point
Do you have this dot? Post for science nostr:note12rsmty590zpprh5652e2ap32qv3ukhlp4fy2e77sadqe8twnzc6smf7vpr
nostrdb will work on android if amethyst integrates it 😇 i should put together kotlin bindings…
someone is spamming my p-tag, so I have to turn on my WoT filter which I don't like doing
I wonder if clients could automatically calculate a spam score for relays and share this score with the network. Maybe if a user marks a note as spam it could implicitly add this to the relays spam score for the user.
once we have spam scoring algos in clients, we could derive a score for the relay automatically. This would give more insight for users, and for clients to recommend relays in manual mode. Autopilot mode (outbox) could use these scores for choosing which relays to pull from.
This is all annoying stuff i would rather not have to deal with, but it’s clear we will have to deal with it sooner than later.
The saddest part is that the bar for creating a usable nostr client is rising. I’m hoping to add as much of this logic into nostrdb as possible so native client devs don’t have to deal with all of this stuff in the future.
I don’t want to have to set two different settings everytime i switch friend filter on/off
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s I think push notifications are being sent for things that we have muted
We check mute lists, but they get cached for 5 mins i think
I got to the last boss in hades and died :( furthest I got. super fun game.
You would first need to define what would actually be shared. Not sure I would trust anything from a dht, some random person could just say “block these ip ranges”. That would not be useful.
Some run instances to spam tons of relays at once. You are likely getting write blocked by using it
we fixed space tagging in the next version! (out this week)
haven’t seen him on damus in a while and did nothing- curious how nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s and the lads did it
ip rate limiting kills most of this spam, if you pick a few high quality relays that does bostr filtering and rate limiting you won’t see much of it.
I built a site for a client using Haskell and Elm where the entire website api, frontend types and backend types were derived automagically from the database. Any change to the data model propagated all the way to the frontend. It was amazing.
You are right, it is weird. Just checked the last event was 7 hours ago 😅
nak req -l 1 relay.damus.io
Only got this one
{"kind":31234,"id":"19ed50446830fefa0757b43eb43ca46839e9e4cea0707f8324216d7f405eeee7","pubkey":"6c0e9016b9c1efe7edef87e505e2a1e03db1fbbcfdc3ed6b4f8aaa4b540ad98f","created_at":1726275953, ... }
/cc nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s
fixed, thanks
They even built their own version control so that any change to the code is automatically tracked so that the timetravelling debugger knows what version of the source code the frame was on. WHAT THE FUCK.
Our local search is on the main timeline when you pull down. We are moving this over to the profile/hashtag search box soon 
This would just be filesharing, which is a whole can of worms
yeah it's bizarre. it's already good for hearing protection, I think they realized they just need to market the features it already has?