Max

Your ISP knows where you’re going anyway. They don’t need DNS for that. They see all the traffic.

The symptoms you describe are exactly what happens to my machine when it runs out of memory and then starts swapping really hard. This is easy to check by seeing if disk io also spikes when it happens, and if memory usage is high

On linux and Mac there’s also https://vorta.borgbase.com/ which is pretty good

Your filter rule association is set to ‘rule’. What is that associated rule, and do things work if you change it to ‘pass’?

https://www.reddit.com/r/opnsense/comments/puty62/correct_option_for_filter_rule_association_when/

Instead of connecting with a web browser, can you try using curl or telnet just to check if you’re getting through at the TCP/IP connection level?

That make sense. I would use tags like that:

• Flickr Published

• year roundup/2022

• type/Landscapes

• type/Portraits

• events/trips/Zion 2022

• content/food

• content/animals

I actually do event level as my on-disk sorting. And then tag for stuff that’s not that. But I think it would work pretty well to do the event sorting under tags as well.

Then I rate my favorite photos, usually using the green approved, not stars. But stars would work too. Then if you want to find say, favorite landscapes, the digikam interface makes it really easy to do so.

I’m not sure if you can select what tags get written into the image, but if you can, you might be able to exclude certain parts of the hierarchy, and only include content/ or type/ subhierarchies

One of the things I really like about digikam is the matching of the disk layout with the album structure. This makes it really easy to have other programs also interact with my photo library in a way that’s near impossible if you instead have an internal photo database.

Tags work great for me for multi-categorization. What feels clunky about them in your workflow? You’re even allowed to have a tag hierarchy.

I think you want something like \s*\(((?!ver\s\d).)*\)\s*

See regexr.com/7jbvk

Basically this consumes all characters between parentheticals with whitespace unless the next character set in the parentheticals is ver followed by a number. Now this uses a negative lookahead which might not be supported by the engine that krename is using. You can also explicitly construct the group to not match, but that’s rather painful, see here