(Damn, that's the kind of stuff we entertained ourselves as freshmen on a PDP-11 with a few terminals in 1991.)
I built this about 8 years ago on a whim, and it blew up. Only recently did I learn there was a memory leak, after getting a big traffic spike that caused an OOM.
Over the years it’s burned through several TB of bandwidth per month.
I built ascii.live to support different animations for fun, although I don’t have as much time to review PRs as I’d like.
I hope you're hosting it on Hetzner (or somewhere else with a generous traffic plan). They give you 20TB traffic per month.
I've seen people pushing e.g. weather data to GitHub in regular intervals blowing up their commit numbers.
Just check this to find crazy numbers: https://committers.top/
A lone developer can get away with infrequent commits at no practical cost. Maybe something happened in 2023 that made them a more prolific committer.
These charts are less useful than they have ever been for determining how much code a person writes, but they are probably a good metric overall to measure the productivity gains going on in the industry overall.
I burn out if I don't take weekends off, its nasty.
Is this just some weird default logging in curl?
If you go to parrot.live from your browser it automatically redirects to the GitHub page for the project; The code for which is on line 103: https://github.com/hugomd/parrot.live/blob/master/index.js#L...
You'll notice though that if you change the user agent from your browser to include the string 'curl' you can reach the site from within the browser as the redirect logic encapsulating line 103 doesn't fire.
You can do that by:
* Opening Chrome,
* Opening Chrome Dev Tools within Chrome,
* Going to the Network Tab within Chrome Dev Tools,
* Clicking on "More Network Conditions" within the Network Tab,
* Go the the "User Agent" section and type 'curl' whithout the parens,
* Navigate to parrot.live with the network tab open and you should see the ascii animation in your browser.
$ curl parrot.live
<html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx/1.14.0 (Ubuntu)</center>
</body>
</html>Out of curiosity, my rudimentary measurement puts bandwidth usage at about 17 KiB/s. Some might say that's negligible nowadays, which is not that unreasonable (1 hour ~ 61 MiB). Still, my efficiency brain is tingling. I guess simply displaying chars is lower risk than running code on your computer.
jasonthorsness•8mo ago
> curl parrot.live
Otherwise parrot.live redirects (which HN followed otherwise link here would be parrot.live).
maxmcd•8mo ago