I read parent comment "grew 35% last quarter" as (income on 2024-09-30) is 1.35 * (income on 2024-07-01)
The balance sheet shows (income on days from 2024-07-01 through 09-30) is 1.35 * (income on days from 2023-07-01 through 09-30)
These are different because with heavily handwavey math the first is growing 35% in a single quarter and the second is growing 35% annually (by comparing like-for-like quarters)
ASCII already has designated bytes for unit, group, and record separators. That aside, a big drawback of using unprintable bytes like these is they're more difficult for humans to read in dumps or type on a keyboard than a newline (provided newline has a strict definition CRLF, LF, etc)
There is in fact a reason those ASCII 'characters' should stay unprintable: the 0x00-0x1f (except Tab, CR, LF) range is explicitly excluded as invalid in a whole bunch of standards, e.g. XML.
I am not a Trump supporter but the headline is completely incorrect and disingenuous. It seems like there's a game of telephone happening for the quote "you're not going to be able to sell those cars", but the context of him saying this was for an import tariff on electric cars built in Mexico by Chinese companies.
> ["you’re going to not hire Americans and you’re going to sell the cars to us. Now, we’re going to put a 100% tariff on every single car that comes across the line, and you’re not going to be able to sell those cars, if I get elected"](https://www.rev.com/blog/transcripts/donald-trump-speaks-at-...)
I don't care to discuss the nuances of this policy and am not saying this to support him, but journalism like this taking stuff out of context and creating a strawman (even if accidental) is really irritating.
Ah, that's an interesting point. I haven't tried to correlate that, but it must be true. For example, the screensaver never seems to appear during Zoom calls!
That might also be implemented as "don't start the screensaver if the camera is in use". Easy to detect in either /proc/ or /sys/, I forget which one I was fiddling with.
I am curious to see benchmark results for the same use cases but with 10ms and 100ms latency added between the client and server. It looks like the bench currently just stays within the same machine.
I do not often operate below application layer, but as I understand it both the HTTP and SSH layers would add back-and-forths from client to server that UDP does not perform. Would UDP over HTTP over SSH have a slowdown steeply (but linearly?) correlated with the ping to the server? And (>linear) increased effects on packet loss? Crowbar seems to only do HTTP, so saves some considerable amount of backs-and-forths... but doesn't have the benefit from websockets...
You’re right, that’d be a better test - and I think the gap between chisel and crowbar would grow even more. Chisel is effectively doing ssh tunnelling, with extra layers. Performance is lost in packet wrapping/unwrapping, reduced MTU but it shouldn’t result in more round trips
Sent you an email. Could you provide context what that email is associated with? It's unclear whether this is for the athletic program, the evolution and ecology group, a recruiter, or a rogue undergrad.
My understanding is that the "disabled" radio option just means the Gnome Tweaks program won't override anything. Caps Lock behavior will be the system default, instead of being changed by Gnome Tweaks. The other one is "Gnome Tweaks will override Caps Lock to disable it"
The variance in the 10^i number generation graphs stands out to me. Is number generation really so periodic in performance? I've seen bumpy graphs from O(log2) algorithms recursing additional times near each power of two, for example.
For the last two graphs, is the x-axis "each run"? Maybe there's a better chart for this than a line chart, as you're really trying to show distributions, not the correlation between run # and time. (if the experiments are independent you could rearrange the order of the runs and the meaning shouldn't change)
Sounds like hiding IP is going to be opt-in? I'm not sure what the implications are of TURN but what would be the downside of making IP-hiding the default?
it would increase latency badly (the turn server for the call.element.io instance is in the UK, so all traffic would bounce through it, often unnecessarily), and it would cost us loads on bandwidth as a result. It also means that the turn server sees all the IPs and metadata of who is calling who, which may not be an improvement if you trust your caller more than your server admins!
For instance, two users on the same LAN calling each other would end up bounced via the UK, which is a bit unfortunate if they are in Australia.
The solution is really to switch to using SFUs everywhere, which then solves both firewall traversal, scalability and privacy (assuming you’re happy for your SFU to know your IP - but if you’re happy for your TURN to know it, then it’s probably fine).
