Replying to Avatar Juraj

I am working on collective identities on Nostr, such nostr:npub1w8y9gff9t3uukezqwrvl557uqca9mgj2w23qh0c5hh4758vr03nq8plssr.

It is basically an anonymous microblog based on Nostr. But you don't have to use Nostr to use it. You can read it through

https://prostate.npub.pro/

and write through clicking the link, or here:

https://cypherpunk.today/static/prostate-poster.html

You need to know the password to post, the key is derived from it. So everyone who knows the password can post. No one has any additional privileges, the password is direct knowledge of the private key.

You spread the password enough to enlarge the anonymity set, but not too much in order to not degrade the quality and vibe of the account.

Code here: https://github.com/jooray/anonmicroblog

Nerdy, mostly useless. Have fun!

Similar concept: many nostr npubs are actually controlled by multiple posters. You wouldn't know if this account, for example, is being used by a few of us sharing the same nsec.

This is also possible with traditional username/password controlled social media, though that can be vulnerable to a rogue sharer changing the password (usually, there are additional verification steps required to change passwords, eg email, not insurmountable).

Reply to this note

Please Login to reply.

Discussion

Yes, they are basically sharing nsec, only you can just tell them the password, they don't even know there's an nsec. It's calculated in JavaScript on the page. So this works for communities that think they are blogging online.

I've migrated one such community that is operating since 2006 to Nostr - nostr:npub1az5kfqpg5hqdma3dxt4yn4wln9ly2wvqjseauq8nhhz3vd9dg7fqv5meat. The backend was ugly PHP and shell scripts, now it's Nostr native, but the interface to the users looks exactly the same, many probably did not even notice it's on Nostr. But now you can repost, zap, ...

I was thinking about sharing password on traditional social media, but for several of these communities they would probably be cancelled. And changing password is a problem. Another problem is an e-mail, or the need to KYC in some cases. With shared nsec, no one has any extra power over the account, with traditional social media, the person that controls the e-mail has extra power and possibly extra responsibility.

With the Nostr approach, all there is are one to four static files (HTML / JavaScript), which can be hosted on blossom drives. And the only thing people need to know is the password.

Thanks for the added context. I was pushed to explore npub.pro a bit more but am still trying to figure that one out. I've heard of draft nips to define how every nostr relay can serve http (or html), which sounds interesting. I should try to make some time to read further.