> Google probably has the gear and the global distribution that they could probably keep pretty close over 30-60 days, but they are assuredly not trying to keep their own independent time standard.

Funny you should say that... https://developers.google.com/time/smear

Why are they totally different? For such an old airframe, the only significant costs are fuel and maintenance.

A revamp to the maintenance schedule that requires more frequent engine overhauls absolutely makes the economics of operating 777-200s even less appealing.

Because an attacker would never cover their tracks...

Indeed, being able to trust your audit logs is imperative.

> The bank instantly ruled in my favor and closed the case, issuing a permanent credit. I have never seen that before. They must be getting tons of Comcast chargebacks to do that.

I did the same thing, except I disputed a collections record on my Credit Report from either AT&T or Comcast. They also ruled in my favor quickly, and I was quite surprised that it wasn't a more difficult process.

Those are some rose tinted glasses. Not having to drive a check to the city utility office to pay the power bill is quite the improvement.

You can mail checks you know.

I will happily let the internet fingerprint my browser to not have to go back to mailing checks. I am guessing this is true of most non-HN people.

Sure, but we're talking about compiled packages being distributed by a package manager.

Yes but my point is: if I download the AVX version instead of the SSE version of a package and that makes my 1000 servers 10% _quicker_ that is not the same as being 10% more _efficient_.

Because typically these modern things are a way of making the CPU do things faster by eating more power. There may be savings from having fewer servers etc, but savings in _speed_ are not the same as savings in _power_ (and some times even work the opposite way)

Where on earth did you get this misconception?

Lived experience? With swap system stays up but is unresponsive, without it is either responsive due to oom kill or completely down.

in either case, what do you do? if you can't reach a box and it's otherwise safe to do so, you just reboot it. so is it just a matter of which situation occurs more often?

The thing is you can survive memory exhaustion if the oom killer can do its job, which it can't many times when there's swap. I guess the topmost response to this thread talks about an earlyoom tool that might alleivate this, but I've never used it, and I don't find swap helpful anyway so there's no need for me to go down this route.

> as the domain suggests

It suggests a couple of things...

Yeah, after the appropriate layers of VPN/Incognito/Tor/muted phone/etc I braved the link, and it turns out it's actually real, but that is still not a hostname I want connected to me in anyone's access logs more than once.

Good news, you can grab the source code and host it yourself on a less troubling domain:

https://git.j3s.sh/vore

It's under the NON-VIOLENT PUBLIC LICENSE v5, which is probably not open source, but should be fine for personal use if you're not an arms dealer or prison warden.

There's more RSS readers than you can count. No need to pick a proprietary one with a sketchy license when there are tons of great open-source options.

Odd conclusion to draw from only two data points over 30 years apart.

The devastation those two fires cost is quite large, though. And, those are just the two I know about, the latest because of the linked article and the earlier one because I lived very near the fire line and know multiple people who lost homes.

I always wanted a TiVo, but by the time I could actually afford (and use) one, Hulu was at it's prime.

Now Hulu is being shuttered

It's being folded into Disney Plus. That's a huge difference.