(This is a followup to nostr:note1xd96rfwvgugcnprshz6sekm24fln9ewgwmg3cxensruazpfca7ts5702d0 ) CC nostr:npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf
Passkey update: Bitwarden, Firefox, and Safari all seem to play nicely together now when it comes to passkeys. I’ve been creating and saving passkeys into Bitwarden whenever a site prompts me to set one up. Signing in with them works how I would expect. It’s not really a different UX from signing in with a username and password using a password manager.
And I think I’m defeating the purpose of passkeys by storing them in a central vault, but hey if websites won’t log me out or ask for 2FA so often that’s a trade I will happily make. The accounts I really need secured get the Yubikey.
Very cool. I’m going to work on getting mine set up. I couldn’t get the Igloo release to run on my Mac but I’ll try building it from source later.
Nostash is a Safari browser extension I created that stores your Nostr private key and signs Nostr events with it per the NIP-07 specification. It’s a fork of Nostore, which is no longer supported by the original developer, nostr:npub19pw5egjuhcsfsv42zkjtjs6nhpm69lnv8w2dacdyez7rvacrqnds6xjtwk , and no longer on the Apple App Store. Nostash is currently in beta on Apple TestFlight and I’ll release it to the Apple App Store soon. Please try it with your favorite Nostr web apps and let me know if you have any feedback. I’m only maintaining Nostash as the sole NIP-07 solution on Apple platforms and do not plan to add new features. I will be putting most of my energy into Yeti, a better native iOS signer app, which will hopefully supersede Nostash once it’s ready.
Thanks for doing this Terry! I just installed and it works well for me.
nostr:npub1gg5uy8cpqx4u8wj9yvlpwm5ht757vudmrzn8y27lwunt5f2ytlusklulq3 frostr is so cool. Is it possible to recover your key from the bifrost if you lose it?
So excited to see where this goes!
Double ratchet NIP — Signal style DM encryption on Nostr. Deployed on https://iris.to
nostr:naddr1qvzqqqr4gupzq3frhevd89d3kxt2nwxg9vpck6y4evptdq7scff6j4gx3kapltxsqq2kgjzlx338g4zsfymky6ncw4r5ys6nw9rrx2qhejc
Double ratchet invites:
nostr:naddr1qvzqqqr4gupzq3frhevd89d3kxt2nwxg9vpck6y4evptdq7scff6j4gx3kapltxsqq2kve6tw9c9xn202eny56edvfjhxmzh2gkkuaadaur
How does this compare to nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2ucwork on MLS?
Test 3
Test
Hah, somehow we ended up on the public net now. We’re not in our community anymore.
Whoah and now it is doing Reddit-style threading
I see it! 🍉
Our CEO nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 lives in New Zealand, but our company is incorporated in the United States (atm).
🤞🏻
If you're wondering how my day is going:
nostr:nprofile1qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszrnhwden5te0dehhxtnvdakz7qg3waehxw309ahx7um5wgh8w6twv5hsqgpjuxp8vd29p6ancknaztql3eajk52y8xkppfn7au7elkw9c68zg5xewh98 nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgnwaehxw309ac82unsd3jhqct89ejhxtcpr9mhxue69uhkwun0w4c8xtnxd9shg6npvchxxmmd9uq3vamnwvaz7tmjv4kxz7fwd4hhxarj9ec82c30qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshsqgrkcud2uwjfruweamz8ewshug5umfq38g9mkmn2u9mk6ajru2w2lg9xxprr and anyone else with an app on the app store, how did you handle the export controls for encryption? My understanding is that at least NIP 44/04 are considered proprietary encryption and need an ECCN approval from BIS.
Nos is marked as not exporting encryption.
I think we need to find a solution to automatically move, at least once, if a group gets banned from a relay. Based on the user interviews we have been doing this is a huge concern for stewards of Facebook groups and other big tech platform. Many of them have had their groups shut down before with no explanation and no recourse. Being able to give them an answer like “on Nostr the relay can boot you off but generally all your groups members will move over to your back just fine” would be a big sell.
Having a backup relay that you hit when the main relay is down or your group data disappears doesn’t seem like it’s too much to ask. Like on app launch if you can’t refresh data from the main relay grab the kind 39000 from the backup relay, see if it still has the main relay listed as the main relay. If it does, great, it must just be an outage. But if an admin has updated the metadata to indicate a new main relay you can just update your local group state to point to the new relay. The user doesn’t necessarily even need to know it has happened.
It's a lot simpler than in a twitter context. Since the relay + identifier is the full id of the group, forking happens explicitly by copying data and using a new qualified id. The outbox model in the narrow sense is irrelevant, and in a broader sense it's barely visible (unless nostr:nprofile1qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg6waehxw309ac8junpd45kgtnxd9shg6npvchxxmmd9uqs6amnwvaz7tmxxaazu6t09uq32amnwvaz7tmpv4nkjueww468smewdahx2tcqyrafsj7hmweg9ur7zmn6apajdg48hxuskujx53rhrux0ttjcqx84y4vxupk starts building multi-relay groups, then all bets are off).
I guess I thought NIP-29 left the door open to multi-relay groups, but rereading it I see that it doesn’t really. It says “fork the group so it exists in different forms -- still using the same id -- across different relays”.
Still I think having backup relays or something seems necessary to deliver on the Nostr promise of being able to take your people and data and go to another server.
What even is the gossip model in a NIP-29 context? Is it important? It seems like idea of a user-defined relay list is somewhat moot. The group needs to more or less say "we're using this relays" and unless you want to migrate or fork the group you maybe only need to read from one and publish to all of them? Have you thought about this yet? nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1lunaq893u4hmtpvqxpk8hfmtkqmm7ggutdtnc4hyuux2skr4ttcqr827lj nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr