A few days ago, my groovebox, the #SynthstromDeluge, running the new and awesome community-built firmware, crashed, which was very cool.
Not that it crashed, but what happened next: It displayed a colorful pattern on its pads.
That's a stack trace. It's listing the last steps the code made before crashing. The devs are have asked to be sent photos of these, to help them find bugs.
I've pasted it on Discord, and there's a _bot_ that recognizes these images and decodes them into addresses!
I checked because of this meme, proves true yet again.
The list btw: https://repology.org/repositories/statistics/newest
@foone I tried arch back in the day. I was impressed that it managed to be worse than Gentoo.
I think the arch install guide may have been written by that guy who wrote the bomb defusal manual used on M*A*S*H.
"remove the tail assembly, and carefully cut the wires leading to the clockwork fuse at the head"
*next page*
"but first, remove the fuse"
omfg so i went through like an hour-long phone-call with a support person to set up my service; and after all that, I go to log in online for the first time …
… … … and it won't let me login until I "fix" my "broken" name.
THIS IS WHY YOU DON'T APPLY 'VALIDATION' TO PEOPLE'S NAMES, FOLKS
@ELLIOTTCABLE A million years ago in the dial-up BBS days there were certain systems that refused my last name “Farley” Eventually figured out the cause was trolls who would log in as “Chuck U. Farley” Due to sysops sharing block lists this problem followed me around on certain brands of BBS for a while.
Crazy read: detecting positions of players in Counterstrike by *listening to their GPU over a microphone*
Software developer, open-source enthusiast, wannabe software architect. I like learning and comparing different technologies. Also general STEM nerd.