Yeah, looks like a series of voluntary tags in the metadata. Which is important, and probably necessary, but won’t actually do much to stop deceptive generation. Just helps highlight and index the use of some of these AI tools for people who don’t particularly want or need to hide that fact.

How would they get past the other factor, the password?

If you’re gonna say “SMS can be used to reset the password” then it starts to sound like you’re complaining about insecure password reset processes, not 2FA.

Ok so most monitors sold today support DDC/CI controls for at least brightness, and some support controlling color profiles over the DDC/CI interface.

If you get some kind of external ambient light sensor and plug it into a USB port, you might be able to configure a script that controls the brightness of the monitor based on ambient light, without buying a new monitor.

Sometimes the identity of the messenger is important.

Twitter was super easy to set up with the API to periodically tweet the output of some automated script: a weather forecast, a public safety alert, an air quality alert, a traffic advisory, a sports score, a news headline, etc.

These are the types of messages that you’d want to subscribe to the actual identity, and maybe even be able to forward to others (aka retweeting) without compromising the identity verification inherent in the system.

Twitter was an important service, and that’s why there are so many contenders trying to replace at least part of the experience.

Yeah, Spotify is trying to force the same thing with a similarly muddled interface.

YouTube Music is still worse, though, in that it’s also tied to YouTube the video hosting service, plus a music streaming service, plus a podcast streaming service.

Legacy nodes (known in the industry as “mature” nodes) remain in use after they’re no longer cutting edge. Each run teaches lessons learned for improving yield or performance, so there’s still room for improvement after mass production starts happening.

I will add that nodes don’t stay still, either. A 2025 run on a node may have a bunch of improvements over a 2023 run on that same node.

And Google’s jump from Samsung to TSMC itself might be a bigger jump than a typical year over year improvement. Although it could also mean growing pains there, too.

Well, by the time the Pixel 10 comes out, it’ll be 2 generations after the iPhone that used a SoC from TSMC’s 3nm node (the A17, used in iPhone 15 Pro, launched September 2023). I’d imagine it’ll have caught up some, but will still behind while Apple is presumably launching something from TSMC’s 2nm or A14 node at the same time.

Instances don’t actually own the copyright to comments. The poster owns the copyright and licenses it to the instance. Which lets the instance use it, but not sublicense to others.

I think that it’s foolish to concentrate people and activity there even further, it defeats the point of a federation.

It defeats some of the points of federation, but there are still a lot of reasons why federation is still worth doing even if there’s essentially one dominant provider. Not least of which is that sometimes the dominant provider does get displaced over time. We’ve seen it happen with email a few times, where the dominant provider loses market share to upstarts, one of whom becomes the new dominant provider in some specific use case (enterprise vs consumer, mobile vs desktop vs automation/scripting, differences by nation or language), and where the federation between those still allows the systems to communicate with each other.

Applied to Lemmy/kbin/mbin and other forum-like social link aggregators, I could see LW being dominant in the English-speaking, American side of things, but with robust options outside of English language or communities physically located outside of North America. And we’ll all still be able to interact.

For my personal devices:

• Microsoft products from MS DOS 6.x or so through Windows Vista
• Ubuntu 6.06 through maybe 9.04 or so
• Arch Linux from 2009 through 2015
• MacOS from 2011 through current
• Arch Linux from 2022 through current

I’ve worked with work systems that used RedHat and Ubuntu back in the late 2000’s, plus decades of work computers with Windows. But I’m no longer in a technical career field so I haven’t kept on top of the latest and greatest.

Our data centers and backbone internet/Tier 1 internet providers are basically the best in the world. The US Department of Energy maintains a network with 46 Tbit/s connections between its labs.

Yes, but an absence of a proof of the positive is itself not proof of the negative, so if we’re in the unprovable unknown, we’re still back at the point that you can’t prove a negative.

Yes but can you prove by evidence that there is no milk in my cup, if I won’t let you look inside?

Those small USB drives are too slow anyway, often limited to USB 2.0 interfaces or slow flash modules. I’ve switched over to an SSD specifically because of how slow booting and installation is from a standard 10-year-old USB stick.

every distro I’ve tried has a strong sense that if you’re using the GUI you don’t need or deserve admin controls

It’s more that GUI programs can’t be trusted with root privileges. They’re not designed for that, and can break things in unpredictable ways.

I don’t think the First Amendment would ever require the government to host private speech. The rule is basically that if you host private speech, you can’t discriminate by viewpoint (and you’re limited in your ability to discriminate by content). Even so, you can always regulate time, place, and manner in a content-neutral way.

The easiest way to do it is to simply do one of the suggestions of the linked article, and only permit government users and government servers to federate inbound, so that the government hosted servers never have to host anything private, while still fulfilling the general purpose of publishing public government communications, for everyone else to host and republish on their own servers if they so choose.

Good writeup.

The use of ephemeral third party accounts to “vouch” for the maintainer seems like one of those things that isn’t easy to catch in the moment (when an account is new, it’s hard to distinguish between a new account that will be used going forward versus an alt account created for just one purpose), but leaves a paper trail for an audit at any given time.

I would think that Western state sponsored hackers would be a little more careful about leaving that trail of crumbs that becomes obvious in an after-the-fact investigation. So that would seem to weigh against Western governments being behind this.

Also, the last bit about all three names seeming like three different systems of Romanization of three different dialects of Chinese is curious. If it is a mistake (and I don’t know enough about Chinese to know whether having three different dialects in the same name is completely implausible), that would seem to suggest that the sponsors behind the attack aren’t that familiar with Chinese names (which weighs against the Chinese government being behind it).

Interesting stuff, lots of unanswered questions still.

Apple, too. The 2012 MacBook Pro had a high DPI display, and everything scales normally even when dragging windows over to non-HiDPI external monitors.

That’s not even getting into the mobile OSes, which have to deal with nonstandard display sizes and resolutions all the time, across multiple settings for accessibility.

I agree.

I especially love that it addresses the biggest pitfall of the typical “fancy new format does things better than the one we’re already using” transition, in that it’s specifically engineered to make migration easier, by allowing a lossless conversion from the dominant format.