System admin working for esports websites. Also into software development, live streaming, reverse engineering and other fun stuff. See https://r1ch.net/ for more.
[ my public key: https://keybase.io/r1ch; my proof: https://keybase.io/r1ch/sigs/pcrLB7IUV_tZ-u-B7hUSOD-5ke3L2JSthNhI1izUmI4 ]
Ideally try to design your loops so you're accessing memory sequentially (better cache locality) and predictably (i.e. don't branch on a condition that changes in every iteration). Using a branchless algorithm is only really beneficial if the branch is constantly being mispredicted.
As always, profile first so you don't fall into the premature optimization hole.
It is indeed an old problem (small fixed size buffers) but it hasn't really been fixed, they only increased the buffer size. You'll only run into this on high bandwidth, high latency connections, e.g. between NYC and AMS - you'll be limited to about 300mbps with stock OpenSSH.
Wouldn't the developers of privacy-focused blockchains like Zcash and Monero also be liable under this logic? Surely they also knew that criminals would use anonymous transactions and they did nothing to implement KYC / AML.
For me one of the key features is the integrated TLS server, so my backups can be transferred over the internet at decent speeds. Tools based on SSH all suffer from the SSH window limit and will never reach high speeds over the internet.
Description provided is insufficient to understand the functionality of the item.
I filled in all the new mandatory fields and had chatgpt rewrite the description about 10 times in increasingly simple language but it was rejected every time with the same reason. Since it only had like 20 installs I gave up trying to get it republished.
The title is a bit misleading. In Quake-speak, the "game" is the what defines the game rules, hence what enables modding. This source release does not include the actual game engine, only the gameplay logic, which has traditionally always been released.
I used to have an extension that promised to never be sold or even updated beyond the initial release, since it was a one-liner that can't possibly ever need to change. The Chrome Web Store took it down after 5+ years, presumably because I never published an update so the the now-mandatory fields were empty.
QUIC unfortunately defaults to 1370 bytes to avoid having to deal with PMTUD :(. Endpoints are free to negotiate higher and the protocol does provide a way to generate arbitrary sized ping frames, but it's likely most implementations will just stick with the default.
I wonder if we're at a point yet where gzip's slowness is becoming a bottleneck. I wish zstd support in the browser was prioritized a bit higher, brotli does have similar/ better compression due to the dictionary but speed is also important.
Unfortunately you can't really rely on PMTU discovery these days. Not only is it regularly filtered, it slows every connection down since you add a RTT for the ICMP packets for every TCP host you talk to. In this case I would say the VPN client would be at fault for not adjusting the TCP MSS.
I've been stripping off the cross signed certificate on my desktop-targeted sites shortly after it was introduced. I found it caused compatibility issues when there were none before as some certificate validators were tripping up on the expired root certificate. I was unfortunately never able find out the root cause as the affected users weren't very technical.
My Aranet4 has been great, the original batteries lasted well over a year with even with Bluetooth transmissions enabled, which can be read by any BLE application (I use Home Assistant). You only "need" the app for firmware updates, speaking of which, the most recent firmware update seems to have thrown my calibration out of whack as outdoor air now reads 600ppm. Hopefully they fix it soon.
We used SMW at Liquipedia, an esports wiki. The idea was that all the data about players and teams could be exposed through SMW. Unfortunately we're now in the process of transitioning away from it due to major performance issues and data inconsistencies. It might be ok on smaller wikis but for us it's become a source of a lot of problems.
Unfortunately SFTP isn't a good replacement when speed is a concern, anything running over OpenSSH will have its bandwidth limited by the fixed window size. I long for the day when HPN-SSH replaces OpenSSH everywhere.
Most freezing situations are blocking the UI thread, which should already be handled by the "Not Responding" dialog. I can't think of many cases where you'd want to terminate an application that isn't frozen instead of exiting it normally.
Providing an option to the average user that will immediately kill an application and lose all unsaved data seems like a terrible idea. Are apps so prone to freezing that they require terminating on a daily basis? I can't even remember the last time I had to End Task a desktop application.
Optane was also a contender for the biggest fundamental shift - byte addressable persistent memory with insane endurance is simply in a different class to every other SSD technology out there. No need for a FTL. No need for a DRAM / SLC cache. Unfortunately no software really took advantage of it, OSes still provisioned it as 512/4096 byte sectors, etc. so in standard benchmarks it never really looked that compelling over a regular NVME drive. But if the access patterns align, nothing can come close. Truly a technology ahead of its time.
It's crazy to me that some carriers still charge extra for 5G when this was the real goal. They're actively incentivizing me to stay on 4G and increase congestion.
OpenSSH does enable TCP keepalives by default so that it can detect and close dead connections, but the keepalive interval is far too high to work around bad NATs.
Kind of related to the OP, I spent a decent amount of time trying to have my SSH sessions survive a sleep on Windows. With keepalive disabled, proper Wi-Fi adapter sleep behavior and long enough DHCP leases, I was able to put my PC to sleep and come back the next day and still have my sessions active on resume. Unfortunately it wasn't too practical to disable keepalive as sessions that really do crash never get cleaned up.
Try connecting to an SSH server for more than a few hours without passing traffic and then have the server be the one to send a message. Oops! Your ISP tore down the NAT association and you have no idea the server isn't sending anything until you try to communicate with the server and get a timeout / RST.
NAT breaks TCP, but at least with consumer NAT you're in control of the timeouts on your router. With CGNAT you're at the mercy of an ISP that likely optimizes for HTTP and has low timeouts that you can't control.