At some point, it stops being a mob and starts being a vote. And while it makes sense to not allow people to drag random folks onto the platform just to vote your way, it doesn't make sense to limit voting on an important issue to the 0.1% of users who pay close enough attention to notice. So I can see both sides on this one.

Maybe the right thing to do is to require a certain level of activity to earn the right to vote, then dump the canvassing rules. That way, any canvassing would only serve to increase turnout, rather than truly padding the ballot box.

Yes:

https://en.wikipedia.org/wiki/...

L1 is where you want to put solar observatories. L2 is popular for not-solar observatories. L4 and L5 not as much, but there are some satellites like Stereo A and B that passed close, and the ESA plans to put a solar observatory actually at L5.

I was curious WTF you're talking about so I looked up the quote. Poettering was proposing socket-based activation where an infrequently used process, for example, sshd, would be launched when a connection was made rather than idling in the background at all times. You know, like process-based webservers do all the time.

It would have pretty much zero effect on your use case even if it weren't completely optional.

As for the accuracy of the example in the actual quote, excluding phones, which usually aren't running SSH, about half of Linux machines are web servers, another third are cloud machines hosting containers, and another ~10% are file or email servers. The vast majority of those are going to be running SSH for occasional administration. Machines hosting remote X connections are going to be a minority.

Yeah, this is apparently where the water usage numbers come from. Somebody makes up a stupid number and then that gets repeated over and over.

Tracking down the source of silly datacentre water usage was a bit of a sport for a while. It seems a lot of it traces back to a single writer who sort of picked a number.

They are not unsafe, they just unfortunately produce the same / similar waste "standard reactors" do.

One of the neat tricks CANDU reactors can do is burning the "waste" from "standard" reactors. They can also run on thorium.

It's not an either-or discussion? So you're going to pay for both things to happen?

Yes? Canada's solar, wind and storage capacity is all growing at double digit rates and BC just finished an enormous new set of hydropower dams.

The way things are headed, the only way people are going to be able to obtain money to pay for those widgets is via social welfare programs.

Doesn't even need time code. FCP lines up the files by matching the audio, mostly, IIRC. Also AFAIK, digital cinematography is pretty much the norm at this point, so film likely doesn't factor in most of the time.

Final Cut Pro can already basically do that, and has been able to do that for several years. Just create a multicam workflow and tell it to synchronize by audio. Not sure how well it works if you're dealing with hundreds of short takes though; I've only used it to line up hour-long continuous shots.

Then again, as cheap as storage is, I'm not sure why anybody actually stops the cameras and audio recorders anyway. If you want to have a private conversation, you can always step off the set and do it in a hallway or whatever.

That makes the narrative that data-centers are 'water hungry' very effective at causing unrest.

Which is probably why that narrative gets pushed so hard. You CAN build a datacentre with evaporative cooling and that will use a lot of water. You can also build one with a closed loop and radiators that doesn't use any water except for the original fill. You can even build one that's air cooled and doesn't use any water at all.

All of those options also apply to anything else that needs to be cooled, which is pretty much everything.

Scanning for Starbucks cups, flagging possible continuity errors, pose estimation and tracking for motion capture, inserting CGI, rendering, there are all sorts of boring tasks that could be automated or improved if already automated.

The iPhone 6s (released in 2015) got a security update last month. So that's almost 11 years and counting.

How can you tell how many red balls there are in the bin if you don't properly sample its contents?

Because I told you:

"a bin full of blue balls with one red ball in it"

If we dropped 8% of a system's capabilities each revision cycle, pretty soon there wouldn't be much left.

The argument that changes to support the majority use case compromise important minority ones is a reasonable one. You didn't make that argument. In what I presume was your effort to be pithy your brain cast "most" to "all" and you provided a single counterexample.

Define "enough". Even 1 percent of the federal budget would be 74 *billion* dollars. The budget shortfall for road maintenance in the U.S. is about 86 billion, so even if it is only 1%, that money would be enough to almost completely fix a major problem that affects us all.