Not with a tattoo gun, but yes, microneedle delivery is a new experimental way to deliver vaccines. It's less like a tattoo gun and more like a nicotine patch or a bandaid, though.

I don't think slashdot has had any actual developers working on its since the early 2000s. It's a mature legacy codebase, destined to run as-is until it can't anymore, then go away.

I'm not so sure there have even been enough incidents to decide if Waymos are more or less likely to run over an animal, but I *STRENUOUSLY* object to trying to soften it with 'made contact with' in the press release.

Okay. Thanks for all but admitting that exactly none of those needs are actually solved by the feature we're talking about.

You don't have a need. You just don't want your routine to be disrupted by a company taking away a feature that works for you. And it's entirely okay to feel that way. But it's not really a good reason to have designed such an overly complex and, at least in the real world, frequently under-performing protocol in the first place.

Keep telling yourself that I'm the one who doesn't understand the tech if it helps you sleep at night.

Then neither will casting, because casting by definition requires the TV to have Internet. It's a handoff process whereby the TV itself retrieves the content from the Netflix servers, and all your phone does is handle the authentication and key delivery plus playback controls.

You can do screen mirroring with a non-Internet-capable or disconnected TV, but not you can't use the ridiculously designed feature that I'm talking about.

So everything I'm saying is useless is useless for you, too.

My latest pet peeve is when Siri violates basic privacy standards by compelling data collection that isn't necessary.

A couple of days ago, I asked it for a list of restaurants near a particular town where I would be in a couple of hours. Siri immediately told me I had to enable location services for that query. What? Why? My query didn't ask for a list of restaurants near me. I asked for a list of restaurants near a different town, and more to the point, I gave both the name of the town and the state.

I attempted probably half a dozen different variations of that query, including things like avoiding the word "near", and Siri failed in the same way every single time, so this isn't just a one-off glitch specific to how I worded the query. It's a general problem with the way Siri handles queries that involve location.

This violates the first rule of location services, which is do not ask for the user's location unless you actually need the user's location. If the user is asking for restaurants in Panama City, Florida, Siri does NOT need to know that the user is currently in Charleston, South Carolina. It's none of Siri's d**n business. And more to the point, if Siri actually tried to do literally anything with that location data, it would be pretty much guaranteed to reduce the quality of the results rather than increase it, so having the data is just an invitation for any AI that might be involved to do something utterly stupid.

I really hope that Waymo's cars aren't relying on their Nader-beepers to avoid killing people. They should be (and AFAIK are) relying instead on their video cameras, LIDARs, and other sensors to stop the car before it hits the wayward kid/technician.

Yes, they should have done it the right way instead!

Err, what was the right way? It's not obvious to me, given that Microsoft doesn't have design control over the hardware its software runs on.

At this point, my biggest fear is that she will -- and then call me over to debug the AI-generated codebase, when it inevitably doesn't work quite right.

And you've done nothing to explain what the use case is. As far as I can tell, the use case is "Someone who wants to use their phone to control the TV instead of the TV remote," which is a tremendous amount of technological overhead for such a negligible benefit.

It's way easier to point your camera at the screen and do an instant sign-in on the TV than it is to get your phone connected to the right Wi-Fi network and cast to the right TV, so the use case would have to be pretty compelling to make up for what a pain in the a** it is when it works, much less when it doesn't.

Major correction here: about something that I have tried to use on many, many occasions, but never used successfully. There's a difference.

You won't read or engage further because you don't actually know any compelling reason to use it. If you did, you would have said what that reason was by now.

Not really, no. If I wanted to use the TV to do all of the networking and playback, I would have just used the TV's app to do it. The number of hotels I've seen where the TV supported Chromecast or AirPlay streaming but did not have a built-in Netflix app are literally zero.

From my perspective, casting is a complete disaster by its very nature. It relies on the display device having full Internet access, which isn't a given. Literally every time I've wanted to do casting, it has been because the TV set's Netflix app wasn't working because of a network problem, and it couldn't get access to the Internet, so I was trying to use the phone's network connection. By shifting the network connectivity back to the TV set, it makes the entire system completely worthless, because the exact situations where it could be useful are the exact situations where it isn't.

SpaceX can probably accelerate their flight schedule to accommodate Russian crew needs. There's the question of if Russia is able/willing to pay nearly $100m per seat. Their flights on Crew Dragon are currently paid through NASA in a seat exchange program where they provide flights from this site on Soyuz for US astronauts. They don't actually pony up the cash.

This launch site is also essential to attitude control of ISS. To refuel the ISS stabilizer thrusters and hold it steady while the gyroscopes are relieved periodically requires Progress modules launched from there. There isn't currently a backup plan for those services.

The figures can be entirely correct and still the answer can be "no". Why? Because Android might use the Linux kernel, but it isn't really a Linux distro in any meaningful sense of the word. And Steam Deck and Chromebooks *can* have some reasonable facsimile of a Linux development environment, but I'd expect maybe 0.1% of users to actually turn it on.

So most of those folks are Linux "users" in much the same way that TiVo owners were linux "users", i.e. they are using a device that deep down, at a level that the user is unaware of, runs some small subset of what a Linux distro typically contains, with a bunch of stuff on top that they mostly aren't in control over.

It's like calling Mac users UNIX users. It's technically correct — the best kind of correct — but grossly misleading.

Let's assume for the sake of argument that OpenAI and its competitors are trying to do the right thing here and make their AIs as harm-free as possible.

Not everyone will be that responsible, however. Now that it has been demonstrated that a suitably sycophantic AI can compromise the psyches of significant numbers of people, it's only a matter of time before various bad actors start weaponizing their own AI models specifically to take advantage of that ability. "Pig butchering" will be one of the first job categories to be successfully replaced by AI. :/

I didn't do anything crazy like actually read the article, but I did go as far as to read the third sentence of the summary, which began like this:

.... and that would seem to indicate that IPv6 is currently handling around half of Internet traffic.