Hormesis is the scientific term for the saying: "what doesn't kill you makes you stronger"
Now you know.
So what should appear when users message the Group? If their actually name/pubkey is used, everyone will see it. I guess everyone is just anonymous to one another. Only admins/moderators can see who each user is?
Weird. Is it slow on scrolling or on everything else?
a use case for nostr: i need a support forum, like a telegram group chat. but unlike telegram, want to avoid scammers snooping around and sending people DMs, pretending to be someone else.
can of course set up a special relay with a blacklist and some other hardcoded conditions, but i don't believe it'd solve the scammers problem.
any ideas nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s ?
Very interesting! So, in your use case, am I right to assume you don't want members to know one another? Or do you just want to approve new users coming in and once they are approved, they can all see and DM each other?
I thought I was the only one breaking stuff. :)
It's not that rare. NIP-26 and NIP-46 are kinda doing the same thing by very different means. Kind 3 relay lists and NIP-65 lists are "similar". Kind 10000 for mute lists is also done as Kind 30000 with a `mute` label. NIP-04 and the new NIP-24 will both do Direct Messages.
As Nostr grows, we will see more and more alternative ways to do similar things.
I believe a WebSocket connection will be superior to any multi-part HTTP design in the long term.
That doesn't mean NIP-96 is bad or can't be used right now.
I am a full supporter of getting them all (NIP-95, NIP-96, NIP-97) merged and letting the best design win.
We just must not keep the current state of image hosting services in Nostr. That will be a disaster in the long run.
yep, I have long been a supporter of using NIP-95 for custom emoji packs, like the ones here: https://emojis-iota.vercel.app/
Not only what sort of risk, but you can put yourself into a different legal framework by the NIP choices you make. Things that are riskier for some are a piece of cake for others.
Why would you assume all relays will offer binary content hosting services out of the gate?
It's just like any other NIP. Relays that can support have the choice to do it.
Yep.
NIP-95 kept the NOSTR protocol intact and transferred content as base64 inside the event.
This one changes the protocol but doesn't use base64 in the event itself.
Both offer similar gains in decentralization. People can choose.
Super cool new NIP PR to decentralize NIP-94 Media from specific image hosts in a backward-compatible way. If this gets implemented, we can get all of the past NIP-94 content and re-broadcast it on as many binary-content relays as we want.
If image hosts go bust or start deleting content, there is a way out.
If *just* one side uses it, the other side might not see it.
For NIP 65 "relay sharing" to work well, both clients must support it. If this one side uses, the other side might not see it.
It depends on what "sharing" means. In NIP-65, you have your relays, I have mine. We don't share anything in the config file, but my app dynamically posts to your relay, and your app posts to mine. We just don't have that written down in our "relay list".
Snail slow? Which phone is that. Right now most phones are running butter smooth. I almost don't tweak the scrolling performance anymore. 🤔
