GM!
#FreeAssange
There should be a key change NIP for Nostr.
Could be interesting too if you had it so that you had designated accounts to confirm a key change too. Like I would use my brother nostr:npub1ajv7m32k0cpgzha32qszsh304qusjvwwmavus0ttktzldms4xzusuftppj and maybe nostr:npub1rxysxnjkhrmqd3ey73dp9n5y5yvyzcs64acc9g0k2epcpwwyya4spvhnp8 or someone else I know really well in the space as ātrusted verifiers.ā Then if my key ever got stolen, even though both myself and the hacker could sign, I could make it so only I could transfer it to a new key by asking my verifiers to sign.
Maybe thatās too convoluted, but I feel like there should be a key cycling method regardless.
We need this
nostr:note1rwnxgwc2xr7z2wv6zmfjnn9cds9zdu2qf0z7rkp3vfrsf5cz267s84k3lu
nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft (who else) had one that Iām not sure was ever merged but is in use. It involves creating an event defining a future key you might need to rotate to and then open timestamping that event to ānotarizeā the time.
I have some sort of odd mental block on remembering the number or the site on this one but Iām sure Pablo can fill in the blanks.
This is the latest spin on that idea: https://github.com/nostr-protocol/nips/pull/1032
"Social proof(optional): the event contains a list of people that the master keypair attaches to the revocation certificate as `p` tags. These pubkeys are designated as trusted identities that can judge/signal if the new proposed identity is trustworthy or not"
There should be a key change NIP for Nostr.
Could be interesting too if you had it so that you had designated accounts to confirm a key change too. Like I would use my brother nostr:npub1ajv7m32k0cpgzha32qszsh304qusjvwwmavus0ttktzldms4xzusuftppj and maybe nostr:npub1rxysxnjkhrmqd3ey73dp9n5y5yvyzcs64acc9g0k2epcpwwyya4spvhnp8 or someone else I know really well in the space as ātrusted verifiers.ā Then if my key ever got stolen, even though both myself and the hacker could sign, I could make it so only I could transfer it to a new key by asking my verifiers to sign.
Maybe thatās too convoluted, but I feel like there should be a key cycling method regardless.
Simplex is still not good. We tried it with a group of people for about a month and some messages arrive a day later in the group chat (these were time sensitive), connecting with some people gets stuck even if we're both online at the same time... it's just unusable at the moment
A foolish and malicious cop out by Apple.
What this means for Mutiny users? If you've installed as a PWA, the data is segregated. With the new update, Apple will bounce you to safari, which still works. However, it'll be at a blank slate.
Be sure to back up your seed phrase!
https://www.macrumors.com/2024/02/15/ios-17-4-web-apps-removed-apple/
Apple digging their own grave
nostr:note12s5l8g8rsfxw5metjqenk6zgt5e8k4e83x5asnm8udacvrgz2q0qeu7jnh
nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9
nostr:note1rmwpc3m9j7nxy6ctq3tk4mv6t4qehgf8gv66lhyy0daw8yye6nas0sq9sf
š on it
Nostr-based app store. To install anything - not just nostr apps.
Working on a nostr-based app store š«”
They also pretend to ignore nostr and that rubs me the wrong way
The whole technical foundation developed/backed by the same company that strongly prefers the cathedral approach? Not sure
GM
Holepunch/Pear tech is cool. They wrote everything including a runtime.
For some reason I think it will struggle to get traction with developers. I hope I'm wrong.
The hypercore repos have been open source for a long time!
Fuck these psycopaths
nostr:note1yjzw99k743hfu25rz49dpr22hypxpx7s76xvz77ecvcxpf5mpqespxhw0s