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 - 42448 (npub1az5…meat). 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.
juraj / Juraj
npub1m2…lr8p9
2024-08-19 21:53:02
in reply to nevent1q…kvdn
Author Public Key
npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9Published at
2024-08-19 21:53:02Event JSON
{
"id": "fd08121106f27ebd0d4f309fdc8c1f9b3a715fd8b79a3c8babf362a27afb51c0",
"pubkey": "dab6c6065c439b9bafb0b0f1ff5a0c68273bce5c1959a4158ad6a70851f507b6",
"created_at": 1724104382,
"kind": 1,
"tags": [
[
"p",
"e8a9648028a5c0ddf62d32ea49d5df997e4539809433de00f3bdc51634ad4792",
"",
"mention"
],
[
"e",
"e05c18ba8be7781ac63a822de3f0033fb1e45c5e0561d51259c3df8115f6294b",
"wss://nostr.mom",
"root"
],
[
"e",
"97555a760d044dff1ebd5725005ab631532df4ee0880450c30291113dc8a967e",
"wss://nostr.mom",
"reply"
],
[
"p",
"dab6c6065c439b9bafb0b0f1ff5a0c68273bce5c1959a4158ad6a70851f507b6"
],
[
"p",
"d112df37f999e8e616652566e4ee666c5537c0479839e2c49d8fbbbf7c73c925"
]
],
"content": "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.\n\nI'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, ...\n\nI 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.\n\nWith 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.",
"sig": "97e4418193338986e8ffc0ad8ed2740307ab384a1c7a3349987b05188058b0b90bcded80a18681f7e73fc17489b6d58613426f62d413848fa595e6785e67f9c4"
}