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.
Ooh, I had a coworker who had one with zoidberg dancing once, though it seems to be dead now so maybe he didn't renew the domain. He probably used ascii.live!
Spending a little bit of my free moments throughout the day interacting with coding agents on my phone, it's almost impossible to not have solid dark green for every day.
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.
With ChatGPT Codex connected to GitHub it's pretty neat. From my phone I throw some tasks at it and go about my day and then check in with it later. After giving it some time, I come back and look at what it's done and kick off some more or look at diffs and create PRs right from my phone. It's fairly limited in what can be done from the phone so you'll need to have a laptop for anything more involved than eg spelling errors, but it's a very interesting view of the future.
Reminds me that I made a rainbow unicorn that jumped across your screen as a cmdline utility to be run after all tests passed. Coworkers got a good laugh if nothing else. Fun times.
Fun little parrot! And beats installing with snap (I don't like snap).
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.
Curl just downloads the http response and prints it to the terminal. The sever streams the response and yields a frame of the video every 70ms or so. It sends control characters in the response to clear the terminal and change the color.
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.
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.