

They know all this. They didn’t fire her out of ignorance.
Moved to frezik@lemmy.blahaj.zone


They know all this. They didn’t fire her out of ignorance.


There’s never going to be a better time to do this. Next election is a long time off. Making a clear statement of “establishment Democrats will either be dragged to the left or kept out in the cold” means they have to play. The potential downside of splitting the ticket and letting Republicans win by default is acceptable if establishment Dems are going to ignore their levers of power, anyway.


The “reality” where fascism backs down when you ask it nice?


The Darkest Brandon move would be to remove the DOJ policy on not investigating sitting Presidents. Many of these cases were clearly not under Presidential Immunity, and some weren’t even done while Trump was President. That should have consequences regardless of getting the job back or not.


Normally, you don’t want to commit code unless it’s been at least minimally tested, and preferably more than that.
All the CI’s, however, force a workflow where you can only test it by committing the code and seeing if it works. I’m not sure how to fix that, but I see the problem.


How did I know it’d be Uline?
You’re right on. As long as you’re otherwise following best practices for storing passwords, there’s no downside.
Those (?=...) bits are positive lookahead assertions:
Lookaround assertions are zero-width patterns which match a specific pattern without including it in $&. Positive assertions match when their subpattern matches, negative assertions match when their subpattern fails. Lookbehind matches text up to the current match position, lookahead matches text following the current match position.
The one (?!...) is a negative lookahead assertion.
The $& var doesn’t really matter outside of Perl. It contains the text of the pattern you just matched, but even within Perl, capture groups are preferred. Once used at all, it will slow down your program every time a new regex is hit, which is especially bad in long running web server environments. Gets used sometimes in short scripts, though.
What really matters is that the lookaheads don’t consume any text. In other words, the pointer that shows where in the text we are doesn’t increment; once we’re outside of the lookahead, we’re still right back in the same place.
So let’s break this down using the /x modifier to make it somewhat sane.
/^
(?!.*\s) # no whitespace allowed
(?=.{8,256}$) # between 8 and 256 characters (the '$' here indicating the end of the string)
(?=.*[a-z]) # has to be a lowercase ASCII alphabet char somewhere
(?=.*[A-Z]) # has to be an uppercase ASCII alphabet char somewhere
( # need a number, or a list of special chars on a US keyboard
(?=.*[0-9])
| (?=.*[~!@#$%^&*()-=_+[\]{}|;:,./<>?])
)
.* # consumes the whole string
$/x
Notes:
That last one has some nuance. We often say you shouldn’t put any upper limit, but that’s generally not true in the real world. You don’t want someone flooding an indefinite amount of data into any field, password or not. A large limit like this is defensible.
Also, lots of devs are surprised to learn that bcrypt and scrypt have a length limit of 72 bytes. A way around this is to run your input through SHA256 before giving it to bcrypt or scrypt.


Which still doesn’t matter, because SCOTUS doesn’t get involved in civil cases unless there’s some kind of constitutional question, and there is none here.


It’s a New York state civil case. SCOTUS would be going way out of their way to get involved in this one.


The “problem” with that tax is that if it’s applied fairly, it gets very big very fast. The damage to the road goes up with weight, but not linearly. Not a square factor, either. Not even cube. It’s to the fourth power.
Start applying that to long haul trucks and the whole industry will be bankrupt in a month. The implication being that we are all subsidizing that industry with taxes on roads. Including that one trucker with a “who is John Galt?” sticker on the back.
That said, this is also a very good argument for improving cargo trains to the point where most long haul trucking goes away.


I’m a little surprised the police didn’t already know about that method. Seems like they’d encounter enough CCTV footage that’d it’d be standard training.
I once again overestimate the training levels of the police.
I also hate the way “algorithm” has taken over the public consciousness. You can find people unironically saying “I don’t want any algorithm in my social media feed”, which is a nonsensical statement.