Should clients add client name + version to events signed by them? I could make debugging and error identification easier.
Maybe an ['agent', name, version] tag?
#[0], #[1], #[2], #[3]?
Discussion
#[5] For a future upgrade, can we get a feature that allows us to save a list of names we want to see in our home feed? This wouldn't be permanent. Just a narrowed list from our Follows.
You can do that on highlighter.com/dashboard/bookmarks
I hacked it together in half an hour this morning so it’s barely functional but it’ll be better later tonight
Yeah, I’ve been debating whether this is desirable of unnecessary bloat
I think at this moment it can be useful; the new client I’m working on at highlighter.com/dashboard/highlights is using “atlas” as client name
Does that reduce privacy?
Slightly to no; you can fingerprint events based on how they’re formed and kinda get the same info with a lot less certainty.
Definitely should be an option
A cool feature would be the ability for me to see who zapped my note and for how much. This would be great for auctions. In my case, I am an artist auctioning off my paintings (see my prior note as an example). Only the person who posted the note should be able to see this in order to preserve the privacy of the zapper
#[7] and I tried to create zapauction.com during nostrica but failed miserably; we got about 2 net hours of work done during the entire time in uvita 😅
But we got REALLY close; we could easily release it if there’s demand for something like this
Snort breaks down reactions
Great is better for Artist
No. Need to avoid bloating the protocol if Nostr is to scale
Is not part of the protocol
Gossip has an option for this. Should match it's format
It’s bloat. You don’t need a client to create events and can imitate a client anyway. You know the poster pubkey, time of creation - what more do you need to follow up if critical?
Plus adding it means lazier coding as expecting a client (which will happen), means less exception or validation handling - and less robust implementations. Expect anything, never trust user input, validate everything.
Browser user agents are completely bull crap today - Apple iOS messages pretends it’s Facebook for previews, everything has WebKit/gecko, it’s just all incorrect bloat from a legacy time.
Optionally while testing is different and no real problem.
I'd say no just to preserve as much privacy as possible for anonymous users.
This is why damus will never add it, even though damus is not the most private, but I want it to be moreso down the line. Seems like it needlessly reduces the anonymity set.
damus has enough users that we can assume that no client tag means damus 😂
Or the 🤙 being used. Or their first follow was Damus. Or they still are following Damus. Other quirks in contact handling or even creation.
I really hope we can combat fingerprinting better in Nostr than Web browsers do. If browsers never added so many fingerprinting privacy holes, perhaps ads never would have felt like your microphone is always on.
would wish for more transparency on the relay end. I fear that in the future the data will be used for marketing and other analytics. Does the relay share with other relays, important info to know. Couple of icons would help:
1. data kept with person xyz
2. shared with other relays or not
3. commercial use of data yes / no
4. possibility to delete data yes / no
All data is public
But it’s not public property, is it?
It’s information. Anyone can access and repeatedly copy it. The wonderful part about Nostr is that you can always prove cryptographically who sent the message.
Mr Edwards. How is sister Johanna? Well I hope.
So is music, but that doesn’t make the thieving right, does it?
But destructing there is no excuse for.
Pay.
And destruction due to envy at that.
Pay for it in blood. 
There is no way to stop the information from being spread to anyone or archived for any amount of time. Changing the information or the author becomes impossible though.
Its not about being impossible. Its about preventing organized abuse by advertisement. Of course you see my post and I see yours, but I should be able to pick what the relay is going to do with it.
Heck, if going for the con, why not just make believe like the artificial sweetener spankers?!
Would be less harmful than needing to target innocent civilians to justify the tie.
https://www.youtube.com/watch?v=3L4YrGaR8E4
Don’t do exploding me blowing up in public to impress me now.
Just some string in some cloud right?
Why bother with the harm if spanking and going for the con?
If you don’t own the relay, there is no force, only suggestion. It’s someone else’s property so you can ask them, but not force them, to do something with it.
In theory, it’s not the relay owners data neither, but the account holder, and there is no two ways around it, and getting cure doesn’t make the relay owners data.
Please understand.
It’s quite remarkable to see how american hypocrisy manifests.
Going to war over democracy, only to act the bullies and then ignoring their own peoples rights.
Now I’m not an American to be offended, but it’s still noteworthy.
Thats just one aspect, which is great. But why to undermine the privacy aspect
Privacy doesn’t imply intentional causing harm like crashing birthday parties in Alabama being reckless.
And mind you, as a spectator to the farce, where innocent American lives are being spilled due to American stupidity to serve sin, what can you do?
You can fool some people sometime, but you can’t fool all the people all the time, and when that happens, shit out of luck.
Massacres.
Does not matter in my op. The data on instagram is public as well, me waking the street is public as well.
In gossip it is configurable and off by default. It makes sense if you are helping developing clients.
no
Probably not by default.
Yes, coracle does [client, coracle]
