antimu0n π€ metal lynx βΏ π³οΈβππ³οΈββ§οΈ
Ren
LuisfWhen the fursoΓ±a is A Fat Fuck
| pronouns | any (for now) |
| age | 41 |
| languages | German, English |
| egg? | bug! |
antimu0n π€ metal lynx βΏ π³οΈβππ³οΈββ§οΈ
- 58 Followers
- 172 Following
- 6.2K Posts
software & hardware - disabled - metalhead - tired lynx - NSFW
Ondii, Praemodian Propagandist (Andi) πͺ½"I offer you a place by my side as my champion, warrior. Accept, and you will help me bring about my new order. Refuse, and you will suffer the same fate as the rest of this dying old world"
β¨nagaciel time! i love being an optional boss who you can pledge to because you too are horny for snakegirls
Brynnbo the FrogMxstressI've still got a whole bunch of progress pride bricks that need a sticky place to live 
Ariadne Conill π°
what I will say is this. there are pieces of software that are frankly "mission critical".
for example, pkgconf, as a key component of most build toolchains, cannot have regressions because those regressions will reverberate throughout the entire "software supply chain" in the form of build errors. it is a mission critical piece of software.
this is why as lead maintainer of pkgconf I have implemented a number of policies and initiatives to reduce the likelihood of software errors and promote correctness in pkgconf as part of the pkgconf 3.0 work.
these initiatives include banning LLM contributions, requiring DCO signoffs on commits, refactoring the codebase to remove entire classes of vulnerability, improving the quality of the windows port so it is equivalent to its unix counterparts and reimplementing and expanding the test suite from scratch.
why? because every single thing I listed reduces the likelihood for regressions.
rsync, like pkgconf, is used at all times of the day, all around the world. I try to visualize the scope to which pkgconf is used and it is just not possible.
rsync is the same way: everyone is using it somehow, either to back up their data, or to mirror data from one machine to another. there are numerous utilities which make use of it somehow to provide functionality.
a regression in rsync is even less tolerable than a pkgconf regression: if you have errors in rsync, they can potentially cause data corruption or loss.
but rsync goes in basically the opposite direction from pkgconf: it embraces LLM contributions. it also has had several regressions since doing so.
οΌ¬οΌ©οΌ¬οΌΉ - οΌοΌοΌοΌin most discord communities you can throw a bat at a hornets nest simply by saying "i dont think screenshots of posts constitute news" in its obligatory politics-channel
π©΅ Bwee the Fluffdragon π©΅Remember your ABCs!!!
~~~
Always Be Cute!
Deeply Embrace Friendship.
Give Hugs Immediately.
Just Keep Loving.
Maintain Neverending Optimism.
Pursue Quirky Recreation.
Show Tender Understanding.
Value Warmth.
Xpress Your Zaniness!
π©΅π©΅π©΅
(It took me literal hours to come up with this, please favorite/boost xD)
dr. fennec 
Kiri πΎπ //nullptr::liveFun #GIF facts learned while writing the GIF loader for #Godot...
- The GIF 89a spec only uses the word "animation" or any other form of it twice, in the part where it says... "Animation - The Graphics Interchange Format is not intended as a platform for animation, even though it can be done in a limited way."
- GIFs can support more than 256 colors. While a GIF palette can only go up to 256 colors, each sub-image can have its own palette which, combined with other sub-images, can result in a final image with more than 256 colors.
- GIFs have a "user input flag" on graphic control extensions for sub-images, meaning that animated GIFs can actually wait for user input before advancing to the next frame. To my knowledge, modern decoders ignore this.
- The GIF 89a spec has a section for text rendering. There is an entire "plain text extension" that remains unimplemented on most modern decoders. So far I can only find one GIF that uses this (along with the user input flag), and one very old decoder for DOS that supports it. This is not related to GIF comment extensions.
- The "loop" count is a nonstandard Netscape 2.0 extension, implemented as an "application extension". GIFs otherwise are not expected to loop.
- The initial GIF version was invented in 1987, but "the web" was invented in 89, meaning the format was likely never intended to be used in web pages.
southie wusky
