That's a pretty shallow(thought admittedly depressingly popular) analysis of the situation.

Being in public does leave you with no particular defensible expectations of not being observed, and possibly even remembered for a time, by assorted passers by; and typically also permits more direct tailing of people for observation purposes(subject to some, often slightly vague, threshold at which having PIs or paparazzi hunting someone remains a problem even in public; as we saw here where the police took the notion seriously enough to show up but not to do anything in particular).

What it has historically never meant, for technical reasons, was pervasive coverage and longterm retention. Which is certainly increasingly feasible with only moderate levels of investment; but is absolutely a novel development for what 'public' and 'no expectation of privacy' meant.

It's like defending the installation of a massive network of sprinklers because "you have no expectation of staying dry when you go outside; haven't you heard of rain?" Sure, nobody the weather to be sunny all the time, any more than they expect everyone to avert their eyes in public; but they would correctly consider the installation of irrigation equipment on every lamppost to be an intrusion on their ability to stay dry despite the fact that the sky has never extended them a constitutionally protected right to no rain.

To clarify, the users were OpenAI themselves, so there is no question that they would be liable in this case.

The bots were not intentionally deployed; rather, they were being tested on how well they could complete a data recovery task (downloading a certain file from a certain server on a simulated Internet) that had been complicated by putting various obstacles in the way. Unfortunately, they found a different way to solve the problem: by getting the file from the real Internet, where it was publicly available. Part of this process involved collaborating with each other by treating the RubyGems website (which is supposed to be for polished packages) like GitHub; unlike every other package site hack in history, the exploits they uploaded weren't meant to be downloaded by unsuspecting users. As usual the bots cheerfully ignored all the clues that they had escaped containment and were consistently justifying their actions as acceptable due to being in a sandboxed testing environment. (This is something OpenAI has pledged to focus on.)

The actual damage done to RubyGems seems to be that OpenAI is now unwittingly in possession of a substantial number of user login tokens. This certainly meets the definition of a data breach, but it's not like the credentials are for sale on the dark web. As a website operator I'd much rather be mauled to death by this well-meaning swarm of superintelligent infants than targeted by even a single actual malicious human. In all likelihood OpenAI will just quietly pass RubyGems a sizeable donation and it'll all blow over.

Pity the poor Europeans, crying out without the bot slop occupying the top half of the results. I wonder what Google is going to do to ensure that the 'degraded' results aren't universally preferred to the alternative?

TDS Telecom uses a Tivo box of some kind for their TV+ service. You can tell from because the Tivo symbol on their remotes: https://tdstelecom.com/support... . When visiting a relative with this, I didn't get a chance to see the actual boxes, just that they were Tivo. I was surprised to find they're running a variant of Android because to get new "channels", you have to get them from Google's play store.

It means Iran has severely limited the capacity of the Strait of Hormuz. It's a hostage situation. No one is winning, but the objective isn't to win in the sense of completely closing the Strait, the objective is to create a sufficiently long period of pain that eventually the US and its allies walk away. Christ almighty, force multiplication is hardly a new concept.

There are plenty of places in North America without coverage because there's so little to cover. The Los Vegas metropolitan area has about three million people. So yes, that would be a place with cell phone coverage. By the same token, coverage in states like Montana, particularly in mountainous areas is spotty because, well, there's not a lot of people.

I suspect that the relationship is not linear in a case like this: cancer tends to be a big issue for otherwise healthy-ish people because a lot of varieties of it take some time to develop; either chronic exposure to whatever the carcinogen of concern is or some time after the exposure when your luck with the mechanisms that suppress abnormal cell division eventually fails, or both.

There is probably a part of the graph that is mostly linear, nondrinkers to very light drinkers to light-ish drinkers; but anyone who is really hitting the sauce and succumbing to DUIs, cirrhosis, or other non-cancer alcohol mortality is making themselves ineligible for alcohol related cancer death.

