Tootfinder

Updated the Flipper Zero yesterday. Was about time #FlipperZero

@…
Quoting Colin Percival (FreeBSD Primary Release Engineering Team Lead):
"… I'd love to talk to them about providing them with images as part of the release process rather than them only getting images a random time after the release when someone remembers they exist."
@…

Chinese startup Moonshot updates its Kimi model, saying K2.5 can process text, images, and videos simultaneously and beats its open-source peers in some tests (Bloomberg)
https://www.bloomberg.com/news/articles/2026-01-27/chi…

Upgrading Funkwhale from 1.4.0 to 2.0.0-rc5 on Debian: https://blog.rmendes.net/2025/12/29/upgrading-funkwhale-from-to-rc.html

I'm building webkit-gtk right now. It's one of these messy packages where a few source files need a lot of memory to compile, and ninja can randomly order jobs so that all of them suddenly start compiling simultaneously. So to keep things going smoothly without OOM-ing, I've been dynamically adjusting the available job count via steve the #jobserver.
While doing that, I've noticed that ninja isn't taking new jobs immediately after I increased the job count. So I've started debugging steve, and couldn't find out anything wrong with it. Finally, I've looked into ninja and realized how lazy their code is.
So, there are two main approaches to acquiring job tokens. Either you do blocking reads, and therefore wait for a token to become available, or you use polling to get noticed when it becomes available. Ninja instead does non-blocking reads, and if there are no more tokens available… it waits till one of its own jobs finish.
This roughly means that as other processes release tokens, ninja won't take them until one of its own jobs finish. And if ninja didn't manage to acquire any job tokens to begin with, it is just running a single process via implicit slot, and that process finishing provides it with the only chance to acquire additional tokens. So realistically speaking, as long as there are other build jobs running in parallel, ninja is going to need to be incredibly lucky to ever get a job token, since all other processes will grab the available tokens immediately.
This isn't something that steve can fix.
#Gentoo #NinjaBuild

There are a lot of takeaways from this:
1. Organizing locally gives you a massive advantage because you will always know your local area better than ICE ever can.
2. Be agile. You can always change tactics faster than a centralized organization.
3. Organize now. The sooner you build your networks, the sooner you can learn.
4. Identify ICE facilities and organize monitoring them directly.
But I think the most interesting one that's not explicitly in there, one that's hinted at the last one, is to go on the offensive. ICE is already afraid. If we all take the anger we have at the murder of #ReneGood, find the local ICE facility that they'll stage from, and bring that anger to #OccupyICE we might be able to just shut the whole thing down preemptively. Completely stop all ICE operations across the US. If they want to fight, they can fight *with everyone, all at once.*
Shut down their ability to operate at all. They have a logistics pipeline. They need cars, they need oil in those cars, they need to be able to move those cars to target areas. They also need money to pay those agents. All of those can be disrupted.
The regime needs your money and labor to maintain the illusion of legitimacy. They chose a bad time because you can hit both of those at once *right now* with a combination of #GeneralStrike and #TaxStrike, and then #BoycottEverything.
The regime is weaker than it's ever been. It's flailing. Their own base is demanding the release of the #EpsteinFiles. Their last gasp attempt to prevent the radical change that's coming is just to ethnically cleanse the US back to the 50's (which is what they always meant by "Make America Great Again"). Trump will do anything to stay in power, even if it means killing everyone on Earth in the process. But Americans can end it now by going on the offensive.
Now is the time.
#USPol