melvincarvalho on Nostr: "secured" server is not that secure, any admin, or the vps provider can access it, ...
"secured" server is not that secure, any admin, or the vps provider can access it, and also ive seen people hack the control panel. This is why mastodon cant really be trusted with payments, and misses out on alot of payment related use cases. But it does scale quite well. Lots of trade-offs. The way things are prioritized in nostr is quite centralized so some things can be a long wait. I'll note that revocation is a different problem to rotation. But really it needs to start with consistent profiles across clients which we cant even do yet. A good solution would be a consistent profile under user control, and to be timestamped, and allowed to evolve, for a small micro payment (fraction of a sat).
Published at
2025-02-15 22:48:25Event JSON
{
"id": "5091612efc1add2a7ef92c9368e11bab35cfd52b55381afcc821b922ecb685c7",
"pubkey": "de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645",
"created_at": 1739659705,
"kind": 1,
"tags": [
[
"e",
"263d9cd30edc7963cf4e82e1ff7a5ca1142f484a32433f25862fc3e7747c9fb9",
"wss://ditto.pub/relay",
"root",
"8757d9c788ddfa02b91056961aa1bced110fa7bd1716af2540c7d013aad337e5"
],
[
"e",
"f8fd38246bbdd5d3f85c8f3d4c0af016c2a42e961d1739f6d5b04457845a7f50",
"wss://ditto.pub/relay",
"reply",
"8757d9c788ddfa02b91056961aa1bced110fa7bd1716af2540c7d013aad337e5"
],
[
"p",
"8757d9c788ddfa02b91056961aa1bced110fa7bd1716af2540c7d013aad337e5",
"wss://ditto.pub/relay"
]
],
"content": "\"secured\" server is not that secure, any admin, or the vps provider can access it, and also ive seen people hack the control panel. This is why mastodon cant really be trusted with payments, and misses out on alot of payment related use cases. But it does scale quite well. Lots of trade-offs. The way things are prioritized in nostr is quite centralized so some things can be a long wait. I'll note that revocation is a different problem to rotation. But really it needs to start with consistent profiles across clients which we cant even do yet. A good solution would be a consistent profile under user control, and to be timestamped, and allowed to evolve, for a small micro payment (fraction of a sat).",
"sig": "a35b15b59487b73ce3fd5260cca8515858598cb4563deb561c969698115158d311c4ca39c59c2d4877efb06ccfa1c2ff84bdddae5782ebe6d9adfcae8bc9d7d6"
}