modderation

I'm early on in my Kubernetes journey and have opted to focus on Talos. Would you be able to share a bit more about the issues and limitations you encountered?

You can always order the pro parts along with a regular display from the regular Framework 13. Some assembly required, but the bits are all interchangeable, so you can have your non-touch display.

Alternatively, you can also "not touch" the touch display :)

Intel got a lot of attention during the keynote, but the Ryzen AI 300 series mainboards are available if you want them. It's one of the first few choices in the configuration flow.

It's either a a Career Limiting Event, or a Career Learning event.

In the case of a Learning event, you keep your job, and take the time to make the environment more resilient to this kind of issue.

In the case of a Limiting event, you lose your job, and get hired somewhere else for significantly better pay, and make the new environment more resilient to this kind of issue.

Hopefully the Wikimedia foundation is the former.

As a guess, large-scale volumetric or photogrammetric "datasets" could be difficult to stream over lesser interconnects.

Can this be generalized into a higher-level metalanguage? Notably, one called FURTRAN with broader support for other fuzzy creatures?

Depends on the setup, but programmatic access to a Gmail account that's used for admin purposes would allow for hijacking via key/password exfiltration of anything in the mailbox, sending unattended approvals, and autonomous conversations with third parties that aren't on the lookout for impersonation. In the average case, the address book would probably get scraped and the account would be used to blast spam to the rest of the internet.

Moving further, if the OAuth Token confers access to the rest of a user's Google suite, any information in Drive can be compromised. If the token has broader access to a Google Workspace account, there's room for inspecting, modifying, and destroying important information belonging to multiple users. If it's got admin privileges, a third party can start making changes to the org's configuration at large, sending spam from the domain to tank its reputation while earning a quick buck, or engage in phishing on internal users.

The next step would be racking up bills in Google's Cloud, but that's hopefully locked behind a different token. All the same, a bit of lateral movement goes a long way ;)

I'm guessing it'd look something like this on a 1-dimensional number line:

    --- >   | > >> . << < |   < ---

The dot in the middle would be the singularity, the pipes the event horizon, and the contents would be increasingly warped spacetime that may or may not exist, depending on your interpretation of things.

I think it's an interesting thought experiment. What would happen if the stock market were quantized to a blind one trade per-minute granularity?

I suspect this would put everyone on more even footing, with less focus on beating causality and light lag, placing more focus on using the acquired information to make longer-term decisions. This would open things up to anyone with a computer and a disposable income, though it would disappoint anyone in the high-frequency trading field.

How about "Vidja" -- the .fr domain seems to be available, the top google hit is for an IKEA floor lamp, and it is generally a silly English mispronunciation of "video" (you kids and yer vidja games...) :)

WORM prevents after-the-fact modification, but it isn't very helpful in the case of persistent threats.

The concern is that the tampering has already been committed to the backups. When was the "Break Glass" password last rotated? Is it protected by one or more Yubikeys that were manufactured before they fixed that nasty exploit? What other attack vectors are baked in through malfeasance or human error?