Wilhelm Codes · Woopshttps://wilhelm.codes/tags/woops/Slinger of nibbles, bits and bytes. Over 25 years of professional experience as a software engineer. Love making glowing rectangles go "beep-boop".Hugoen-US0xdeadbeef@devilmayco.de (Wilhelm Murdoch)0xdeadbeef@devilmayco.de (Wilhelm Murdoch)Fri, 19 Jun 2026 00:00:00 +0000I am not a smart man. I completely forgot I was using the “Pro” …https://wilhelm.codes/bits/blurb-i-am-not-a-smart-man/Fri, 19 Jun 2026 00:00:00 +00000xdeadbeef@devilmayco.de (Wilhelm Murdoch)https://wilhelm.codes/bits/blurb-i-am-not-a-smart-man/woopswilhelm.codesbitblurbtrueI am not a smart man. I completely forgot I was using the “Pro” version of FontAwesome and had the entire library committed to this very public repository without any licensing coverage. I mean, the pro version shouldn’t be shared anyway. You may have noticed the associated Github repository has been temporarily set to private and that all commit history as been wiped. Sucks, but I felt this was much more pragmatic than removing multiple specific files from the tree. I am not an expert git surgeon, so that got a hard pass from me.I am not a smart man. I completely forgot I was using the “Pro” version of FontAwesome and had the entire library committed to this very public repository without any licensing coverage. I mean, the pro version shouldn’t be shared anyway. You may have noticed the associated Github repository has been temporarily set to private and that all commit history as been wiped. Sucks, but I felt this was much more pragmatic than removing multiple specific files from the tree. I am not an expert git surgeon, so that got a hard pass from me.

I’m currently experimenting with some alternative OPEN SOURCE web icons and updating the third-party licensing notice bundled with the repo to cover icons as well as web fonts.

Luckily, only I noticed this issue and immediately worked to address it.

edit: Good-bye, sweet git history!

]]>