Oddbean new post about | logout
 Equally safe 
 Bunker urls currently generated by nsec.app aren't sensitive. But there are different kinds of bunker urls, some of which are sensitive, so I'd say you shouldn't get used to treating them lightly. 
 Thanks, so I should treat them like nsec, but then if your app makes them not sensitive, then even better? Also, what do you make of the ncrypt method, do you know if that just gets inputted to an nsec field, and are you planning to add this or any other additional methods to nsec.app? Or do you feel your implementation of bunker url is enough? 
 I would encourage you to use your name@nsec.app to login where possible. If we ever start generating bunker urls that must be kept secret we will have big warning all over the place. 

We currently export keys in ncryptsec format, not many apps support it yet (Amethyst does). Importing ncryptsec is on the roadmap.  
 Thanks, I wasn’t actually aware of that being the primary method. So that is what I am being asked for by NoStrudel, where in the first instance I am only presented with the @ Nostr Address, and all the additional options are hidden behind the Show Advanced drop-down? 
 Yes I think so