Android uses one uid per app.
> There's no way around it: a non-IPng-having node will have to go through a translation box of some kind. Yes. Note that it doesn't need to be someone else's relay; anyone with IPv4 connectivity could easily route…
> Actually, we tried that I'm always fascinated by how many people think IPv6 adoption would have gone lightning-fast if we just used This One Weird Trick, where said trick has actually been tried and didn't help. They…
> The current design was implementable by zillions of cheap humans running cheap hardware. Yes and no. The current internet arguably does not work without a browser and a TLS stack anyway, neither of which is easily…
I was at a talk where he brought up exactly this (I also once did a talk alongside him, but that's a different story). He said there would be two changes: 1. It would have 128-bit addresses. 2. It would have end-to-end…
So, in your example, each request needs 0.1 core-seconds of PoW. Is that right? Or, since you're saying 10000 hashes across the entire machine and 1000 needed, then on a typical 96-core server you need 9.6 core-seconds…
I don't have a book, but my best recommendation would be: Learn how to measure. Whatever language you are using should have a profiler. Learn how to use it and look at how your code holds up. Look for surprises; those…
This is called “installing a cryptominer on your web page” and is generally considered illegitimate.
That's a completely different question, your claim was about parallelism.
Uh, is it resistant to parallelization across multiple sites? Because that's the situation for the scrapers. They're not trying to solve a single PoW challenge across many cores.
The sad part is that most employers don't care particularly about performance optimization skills (the economics don't work out, they can often just fix the problem cheaper with more hardware—and even if they can't,…
I once measured a 80s-communally-built event space with a laser meter (it was useful to have digital floor maps for event planning). No measurement was a perfectly round number. No angle was perfectly right. Nothing…
> Also to your point, this is why compliant peak meters use a mandatory 4x upsampling at 48k. This isn't due to latency, it's because the true peak (in the analog waveform) could be between samples.
It's behind a flag, if you want to play with it. (The easiest way is usually just to test in Canary.)
Did you actually test? I did it and it worked fine (and zooming in confirmed that the RGB bars are nicely preserved). Be sure to put your subsampling at 4:4:4.
Why do you think it wouldn't work for a JPEG? I just made one like that, and it worked just fine.
Just remove the A record, and nearly all the scrapers disappear. :-) (And then you get one email per month or so that “your host does not resolve in DNS”.)
Are you maybe confusing “downstream” with “mainstream”? Being “downstream” of a product means that you are a derivative of that product (your upstream), taking in basically all of their code and adding your own on top.
> And while they've recently announced more of this stuff will move to FOSS soon, at the same time their response rate to new bug reports has become worse than ever before, which is deeply worrying. A huge chunk[1] of…
MySQL has never been downstream of MariaDB.
They are using a fork, although nobody _really_ knows how up-to-date it is.
It's the one that nags you to upload all your IMAP passwords and email to Microsoft's cloud.
FFmpeg has its own native H.264, HEVC, MP3, Speex and AAC decoders. It's true that they don't have an H.264 or HEVC _encoder_ without calling out to external libraries, but they have a pretty good AAC encoder now, and…
> due to FFmpeg back then lacking any framework for code sharing between components and codecs Funny, I remember this being completely different; FFmpeg bundled ffserver, which transcoded to a bunch of codecs at the…
The idea of having two arguments to fread() is presumably to be able to do something else than all-or-nothing when there's a short read.
Android uses one uid per app.
> There's no way around it: a non-IPng-having node will have to go through a translation box of some kind. Yes. Note that it doesn't need to be someone else's relay; anyone with IPv4 connectivity could easily route…
> Actually, we tried that I'm always fascinated by how many people think IPv6 adoption would have gone lightning-fast if we just used This One Weird Trick, where said trick has actually been tried and didn't help. They…
> The current design was implementable by zillions of cheap humans running cheap hardware. Yes and no. The current internet arguably does not work without a browser and a TLS stack anyway, neither of which is easily…
I was at a talk where he brought up exactly this (I also once did a talk alongside him, but that's a different story). He said there would be two changes: 1. It would have 128-bit addresses. 2. It would have end-to-end…
So, in your example, each request needs 0.1 core-seconds of PoW. Is that right? Or, since you're saying 10000 hashes across the entire machine and 1000 needed, then on a typical 96-core server you need 9.6 core-seconds…
I don't have a book, but my best recommendation would be: Learn how to measure. Whatever language you are using should have a profiler. Learn how to use it and look at how your code holds up. Look for surprises; those…
This is called “installing a cryptominer on your web page” and is generally considered illegitimate.
That's a completely different question, your claim was about parallelism.
Uh, is it resistant to parallelization across multiple sites? Because that's the situation for the scrapers. They're not trying to solve a single PoW challenge across many cores.
The sad part is that most employers don't care particularly about performance optimization skills (the economics don't work out, they can often just fix the problem cheaper with more hardware—and even if they can't,…
I once measured a 80s-communally-built event space with a laser meter (it was useful to have digital floor maps for event planning). No measurement was a perfectly round number. No angle was perfectly right. Nothing…
> Also to your point, this is why compliant peak meters use a mandatory 4x upsampling at 48k. This isn't due to latency, it's because the true peak (in the analog waveform) could be between samples.
It's behind a flag, if you want to play with it. (The easiest way is usually just to test in Canary.)
Did you actually test? I did it and it worked fine (and zooming in confirmed that the RGB bars are nicely preserved). Be sure to put your subsampling at 4:4:4.
Why do you think it wouldn't work for a JPEG? I just made one like that, and it worked just fine.
Just remove the A record, and nearly all the scrapers disappear. :-) (And then you get one email per month or so that “your host does not resolve in DNS”.)
Are you maybe confusing “downstream” with “mainstream”? Being “downstream” of a product means that you are a derivative of that product (your upstream), taking in basically all of their code and adding your own on top.
> And while they've recently announced more of this stuff will move to FOSS soon, at the same time their response rate to new bug reports has become worse than ever before, which is deeply worrying. A huge chunk[1] of…
MySQL has never been downstream of MariaDB.
They are using a fork, although nobody _really_ knows how up-to-date it is.
It's the one that nags you to upload all your IMAP passwords and email to Microsoft's cloud.
FFmpeg has its own native H.264, HEVC, MP3, Speex and AAC decoders. It's true that they don't have an H.264 or HEVC _encoder_ without calling out to external libraries, but they have a pretty good AAC encoder now, and…
> due to FFmpeg back then lacking any framework for code sharing between components and codecs Funny, I remember this being completely different; FFmpeg bundled ffserver, which transcoded to a bunch of codecs at the…
The idea of having two arguments to fread() is presumably to be able to do something else than all-or-nothing when there's a short read.