Oddbean new post about login | logout Good news: saved my #nostr key correctly and was able to sign out and in. Bad news: my avatar is still whack Af and it appears that way for @Kingbee too. Halp, my brainiac frens, I am at the end of my tech tether. https://image.nostr.build/94dbe3c8904602721dbadb8c9da7ca1b8c9bf77e8eeefb3a08bc5a649385eaac.jpg https://image.nostr.build/a12f21d4276740902cf8ecadc0569b82a27b37bd5bb6f18b43bd617e53980249.jpg
I see your animated avatar. Same as always
I don’t. This monstrosity is what I see… https://image.nostr.build/d7047aaa5869cd459c2f3504126a6584775cf5a27282908fc2056f506bdaca29.jpg
You could try adding a blastr relay. It broadcasts your changes to all major relays. Once you add it you can go into settings and save your pfp again. It will get broadcasted and maybe fix your issue. Try wss://nostr.mutinywallet.com
You’re amazing. It’s worth a try! Thank you!
Another thing you could try, in case you have a problem in the future, is to add wss://hist.nostr.land It’s a relay that does a backup of your profile and follows everytime there’s a change. If ever something seems wrong, you can go to hist.nostr.land in a web browser, login with a nostr extension and restore your profile or follows from a previous state. Works well. And it’s made by Semisol
Thank you. This is the error I get when I clock that link.
I don’t see the error. There is a known bug with relays though. When your follow list is greater than 1000 and/or when your number of relays is greater than 10, a lot of relays won’t accept your follow list. Not sure if that’s your issue
No. My issue is my avatar appears to me and @Kingbee as a blue robot. Otherwise, most everything runs well now. For a minute, all my settings got sideways in my whole phone system. https://image.nostr.build/a995168d6d2ea22549685832cb3cbec7629f8333b03d6f66e05f74c8f7b1594a.jpg https://image.nostr.build/09110b1dd51fcb63da47aeb5a9a4c05d48faaec23e2e74f1123fef148f19dd79.jpg https://image.nostr.build/78868b4e59c7219a28b05c2c810028361e12da46267fe8c19f6ed5af64eb4af6.jpg
You've already tried clearing the app's cache, right?
