The match statement is cleaner.
With the sequential if statements, it might seem on a casual read that both if statements could pass - you’d catch both warnings and errors. Only by looking at the conditions do you realize that only up-to-1 of them will run.
With the match statement, it’s very immediately obvious that only one of the commands will run.
AI is the new tobacco.
“More are in the works”? Please no. AI wastes too much energy to produce fakey slop.
Just get someone to draw their idea. It’ll look better.
According to the last paragraph, the vulnerability is in reading the archive itself, not the decompressed contents.
Gonna give this a try on my work computer!
Yep. Although I have definitely seen people over-rely on calculators and make errors with money because of it.
This. Nix on SteamOS works great and gets you access to a lot of packages, easily. Set up Nix, then Pandoc is just right there.
It’s not your computer; it’s their computer. Do not ever forget this.
So if there’s anything personal you want to use a computer for, don’t use their machine for it. Use your own.
This looks great. I’m try it out today! I love that it handles MMS correctly.
If you have a PS5 and a Linux machine, Chiaki is amazing. Thanks for sharing the update news!
Whatever you say, day-old account. Unless you have some examples to share?
“Javascript was on during this test.”
I always liked the Excelsior class. (Judging by the replies, I might be the only one!)
I’d think that time travel episodes should be considered based on what time the crew is coming from, instead of where they go. So Voyage Home is still between STIII and STV, and First Contact is between Generations and Insurrection.
This will lead to minor troubles, mainly with Enterprise, since it has a few references to First Contact and The Tholian Web.
Also there’s that one far future episode of Voyager where a copy of the Doctor has to clear Voyager’s name, which doesnt involve time travel and must therefore be watched between seasons 2 and 3 of Discovery.
I acknowledge that the idea is amusing.
Let’s be clear: anything that prevents devs from pushing to a branch will necessarily result in code being isolated on a dev’s local machine. This is always a bad idea, and will always lead to lost work. I’ve seen it happen too many times.
Pre-commit hooks and pre-push hooks must be skipped, and eventually deleted. Every single time.
I’ve been loving Jujutsu VCS. It’s a terminal app, works on all 3 major desktop OSes, and makes it so easy to manage efforts across multiple branches.
Also, jj undo is like a gift from the gods.
I have it working through a program called Chiaki which is much easier to set up than what you described. Please give it a try! You should be able to install it via desktop mode, using the Deck’s built-in package manager.
A real human artist, who can’t draw hands, and who probably has a name. Who actually finds this convincing?
https://i.imgur.com/DiRNxEY.png https://i.imgur.com/ZUxrFfp.png
Don’t let AI draw hands. Or anything.
It’s funny how every poster who criticizes Signal inevitably makes a technical error. In your case, the claim that “Basically if you are an organizer, criminal, government, part of a hunted opposition, you will leak the whole core group structure of your org with attached phone numbers” entirely lacks basis. The Signal client - the OSS part we can and do control - does not divulge phone numbers.
You have this theory that Signal’s servers are storing communication records. (While there is no evidence to support this, it’s valuable to consider what they could do.) So the data that would be captured here is a network of hashed phone numbers and literally undecryptable messages. It’s impossible for the adversary to determine any phone numbers they don’t already know this way.
And since you can make a Signal account with a burner phone and create a “username”, even a known phone number becomes useless against targets who don’t want to be identified.