They also seem to be going after Terraform Labs, which is an active legal entity in South Korea (Edit: Actually appears to be Singapore now). Impeding their current work on (I kid you not!) Terra 2.0 may still prevent a future ponzi meltdown.
"Anything that gratifies ones intellectual curiosity." So clearly on-topic.
It's a flame-bait topic, no doubt, but the idea that this (progressive pressure leading to tolerance of girls being abused) isn't a topic for the intellectually curious is contentious to say the least.
Specifically, mainstream press and TV have not covered this until their hands were forced, so flaggers should probably clarify why they are doing so.
I do understand the distaste for flame-ish subjects, but that's ultimately down to the conduct of the commenters.
Good question. I googled, and it may be "unregretted attrition rate," or URA, which represents the percentage of employees that managers aren't sad to see leave the company — whether they part ways voluntarily or otherwise.
What files are in the purchase package? Does it have a vector version of the logo? 1024 x 1024 resolution doesn't sound like a lot for a number of purposes, eg print.
I would guess fork means code fork where your same wallet works on that seperate network. Farm usually means something that produces a yield, which either means a loan interest or a ponzi scheme.
It is a hit or miss, as some password fields don't get this. However, I personally fund it useful and use it about 100/% of the time in new signups/resets when available.
Yeah that's the problem though: A lot of websites don't set the password field to "type=password" or they don't set the second (verify) password field like that. Why do they do this? Either the web developer didn't really know what they were doing or they were given some very unique requirements (e.g. need to work with a legacy framework).
Wrong. There's random generation, and each randomly generated password is pinned to the site where it was generated. When you navigate to a different site, Firefox will generate a new password. There's no cross-site leaking.
Password is leaked and you want to change it all in the same browser session/tab since you created it for the 1st time? I mean, technically you could be living with the same tab opened for months but...
Seems they saw the submission and edited their response, appending the following:
EDIT 2022-12-20: There are at least 3 cases where this is desirable within a short period of time:
1. Filling password confirmation fields on the same page if we were not able to automatically do so.
2. Filling the same password on the next page
3. The password didn’t save on the change form so you need to fill it on the log in page.
Bug 1551723 will give the user the option to choose a new password.
It only generates the same password if the browser session is also the same, i.e. it generates a different password for the same domain if the browser was closed in the meantime.
