I wasn’t certain they are bots. Semi-felt like it was a Nostr bridge publishing bot/service someone is playing with.
I welcomed a few anyway 😂
Depends on your app. Most apps have a default zap amount set in the settings options. If you long or double tab zap, it often gives you the customise pop up. Depends again on the app.
Well it’s a delete request. You can’t delete off mobile phones or browsers that have it stored locally. Most likely archival services will hold some reference long time anyway.
There are replaceable events too.. so some event history could be lost if not stored somewhere.
Yep. Some apps have autocomplete for the username of people you follow too.
Depends on context a lot. Sometimes you want to navigate lots of replies. Other times just a few DAGs that interest you. I prefer Reddit style for computer screens.
Hey, GoWildish is a nice name :)
I prefer to get stuck hiking mountains, while wincing as I eat freeze dried meals, and complain about all the wet firewood. I’m told it’s character building 😄
You can only request to delete your own events from relays. It’s effectively a “stop including in future event queries” request.
And it’s been part of the protocol a long time.
What if governments existed to make their people “safer from governments” - which literally should be their sole justification for continuing existence.
#[0] opening this separately from the other discussion as this is quite unrelated, but would be a cool idea and I’m kinda doing something like this already but not as cool:
A cooler but way more out-there idea, if nostr could act like a DNS SRV-type record for service-handler discoverability, nostr clients could query my follow list for a recommended list of services that are compatible with a certain kind
1111 = made-up “kind-handler” kind
"kind": 1111,
"content": "zapstr music player",
"tags": [
[ "k": 31337 ],
[ "url": "https://zapstr.com/a/
]
{"kinds": [1111], "authors": [
Yep. Cool idea 😎
I forgot about DoH existing 🙃
By all means write up a NIP and see how far it’s possible to get. Key signing is likely the next major issue. A less stateful lookup approach would be interesting.
I’m already wondering if NIP-05 is the best approach for people long term. Likely not. Businesses maybe. I think something else can replace it in future.
Web clients. You’ll notice that this has near zero browser compatibility. And I don’t think it can even do DNSSEC.
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/dns/resolve
Web browsers are still heavily sandboxed today.
I think it’s fair to give JB a lot of credit for his efforts and listening to feedback. Be mindful it’s all experimentation, and sometimes burning bridges is the only way to encourage change.. some people still use fax machines… why..
I think of a lot of Nostr devs may be a little raw in their responses because things are moving fast, dev time limited, and in reality, we’re slowly working towards a burnt-out like state. I’d try not to take it personally.. it’s a side effect of a new crazy little chaotic thing called Nostr.
Maybe there are two parts. Previously I suggested another approach too - see below.
1. We should be able to reasonably have a kind to kind label mapping that can be used to at least give context in apps. That’s a step forward.
2. If that kind can somehow give a fallback content or similar, great. Maybe the equivalent to the noscript HTML tag or img alt attribute. Dupe data, but that’s life. A tag is better suited long term than the content.
Additionally, we could somehow have registrable Nostr event kind url handlers - so you can tap the placeholder to load it in a different application. I don’t know how this scales perfectly, as url handlers may not allow kind ranges.. but worth experimenting. Apps are likely linked to target kinds over ranges anyway.
POW has a fair chunk of pushback - however it does offer unique properties. The general preferred approach is pay-to-relay.
It’s a good point that perhaps generic messages shouldn’t be posted to dedicated public human consumption relays to begin with - but again, you can’t really control this. However, pay-to-relay could assist - but people will just pay for their bot pubkeys to relay, as it’s cheap per event in general.
A counter point is, just like advertising and tagging, as soon as it’s used for discovery, people will do whatever they get to boost/maximise their discovery for the lowest cost. Bot dedicated relays for example likely wouldn’t get as much attention or engagement.
I see kind 1 as a forever dumping ground of random events, as it will be the most supported kind by apps and get the most eyes. Our engineering challenge is to best manage that.