I completely agree. I guess you can turn off biometrics if you're in an environment where being forced to unlock your phone is a threat ( airports would be one of those envs for "normal" people ) but most people aren't going to do that
irq0
I don't think this is true. If I open my wallet from the lock screen then cover the front camera and close the wallet app my phone remains locked. Obviously it's a different story if you open the wallet app when the phone is unlocked
That being said, I do have some non-default FaceID settings
I believe us-east-1 is the default region so it's probably a case of devs not changing their region unless they need to.
Also, 1000s of companies use AWS. In issue in any of their regions is likely to have significant impact on internet services
A shoe horn is still a better spoon than option 3
She's welcome to chose spoon 1
1 - I don't want my spoons to be ribbed for her pleasure
2 - This spoon is simply incorrect
3 - This is the most disgusting thing I've ever seen
I'll choose option 4, its the least offensive option, but I'm not happy about it
I used to run PFSense ( pretty much the same as Opensense ) and really liked it but moved over to Ubiquity in the last year or so. Here's my 2 cents...
Go with Ubiquity if you want a single unified interface for managing all your devices. You'll have "soft vendor lock in", their kit will work just fine with a mix of hardware but it's best if everything is Ubiquity
Go with Opensense if you want complete flexibility in the kit you're using. I feel likeI had more fine grained control with PFSense than I do with Ubiquity but I think that's a symptom of how the UI/UX rather than the features
You can do the same stuff with both options. I'm very happy with my Ubiquity set up, I don't see myself changing anything anytime soon
You're saying that like it's a bad thing?
The CAB Forum only govern public CAs and certificates and the use of certs on the public internet. Your private PKI will be unaffected by the new changes. On top of that the change will be introduced gradually, the first reduction is in March 2026 and will limit certs issued after March 2026 to 200 days so even if you saw some impact for some reason you'd still have a couple of months to put a fix in place
Freshman need to accept the cert once (hopefully after checking the fingerprint)
Nobody is checking the fingerprint, nobody

I appreciate you taking the time to implement this and answering some questions! I have a follow up question- What's the benefit of using asymmetric encryption here? You're not signing the message ( you probably should imo ) and you don't appear to support sharing encrypted notes ( i.e a user provides one or more additional public keys that a note is encrypted for ). You're basically doing symmetric encryption with the pain of key management
It'd be simpler ( from a user and code perspective )to use symmetric encryption ( something like aes-256-gcm or ChaCha20-Poly1305 for example ) and use key wrapping to avoid encrypting user data directly and you'd have stronger crypto as a result
You're right that PGP is a valid encryption method but it's not very popular in the modern day because it's very hard to get right. Latacora has a great post on the PGP Problemand the Soatok blogs that u/litchralee linked are well worth a read too