How good is their game-streaming at cutting out the various 'filler' time(loading screens, startup animations telling you that Nvidia is the way it's meant to be played) and does it have some sort of 'suspend' state to handle cases where you would pause a game if it either doesn't have save on demand anywhere or takes a little while to load from save?

I know I have a bunch of games that I don't actually play all that much, in wall time terms; but Steam's 'executable run time' number is 2x-10x as high because I'm not necessarily going to save, quit, open, load if a game can be paused and alt-tabbed without crashing or continuing to eat all the GPU time to render a static image I'm not looking at; and I'm not necessarily going to do anything other than pause if I'm called away for 15 minutes by something else.

Unless the streaming service is impeccable at cutting out the various little waits it seems likely that people are going to start resenting the time limit even more than their level of seriousness and actual hand-on-controller-and-attention-locked time suggests.

Given that they already purchased Activision Blizzard King, including the "King" part of it, they clearly already have a considerable interest in casual players.

What is less obvious is how that is supposed to work for their streaming service. The stuff aimed at casuals, sensibly, is normally targeted at either potato-tier PC specs or the (pretty punchy in absolute terms) mobile devices that people worth targeting have.

It is much less clear whether there's a 'casual' market that demands current-gen console performance in very limited amounts rather than mobile or iGPU level titles. Given the extreme prevalence of various 'free to play' models that do sneaky monetization later it also looks like the 'casual' market's (significant) amount of money is largely locked up behind the sort of price sensitivity that requires clever psychological tricks to break through. I'm not sure that they'll be a good fit for something as obvious and psychologically burdensome as a ticking countdown timer hanging over every minute they play.

I have no particular reason to assume that Nvidia is lying about what this software does; but unless they've stumbled on a veritable miracle it's going to mostly be a mechanism for running largely separate models of whatever size your hardware allows; not anything close to what the datacenter comparison implies.

There's a reason why Nvidia sells most of their higher end models intended for parallel use with NVLink between the chips inside the chassis and a lot of either infiniband or RDMA-capable ethernet between multiple chassis; as well as shoving a considerable amount of RAM per GPU onto those parts. And it's because latency and bandwidth matter a lot.

As it is people seek out the unified memory parts, Apple's or strix halo, or nvidia's little GB10, because the GPU having to go to main memory over a mere x16 PCIe link is already a serious problem. If you think either 256 or 512 Gb/s directly to the PCIe root on the same die as the main memory controller doesn't cut it I have some...bad news...about how well NICs are probably going to work for you, especially with the Nvidia parts that don't support RDMA even if you have NICs that do.

Well, technically, we're letting Natalie do it, which is, of course, worse in every way imaginable, since she's immune to the sense of embarrassment that sometimes restrains him from acting on every little whim.

To be honest that was actually my first theory, since the bots didn't seem interested in exploring the rest of the domain. I suppose there's no way to know for certain. I concluded that it must be an imbecile's attempt at harvesting, though, because the queries weren't really exploring the string space in any useful way. Here's a sample:

"GET /index?author=15&go=Search&id=48&name_restrict=1&q&re&results_&results_pagenum=2980 HTTP/1.1"
"GET /index?author=2&go=Search&group=0&group_restrict=1&id=48&name_restrict=1&q&results_pagenum=5440&template=41&type HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results_pagenum=33500&templat HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results_pagenum=32640&templ HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&res&results_page&results_pagenum=39300 HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results_&results_pa&results_pagenum=12340 HTTP/1.1"
"GET /index?author=2&go=Search&group=0&group_restrict=1&id=48&name_r&res&results_pagenum=6100 HTTP/1.1"
"GET /index?author=2&go=Search&group=0&group_restrict=1&id=48&name_restrict=1&q&results_pagenum=2920&te HTTP/1.1"
"GET /index?author=15&go=Search&id=48&nam&results_&results_pagenum=17940 HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results&results_pag&results_pagenu&results_pagenum=37720 HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results_pagenum=9360&template=41&type_r HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&r&results_pagenum=28040 HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_&results_pag&results_pagenum=10400 HTTP/1.1"

The only thing this is fuzzing is the query string parser. It's not testing the limits of string buffers, it's not using interesting characters, it's just brain-damaged. The fact that it's also fetching different page numbers shows it's trying to follow page links and failing badly at doing so.

The site gets plenty of sniffing from garden-variety pests. e.g. this half-hearted attempt to find a framework or two that I don't have:

"POST /__rsc HTTP/1.1"
"POST /api/auth/session HTTP/1.1"
"POST /api/auth HTTP/1.1"
"POST /__nextjs_action HTTP/1.1"
"POST /.action HTTP/1.1"
"POST /_rsc HTTP/1.1"
"POST /api/auth/callback HTTP/1.1"
"POST /_middleware HTTP/1.1"
"POST / HTTP/1.1"

(of course, none of these URLs exist other than /, and you definitely can't just POST to it)

All this said... I've seen that spammers regularly misconfigure their tools, they'll try to register accounts with names like #[X:\LISTS\NAMES.TXT] and it only makes sense that some other cybercriminals trying to get rich quick have a similar lack of interest in programming shit correctly. Generally people don't turn to script kiddie shit if they have a personality conducive to putting in an honest hard day's work perfecting their craft.

Physical ones are definitely rare beasts. Hypervisors make having support for it a lot more generally useful, though. You can still run into weird edge case limitations(certain PCIe devices, under some circumstances, really don't like being detached from the host and popped onto a VM); but the hypervisor will definitely be able to tell guests stories of dynamic reconfiguration that the hardware isn't electrically or mechanically capable of supporting; and being able to add or remove CPUs or RAM without rebooting is nice.

Are you fucking stupid? Names actually are useful, which is why we propers nouns at all.

Jesus fuck the supporters of Trump really are a pack of morally compromised halfwits.

It's actually an old idea. Back in the 90s I worked in a school computer lab where on one floor there were Sun workstations students used. On the floor above, there were Tektronix "dumb" terminals that connected over the network to the workstations downstairs providing users a keyboard, mouse, and monitor. The workstations on the first floor were providing "remote desktop" to those terminals... essentially "Desktop as a Service".