hey nostr:nprofile1qqsgzu4eypfy0h07nxmcxvs8stgrztarqksen7etaz37v437yz60pcspzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctcpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59uzkvpwz nostr:nprofile1qqsyy2wzruqsr27rhfzjx0shd6t4l20xwxa33fnj900hwf46y4z9l7gppemhxue69uhkummn9ekx7mp0qyfhwumn8ghj7mmxve3ksctfdch8qatz9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tc4w0e7l i've been seeing all the progress yall are making with frostr and was wondering if you are planning on advertising what's being worked on to nostr users?
it seems very promising but i don't see much talk about it which is a shame. theres also a few things i don't quite get.
how does this protocol protect shares that have not been compromised in a scenario where an attacker would have control over a share ? wouldn't the compromised device allow for a request to get something signed from other devices/shares and succesfully get it back?
i think i saw theres a way to make it so that only certain shares can make requests to others or something along these lines?
a detailed explanation on how to properly and securely adopt frostr for one's keys on that regard would probably be useful to new users.
richard
npub1l9r0...czrs
Notes (5)
nostr needs more ui/ux designers
nostr:nevent1qqs2ldnecevpxhvkjejqtuw2u6z4qwt5d9x35h8ek6kcnjnc8qsynmcprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsygpm7rrrljungc6q0tuh5hj7ue863q73qlheu4vywtzwhx42a7j9n5psgqqqqqqsx8uwp0
seeing nostr's true potential requires more technical understanding than usual and that's okay.
i don't see web of trust being the future of nostr or any open social app. wot limits people's reach by default, leaving the biggest voices with maximum reach - this is called centralization - we don't want that.
AI content isn't always bad, some content can be good as long as we see it like any other kind of content, with critical thinking. there will be more bots than humans in the future, it's something we have to get used to.
that leaves us with spam and content filtering problems, both can be dealt with on relays and clients.
nostr:nprofile1qqsdy27dk8f9qk7qvrm94pkdtus9xtk970jpcp4w48k6cw0khfm06mspp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg4waehxw309ahx7um5wghx77r5wghxgetk9uj8qus8 "Cannot read properties of undefined (reading 'url citation')", after getting data from models the screen turns dark and says a client side error occurred.
tried on multiple devices yet nothing changes