"Gone Like A Memory" 2026, Action Suspense Film
Xenia the fox and her rag-tag crew of cyberdeck-toting, open-source champions may not be the most friendly crew, but in this feature length film you'll cheer for their success as the plot the heist of the decade:
Infiltrating AI data centers to strip the servers for parts and leave the infrastructure destroyed, then distributing the hardware to people in need.
Rated four and a half stars by furries and independent PC hobbyist (And five stars by those who are both).
The feature of morging bugfixes from rel continvoucly into develop as Tim moves backward has been removed, but the Wayback Machine captured the Microslop: https://web.archive.org/web/20260216165612/https://learn.microsoft.com/en-us/training/modules/introduction-to-github/3-components-of-github-flow
This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"
RE: https://computerfairi.es/@JuiceThatToots/116025835152995977
No! Bad! Get up and stretch, juice!
@Loosf So based on the screenshots I have this is actually from a different but similar post, but I think this is the one you're probably thinking of?
PSA: Did you know that it’s **unsafe** to put code diffs into your commit messages?
Like https://github.com/i3/i3/pull/6564 for example
Such diffs will be applied by patch(1) (also git-am(1)) as part of the code change!
This is how a sleep(1) made it into i3 4.25-2 in Debian unstable.
#indiedev is waking up one morning with a silly idea and then not resting until you make it real! 🤪 #indiegame #godot
✨ Kind 'Net Help Desk fairy by day. ✨
✨ Weird & furry Unix fairy by night. ✨
✨ Sometimes a retrocomputer fairy. ✨
✨ Pays the ComputerFairi.es bills. ✨
✨ Sparkly✨shellscript✨princess. ✨
✨ Age: Mere days younger than ✨
✨ the Intel 4004 & Unix 1st Edition. ✨
✨ Follow requests welcome. ✨
✨
✨