For example filesystems like btrfs can be very sensitive to errors in ram due to all the checksumming. On the positive side you’ll know about it fast!

More than one it seems:

https://forum.typst.app/t/tinymist-vs-typst-vim-vs-typst-preview-nvim/1775/7

For restic:

Every backup is incremental after the first or rather restic makes no distinction because it chunks and dedups the data on the way in so if it’s already in the repo it doesn’t get stored twice.

Restic has customisable ‘forget’ cmd that can do whatever you want

Restic has filtering flags, you can use a gitignore style file also. Many people use a wrapper though like autorestic.

The ghost files are interesting. Restic has nothing special for this. A script that mirrored those files and wrote them all as 0 bytes which restic could then backup would be possible, this would work same for any backup tool.

You get that summary after every restic backup. You can also compare snapshots and mount them all to run your own analysis if you want.

Again if you mount a restic backup you have access to every file and snapshot taken in the repo. You could compare or diff them using usual tools.

There is a ‘exclude-if-present’ option where you can say if a file with the name of your choosing is present do not backup that dir etc

Hello

Somebody developed a Home Assistant integration for monitoring and managing sourdough starters

I think he would agree with you that many don’t have good choices

He said the food available on high streets in places like Wigan or Blackpool was “completely different” to equivalent towns in France and it was not the fault of people living there when presented with “wall to wall” junk food.

The danger being raised with the licensing is that you can’t license something if you’re not considered to be the author. There are growing examples of courts and lawmakers determining AI output to be public domain:

The US Supreme Court recently refused to reconsider Thaler v. Perlmutter, in which the plaintiff sought to overturn a lower court decision that he could not copyright an AI-generated image. This is an area of ongoing concern among the defenders of copyleft because many open source projects incorporate some level of AI assistance. It’s unclear how much AI involvement in coding would dilute the human contribution to the extent that a court would disallow a copyright claim.

https://www.theregister.com/2026/03/06/ai_kills_software_licensing/

This is an evolving, global situation and hard to know what to do right now. I think what you’ve got is fine though - you’ve made it clear your intention is to license with AGPL. It’s just that depending on the jurisdiction it might be public domain instead.

This is another reason to be clear about the use of AI in the README so your users can make an informed decision.

If curious:

• Tap quickly twice anywhere on the map, but don’t lift up a finger after the 2nd tap.

• Move your finger up or down to zoom out or zoom in.

The config file has some settings that might help

https://github.com/0ad/0ad/blob/master/binaries/data/config/default.cfg

Such as

scale = 1.0 ; GUI scaling factor, for improved compatibility with 4K displays

And maybe

; Enable Hi-DPI where supported, currently working only for testing. hidpi = false

Finally

; Force a particular resolution. (If these are 0, the default is ; to keep the current desktop resolution in fullscreen mode or to ; use 1024x768 in windowed mode.) xres = 0 yres = 0