If the 256c palette is generated from a -- potentially wild -- 16c palette then there is no guarantee anymore that 146 will indeed be the 146 I expect.
Turning 16-255 into the same kind of minefield as 0-15 seems very misguided to me.
1,582 karma · joined May 20, 2010
If the 256c palette is generated from a -- potentially wild -- 16c palette then there is no guarantee anymore that 146 will indeed be the 146 I expect.
Turning 16-255 into the same kind of minefield as 0-15 seems very misguided to me.
Much better than all three choices combined if you ask me.
First new word of 2026. Thank you.
I'm here for ASCII characters rendering pipelines, scientific breakthroughs, experimental filesystems, random wikipedia links, monospaced fonts, etc., not for silly politics.
The only explanation is that his OPSEC wasn't as rigorous as you think it was.
Reading the Wikipedia page, the most obvious gap would be the medical treatment he received in 2017. If he mentioned it publicly, then it was basically game over: finding him would have been routine police work at that point. The process that led to the interview by a German newspaper might have been leaky as well. There are so many opportunities.
As a rule of thumb, you can consider that while your OPSEC might _theoretically_ be the tightest in the world, you will eventually have to deal with other people and orgs at some time, who might not care as much as you do. In which case your OPSEC is really only as strong as _theirs_.
> Is it even possible to win a "battle" where you have to be perfect 100% of the time, while the adversary only needs to find one leak?
It is not. Simply because you can only control so much. A few years ago, there was a story about a mafia boss who successfully escaped justice for 20 years… until a Google Street View passed by while he was shopping groceries in a Spanish village. The guy certainly had the strongest OPSEC his money and relationships could buy, but it eventually amounted to nothing in the face of pure randomness.
All you can do is try to compartmentalize as best as you can for as long as you can, but something will eventually leak.
Also, it will be harder…
- the longer you keep it going,
- if it involves others,
- if you are married, have kids, etc.,
- if you have complicated needs (sex, drugs, health issues, etc.),
- if money is tight,
- if you are not geographically and socially mobile,
- if your public persona is too close to your real identity,
- etc.
> maybe
I know, it's more exciting to play the worst scenarios in one's head, but… _maybe not_?
Always on time, always charged, always precise, highly readable, packed with useful features… that thing went through a lot without any issue whatsoever. It only leaves my wrist when I feel like cleaning it.
Highly recommended.
Pawn shops, thrift stores, or their "modern" equivalents (EasyCash, CashConverters, etc. YMMV) would be a good start. I got mine out of a pile for 10€ at a countryside GiFi (French store) ten years ago.
Also I must say that my regex-fu improved dramatically after I picked Vim.
The journey starts by running the following command:
$ vimutor
in your shell to learn the absolute basics in about 20 minutes, which is largely enough to be able to perform quick edits on config files. If it didn't stick the first time, then try again. If it didn't stick the second time, then don't bother: Vim is not for you and that's 100% OK.At the end of vimtutor there is a strong hint that there is a lot more to learn. If you are still interested at this point, then run the following command in a Vim session to access the user manual:
:help user-manual
An _active_ reading of chapters 1-12 and 20-32 is pretty much required if you really want Vim to disappear. Skipping this step will make everything worse down the line. It may take something like a month or two if you only do that, and probably a couple more if you do that on the side.Now, a few recommendations…
Yes, you _need_ to read a lot and experiment a lot if you ever hope to become proficient with Vim. Just like with any "pro" app. It takes time and practice to become a pro at anything. That's life. Luckily, no one is expecting you to be a "pro" vimmer, now or ever, so you can do the learning at your leisure and even drop out if you have to. It's just a weird text editor after all and you still have VSCode.
Each chapter of the user manual builds up on the previous ones so you actually get a very gentle and progression curve. The wording is also very approachable so you don't have to be a CS major to understand it.
Don't go in with the project of replacing your current editor. This would be an absolute waste of time as it would give you false expectations AND a strong incentive to cut corners. Just… look at it. Poke at it. See if you like it and, eventually, dive in. Maybe you will end up replacing VSCode with it. Maybe not. Who cares?
---
As a programer, I have been using Vim as main text editor since 2010. I love it and I'm pretty good at it, active in the community and all, but I also use other editors and IDEs when doing so makes more sense and I'm not here to evangelize the masses. Vim is old and weird and powerful but a) that power comes at a (rather low, IMO) price and b) it won't solve all your problems so don't invest too much, emotionally, into that learning.
The real life of real people is still very different across the continent (the gradient from Oslo to Athens is striking), but how that reality is presented is important. And it is currently presented in a very polished, generic way.
In this case, SpaceX seems to be using UNIX timestamps(1) which is probably fed to a combination of Date and Intl to obtain a localized date string. Extrapolating the country where the user is located is not really rocket science either. But, if my context is somehow tampered with (VPN, internal clock, browser settings…), then I will get a potentially "wrong" date, for whatever definition of "wrong".
The problem is fundamentally the same on the server side because you can only rely on the information you get… which might be wrong.
So either you take the safest route, which is to display the local time of the organization or its UTC representation and let visitors figure out their local date on their own, or you take a somewhat riskier one, which is to try to display a localized date to your users and accept the potential flaws of the method.
[1] https://sxcontent9668.azureedge.us/cms-assets/future_mission...
Those texts don't say anything about cookie banners, though, only that users should be informed and have the possibility to make a choice. How that information and ability to make a choice are presented to the user is left to the site owner to decide.
For site owners, cookie banners are an easy way to comply without having to DESIGN that compliance into their site, which can be interesting but time consuming and expensive.
In theory, it should be possible to prompt the user for consent before storing something on their device but that would only work for stuff site owners have control over.
In practice, "cookies" are rarely used voluntarily by the site owners themselves but they are used a lot by the crap they add to their sites for tracking and so on via tag managers. And for that there is no better solution than a blanket cookie banner.
No wonder so many things are starting to fall apart around here.
> Officials said they haven’t uncovered a direct plot to disrupt the U.N. General Assembly and note there are no known credible threats to New York City.
Possibly related: janky playback of YouTube videos at large sizes (theater and full screen).
Both work just fine in Firefox and worked just fine last week in Chrome. I'm at a loss as to why this could be happening all of a sudden.
It's the protruding camera lenses being off-center. I don't mind the "protruding" part but, every time I interact with my phone lying onto a table or countertop or whatever, I have to bear with that silly tick-tack because the damn phone is not level.