https://itsfoss.com/news/asahi-linux-drops-mit-for-gpl/

Astro Loop, roguelike shooter

https://f-droid.org/packages/com.astroloop.game

Surprisingly addictive

Is it possible to degoogle an android tv stick so that it’s as private as an apple tv?

https://keepass.info/help/v2/sync.html

https://github.com/Kunzisoft/KeePassDX/wiki/File-Manager-and-Sync#data-synchronization

I cannot find confirmation for keepassxc but they check for changes before saving (and I believe offer to merge) as confirmed in this non-issue:

https://github.com/keepassxreboot/keepassxc/issues/12690#issuecomment-3538942799

You could still get conflict files being created by the sync software and would need to watch and merge those manually. However you can mitigate that by saving on every change (this is the default I think) and synching as often as possible between devices.

Keepass (some clients anyway) helpfully merges changes to the underlying file if it changes whilst open so a simple sync of the file is enough.

They are tracking the work here and welcome subscribers:

https://github.com/GraphiteEditor/Graphite/issues/2535

For voyager it is an open issue

https://github.com/aeharding/voyager/discussions/465

Didn’t know this:

Shallow clones are awful. Run your own damn mirror if you’re going to do something nasty like that.

Shallow is the default/recommended in a lot of places though apparently:

Shallow wins the clone, every time, by 4-6x. Which is exactly why actions/checkout defaults to depth=1, why GitLab CI ships GIT_DEPTH=20, and why Vercel hard-codes --depth=2 with no way to change it.

https://bex.co/blog/2026/08/08/git-push-paas-shallow-vs-partial-clone-build-checkout

Separately, one source of the scraping:

welcome to the wonderful world of “proxy SDK monetization.” It’s big business, and your TV is probably doing it.

The link in the article is useful, https://spur.us/blog/smart-tv-apps-residential-proxy-sdks

Amazon makes it explicit: its Device and System Abuse Policy prohibits apps that facilitate proxy services for third parties. Roku has reportedly shut the door too: Lowpass, syndicated at The Verge, reported that Roku bars developers from using Bright SDK and similar proxy services, and that Roku apps using the SDK disappeared after the company was contacted.

LG and Samsung have not drawn an equivalent public line. That is the gap these apps are living in. The same business model that Amazon bans and Roku reportedly blocks is still showing up at scale on webOS and Tizen.

It concludes:

A TV app should not be able to quietly turn a living-room device into residential proxy infrastructure. Screensavers, games, clocks, and novelty apps can be boring, cheap, or ad-supported. If an app is going to monetize a household’s internet connection, the user should be clearly informed about what that means, how the connection will be used, and what risks and tradeoffs they are accepting.

We need to help everyone in the world block their TVs from doing this, this is such an abuse of trust.

Done this for my partner - usb goes in to boot to Linux, take it out to boot back to pre-existing Windows, really simple. Fedora will install to usb no problem. Windows can’t screw up this way either, bit safer then using same drive. Speed has not been a problem.