It never worked with my nsec. I am not sure why.
Login to reply
Replies (12)
It works if your nsec was generated initially in white noise. So either you start off with white noise or you have a burner nsec alt.
Yeah, that sucks.
Unless there is a way to prove the alt is 'your' alt, I agree. If we could solve the key rotation problem at have it still work with their method of key rotation then maybe it would suck a lot less.
That's like worst case: The app asks for your "nsec" but other than having leaked your nsec to yet another app that now can rug you (on purpose or by accident), you don't even get anything in return. A bit like those pages that ask your contact details and CC number before telling you the product is out of stock.
VocΓͺ tentou ir em :
"Developer Options" > Delete all key packages from Relays > Publish new key package?
Tive esse problema no White Noise, mas depois que fiz isso, funcionou. Γs vezes tambΓ©m Γ© um problema de conexΓ£o.
Se vocΓͺ clicar em Login, sair do app e voltar, o Key package pode bugar e nΓ£o funcionar de primeira. Precisando resolver no Developer Options.
#WoT fixes this
i used white noise to dm the "white noise support" account. they either never replied or my app is broken enough that i never got it
Again, from an engineering perspective, no it doesn't. Grandma doesn't know what that means.
trust isn't an engineering problem. neither is identity (or pseudonymity).
Yes but having things 'just work' is. It all has to happen behind the scenes.
It might be a too large follow list. Or some advanced outbox model config, not sure.