I've heard of that too. They also have a mobile app, so you can do it directly from your phone.

Good point!

Lucky!

Cool, thank you for the reference! If I decide to pursue something like this, I will know someone to ask questions to.

That's cool. That would be something to consider if the developer will absolutely not entertain the idea.

Thanks! Those sound more like rewrites though?

Absolutely. I'm glad that I usually avoid links to them.

It can be used for either: https://en.wikipedia.org/wiki/FIRE

This is correct. I've been in two juries that went to trial, and each side got a handful of denials that they could use, each. Like 5 for my cases, or something in that ballpark. I think that the number is at the discretion of the judge, so because there is so much sympathy for the defendant, the judge may allow a much larger number of denials.

Disclaimer: I have no legal training and my trials were not in New York, so my comments could be inaccurate.

Edit: according to this article, this is the number of peremptory challenges (i.e., objecting to a juror during selection for no reason) each side gets - https://codes.findlaw.com/ny/criminal-procedure-law/cpl-sect-270-25/

2. Each party must be allowed the following number of peremptory challenges:

(a) Twenty for the regular jurors if the highest crime charged is a class A felony, and two for each alternate juror to be selected.

This is in addition to presumably an infinite number of juror dismissals for cause, like, for example, if the juror tells that the judge that they would not be able to follow the law.

Exactly this. Another factor in choosing TLDs is that they have different rules. Read those rules closely. Some of them make it much easier for them to take the domain names away from you, for things like copyright infringement, for example. .COM/.NET/.ORG have the strongest rules protecting your ownership, as far as I can recall. This is one of the reasons I stick to those old 3 rather than using newer gTLDs like .INFO, .BIZ, etc.

Just wanted to add something for future reference of anyone reading your post: after Canonical did this, LXD was forked by Linux Containers into a new project named Incus.

It's crazy that they didn't include all the "should" items in that list. If you read the entire section, there's a critical element that's missing in the list, which is that new passwords should be checked against blocklists. Otherwise, if you combine 1, 5, and 6, you end up with people using "password" as their password, and keeping that forever. Really, really poor organization on their part. I'm already fighting this at work.