charliedevolve

Roughly, "ruled by whatever you have on hand"?

When I upgraded to FF 60.0.2 the energy use on my Mac went off a cliff. Maybe you should try re-creating your FF profile?

I suppose that means that in our search for potentially life-supporting exoplanets, we ought to place a higher priority on systems with large outer planets.

The web clipper is the killer app for me as well. I've been looking for a replacement for a long time and thus far have found nothing comparable that is open, self-hostable, cross-platform & syncable, and saves web media or pdf natively. I will also kick in to a Patreon if a web clipper is promised.

While reading the exchange, I totally thought that you were conversing with a bot. Just scanning the resume for missing items and pointing them out in slightly different ways each time. Kind of disturbing, actually.

That's not what happened in this case. The statute was written in accordance with the style guide, which made it ambiguous, which is why it went to court in the first place.

Yes, and look at the avg response times. It looks likely that the webserver can't handle the load. The number of concurrent requests should be limited.

Signed updates aren't secure either. Ask Microsoft.

I think he meant that MySQL is the only supported DB for Wordpress, and while you might be able to get it running on another DB after jumping through some hoops, it's probably not worth the effort.

I also use Selfoss, it does what I need it to. Although the author's decision to override the Space key is odd. I comment that part of the JS and let the aggregated js regenerate to return that behavior to the browser.

Well, based on Assange's history, I wouldn't travel through Swedish territory if I were him.

Oh yes, I forgot that tcp/53 is mostly (if not entirely) for zone transfers.

Mixing in the source port might be a good way to fix that hash function.

Reduce the collisions how much, though? Are you using a port number == N*hashSize+53 for something else a lot? A collision is guaranteed for every connection to port 53, so isn't that a much bigger source of collisions? I think the hash size of 32 isn't the problem. It's the function.

Why did increasing the size of the hash help? Wouldn't the %64 (or whatever the new value was) just send all the port 53 sockets into the same bucket again? It seems you'd need a different hash function that provides more uniformity.