2d
Sam
2d0fc896761fd8822cf1af95cdb12c298bbb55bb0777691a9df26a76e21e82bf
I make stuff that connects to the internet. Sometimes I even get paid for it.

This is actually already a NIP, so in theory, some clients should support it. So far I've checked Damus, snort, and iris... None of them seem to support sending a šŸ‘Ž, but at least one recognizes it.

Check out mostr.pub they've set up a bridge between nostr and the fediverse, so you can follow those accounts here until they see the light and decide to hop on over to the purple side.

Replying to Sam

Reading the comments on the initial PR for NIP-25, https://github.com/nostr-protocol/nips/pull/26 , inspired some thoughts.

Prefixing reactions with the "+" or "-" would allow for multiple emoji reactions to be sent at once, in the form of "+šŸ‘€ā¤ļøšŸ”„". This would allow multiple reactions like on GitHub or Discord, without overly spamming relays.

Supporting the exact same UX as the aforementioned apps, however, might require use of a different event kind, perhaps a NIP-33 Parameterized Replaceable Event. Backwards compatibility could be maintained by sending/storing both the new kind and a basic kind 7 "+" or "-".

Looking at this idea again, it's definitely too complicated. I'm now thinking the best ideas are either my original modification, or moving emoji reactions to a tag.

The tag would still allow any random emoji to be entered, but clients would only have to look at it if they were interested in displaying it. Trade-off being a slightly bigger message on the wire.

Doesn't that mean Damus is out of spec from your own NIP? The whole "It SHOULD NOT be counted as a "like"..." bit.

Also, how does Damus handle random emoji reactions, is everything just considered a like?

Reading the comments on the initial PR for NIP-25, https://github.com/nostr-protocol/nips/pull/26 , inspired some thoughts.

Prefixing reactions with the "+" or "-" would allow for multiple emoji reactions to be sent at once, in the form of "+šŸ‘€ā¤ļøšŸ”„". This would allow multiple reactions like on GitHub or Discord, without overly spamming relays.

Supporting the exact same UX as the aforementioned apps, however, might require use of a different event kind, perhaps a NIP-33 Parameterized Replaceable Event. Backwards compatibility could be maintained by sending/storing both the new kind and a basic kind 7 "+" or "-".

Brainstorming a better system for #nostr reactions. I initially thought just adding a "+" or "-" to the start of all emoji reactions would be a simple solution, but nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 pointed out that it would break some current clients. See https://github.com/nostr-protocol/nips/pull/509

More thoughts to follow.

I forgot to mention the main benefit of putting it on Glitch!

Hosting your own copy is as easy as clicking the remix button, signing in/up, and typing in the random name it gives you in the format wss://random-name-here.glitch.me

Whipped up a simple nostr relay on Glitch last weekend. Could be a nice starting place for anyone looking to host a relay or make one with JS.

Check it out at https://glitch.com/edit/#!/hello-nostr or just add it to your relays wss://hello-nostr.glitch.me and help me stress test it! #nostrdev

Doesn't stop the need for manual intervention, but muted IDs could be added to the subscription filters so the relay knows what NOT to send.

Yes. Install it on top of any linux distro to get access to everything in nixpkgs!

That's actually how I got started with nix :D