Back in the early days of twitter clients could say their name in posts. It was a really good way to discover new twitter apps. It was dropped in 2012 as part of twitter abandoning the open app ecosystem.

I’d like to have that feature in Nostr. For example, today I’ve posted from nos.social, damus, coracle, listr, and primal.

To make it short, maybe we don’t do a user-agent like string, but instead add a field or tag to events with the app name. Then apps can store a name to link url depending on how they want to use it and make it visible and clickable or not.

Reply to this note

Please Login to reply.

Discussion

This would help a lot with debugging too.

I miss tweetdeck. This is good information

We’ve had many clients write “client” tag but its usage has been dropping. I agree it would be nice to have more of that.

Just use tags

A year ago a lot of clients included a 'client' tag. Gossip made it optional, default is off for privacy reasons. I have it on so people can contact me about invalid events gossip may create, so as the developer I can get them fixed.

I believe coracle did something like this for a while? nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn ?

I’d actually love a “client” tag like this!

Yeah, I used to do `["client", "coracle"]`. I liked it, I can't remember why I removed it.

Ok, we’ll add it to nos.social, and find a way to display it. Hopefully others do too.

Agree. That would be dope!

nostr:note1ku0sulxaglljtec3mwz9nuwq2gly2lqaw3m84r4ms70m3hd85c7snrt27u

I remember those days... Really fascinating way to discover new apps!

😎

can we make it optional, for privacy

Yes but it should use nip-89 for better app identification and imediate app's review browsing.

It lasted beyond 2012 IF you were using some publishing tools. I think sprout social was one that I could either see what was being used still? It’s hard to remember everything but I know it was 2019 and I was seeing some info somehow.

I was checking out what tools certain accounts were using because it helped me figure out if there was something new I should be checking out (more for marketing than for personal though, I was looking for power tools basically to help me stay on top of event marketing.)

Honestly it might help me here if it were accurate. Or even if someone wanted to pretend to be on something it would bring awareness. 🤷‍♀️

Nice discovery, marketing and acknowledgement tool

Might even help in debugging

nostr:note1ku0sulxaglljtec3mwz9nuwq2gly2lqaw3m84r4ms70m3hd85c7snrt27u

That was fast. Now also for the notes.

note1h508mz0l2k5r0atsvexlsdupa7jmaalfptyy56adjmxa4yu8vrmqptgf0u

That’s a good idea 🤙

your tweet on spring mini for twitter, i see the nos.social link

I really love this idea😻

nostr:note1ku0sulxaglljtec3mwz9nuwq2gly2lqaw3m84r4ms70m3hd85c7snrt27u

[“client”,”Damus”,”http://damus.io”]

whats wrong with a user-agent tag?

+1 for this :)

Do you have articles or books in mind to read about those early days?

I love this idea. Should we include an optional reference to the nip-89 app definition in the 'client' tag?

it should be an OPTIONAL feature only or other devs will invent below

addons.mozilla.org/en-US/firefox/addon/uaswitcher/

Voicing privacy concern: I understand nostr is not necessarily a privacy protocol, but I don't need clients auto injecting more metadata into my events. Must be OPTIONAL. I will 100% be building a feature in NVault to strip client metadata from events before they are signed

I love this idea and I absolutely agree. I remember seeing a client and would always go check it out if I hadn't heard of it before.

NIPs のコミットのキャッチアップ

https://github.com/nostr-protocol/nips/commits/master?since=2023-11-15&until=2023-11-17

* NIP-89: Recommended Application Handlers

* `client` タグが追加された

* すべての NIP

* NIP の著者が削除された

* NIP-51: Lists

* リレーを分類するための `kind: 30002` が追加された

`client` タグについて: nostr:nevent1qqstw8cw0nw50le9uugahpze78q9y0j90swhgan636ac08acmkn6v0gpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqzypmvwx4w8fy378v7a3ruhgt7y2wd5sgn5zamde4wzamdwep798905qcyqqqqqqgfvd9j0

NIP-51 の kind は、全面的に見直されている: https://github.com/nostr-protocol/nips/pull/880

#キャッチアップ #nips

Agree!