It's actually difficult to find software that supports it, assuming you're not using Copilot. Ollama on my NPU enabled laptop doesn't even try to use it, and even if it did, performance might suffer anyway.

It does - this is how Android's media scanner works.

This is Android's media scanner in action.

Fortunately, you can add a .nomedia file at the root of your Obsidian files to prevent them from showing up in your galleries.

If it's peace of mind that you're after, you can never go wrong with a backup.

It is not nearly a replacement for me.

This was when I stopped using it for a while. I sent multiple feedback messages as it really irritated me.

It's a W3C managed standard, but there are tons of behavior not spelled out in the specification that platforms can choose to impose.

The standard doesn't impose a 500 character limit, but there's nothing that says there can't be a limit.

I think this is part of a larger trend of Microsoft refusing to patch any bug they simply don't want to.

I've had an issue with the Remote Desktop app on Android for three years where the cursor drifts further and further away from where it's drawn over the course of a session and when the Android keyboard pops up. Several users have reported the issue (including myself), and Microsoft still hasn't fixed it.

Once again, this has been a major usability bug for over three years. The only way around it is to disconnect from the session and reconnect every time you use the keyboard or once the drifting becomes too much.

PNG support lossless compression through deflation, but there are encoders that can apply a lossy filter to the image to make the compression more effective.

PNG doesn't support lossy compression natively, to be clear.

Sounds like a job for Ansible. ;-)

Just so you're aware why people are disagreeing with you - an installed browser does not change the behavior of HTTP calls made in other applications.

It's not bash itself that was the complex part exactly, but I have a CI/CD pipeline that generates epub files from markdown. In some cases I have custom designed covers, but where a cover doesn't exist I have a bash script generate one using Imagemagick.

I wanted to generate the cover in one command to lessen performance impacts and disk I/O, but it took me a few weeks to figure out how to do it all in a single Imagemagick command:

convert \
    -size 960x1536 \
    -background "${backgroundColor}" \
    -fill "${textColor}" \
    -font "Liberation-Serif" \
    -pointsize 96 \
    -gravity north \
    caption:"${title}" \
    -bordercolor "rgb(0, 0, 0)" \
    -border 2 \
    -bordercolor "${borderColor}" \
    -border 40 \
    -background none \
    -fill "${textColor}" \
    -font "Liberation-Serif" \
    -pointsize 48 \
    -gravity south \
    -geometry +0-800 \
    -annotate +0+40 "${author}" \
    "${destination}cover.jpg"

Eventually it made an abstract sense to me, and I was able to bring it down to two commands and then finally one. This generates a cover with a selected background color (based on content type) and contains title text that will wrap to an inner border.

I think I had to give up on the author being wrapped, but it's much smaller than the title anyway.