nostr:npub138s5hey76qrnm2pmv7p8nnffhfddsm8sqzm285dyc0wy4f8a6qkqtzx624 - I think I hosed my install of nostrcheck. It will not let me sign in. I tried to update the primary npub to be a different nip-05 and now it will not let me login. Just pops up an ! in a triangle, no additional info.
A) can this be prevented?
B) can the primary npub be the root domain as an option
C) Can I fix it on the DB side?
Best,
nostr:npub1uf5krsdawn6t8qq6c9uhsq5gtkk8jlzrau4se9gv9mfkzy4fr7yszdr7fw
A. It shouldn’t have given you any problems, I’ll check it.
B. What do you mean? I don’t quite understand the question.
C. Of course, we’ll solve it together.
I sent you a DM
I will reach out, but I am dealing with some family stuff. I got the dm and am looking forward to fixing it. Not to burden you with the details, but my mom is dying and I need to spend some time with her while I can, which seems like it might not be a long window of opportunity anymore. They just hit us with the news today that it will likely be shorter than we thought.
If an opportunity opens up in the near term, I will reach out and start the investigation, but idk what to expect right now.
In either case, I still want to debug it and see what we can find out about how it made it to this state.
I’m very sorry for what has happened to you. Life is fleeting, and I hope your mother spends her final days in the best possible way. I truly mean it, I’m sorry.
Whenever you’re ready, I’ll be available to help you, of course.
I figured out what was wrong. It was actually the changes I did to nginx that were misrepresenting the issue. I am able to login now.
I am just now getting back in the swing of life after the recent events, but I would like to know the best path to update to new builds of the v0.6.0 builds, if you have some time to provide them.
Hello, I’ll send you some instructions by DM 🤓
