Michael Dilger
Michael Dilger
Keep in mind that once I figure out how to do it, we may also need to say "Event not found" or something... to give feedback when it failed so...
I agree with your assessment of a problem. But maybe instead of a color we can think up how to represent web of trust figures now, so we don't chop...
Each message in your DM feed could be either weak or strong. Maybe we should highlight each message.
Here is a nostr event with a link to a non-existent note, that can be used to test the note-loading failure state: nostr:nevent1qqsplmeedff65ylasgu36udskczfyfgrp5td80t4m7fl27c7y57jr6qpypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z76kg24y
* The first one, identity/signer, we got stuck on an async bug so we still never got to be a nip46 client. * The second one it looks like didn't...
We implemented bookmarks, but we have no notification system for replies to bookmarked events. This should probably be a separate list of events to watch, different than the bookmarks.
Are you at the wizard page? Or are you already setup and now you want to import an nsec? At the wizard page it seems to work for me.
I simply cannot replicate. I can import nsecs from the keys page after I delete my identity and it gives me the field. So I don't know how to fix...
Here is the relevant block of code ````rust /// Import a private key pub fn import_priv(mut privkey: String, mut password: String) -> Result { if privkey.starts_with("ncryptsec") { let epk =...