Once I was using Blizzard's downloader to install something (StarCraft, Diablo, I don't remember), and it was kinda slow. I disabled P2P downloads and speed skyrocketed, and I said "Huh, this was unexpected".
When P2P downloads disabled you could see the list of CDNs you're downloading from and mine had a single IP on that list. It looked familiar. Then it dawned on to me. It was the Akamai server which we were hosting in our system room, at 15 minutes of driving distance. After a chuckle, I went to get a cup of tea, because that was entertaining than the game itself.
Then of course, I dived into whatever I was installing that night.
Edit: From the screenshots in the wiki, I remembered that the progress bar was red. It was possibly Diablo 3, then. However, I'm still not 100% sure about it.
So how come was using your own ip? Become a Diablo node installer so you downloaded from there, like how can they convert your own akamai instance into anode without you knowing?
It's not my own IP, but our IP block. As an institution we have a couple of big networking related hats, so we have a couple of B blocks (/16 networks) for ourselves. The IP was from one of these blocks.
However, these network operations (and CDN related stuff) are not managed by us, but by a couple of high profile guys next door. I knew we had an Akamai node, because the machines were shipped recently and we had a chat about it.
Funnily, some of the performance optimizations on Akamai's disk access algorithms (SSDs were not dime a dozen back then, so people were still optimizing for spinning drives) was apparently developed by a friend of mine, but I don't know any details about that.
Same here. Inspired by both, I used to delivery videos over torrent to in door machines since at that time, there's no CDNs (or it was difficult to get one).
I've seen this used for distributing container images in networks with awkward network topologies (e.g. a lot of bandwidth within a site or sub-site but limited bandwidth to central registries)
Several companies tried this for distributing software.
It was very controversial. Users were angry that software companies were using their internet bandwidth to distribute their software. Made a lot of people angry.
As someone who was annoyed by it at the time, I don't think it's a good example of that.
This was in an era of much more limited upstream bandwidth. The p2p nature was obscured from non-technical users in some implementations. So on and so on. I'm sure there are plenty of writeups from that era detailing why it was a bad idea.
These companies already used capable CDNs to distribute patches. It was a way for them to shift their CDN bill onto their paying customers.
When you have barely the upstream bandwidth to send the ACK stream of your downloads, anything sending something becomes a big burden on your system.
Not everyone has the luxury of fully symmetric internet connections even in this age. Yes, my uplink speeds are absurd when compared to a decade ago, but when I ratio it to my downlink, it's still slow.
I have no comment on residential proxies. Somebody doing something in my name is unacceptable to put it very mildly.
>
AI writes unmaintainable code - you can see that many projects don't accept it.
There also exist other good reasons why projects don't want AI-generated code, in particular
- because of unclarity of copyright status and consequences of AI-generated code
- because the project leader simply made the observation than many programmers who hand in AI-generated code care more about "getting things done" and "pushing through their changes" (possibly to boost their CV) instead of deeply caring about code quality
reply