Just do it. Be sure you don’t have any other immediate responsibilities though. It’s a time sink for sure.

New Features:

• All new UI to make using Warehouse’s features easier
• UI now better adapts to larger window sizes
• UI now better adapts to smaller window sizes
• Improved UI for installing packages from remotes
• Snapshots can be given names
• Packages can be reinstalled with a few clicks
• User Data can now be sorted in multiple ways
• Active User Data can be browsed just as easily as leftover User Data
• Custom installation locations are now supported
• Leftover Snapshots are now shown
• Apps can be reinstalled from leftover Snapshots
• Installation location of disabled remotes is now shown

Changes:

• Packages list filter options are now easier to understand, and more predictable with how they are applied
• Improved keyboard shortcuts for quick navigation
• The Downgrades (renamed to Change Version) interface now shows the currently installed version
• Long running processes now have progress bars and can be canceled
• Better status icons for End of Life, Masked, and Pinned packages
• Warehouse no longer disables closing its window when long running processes are happening
• Refreshing now shows a loading animation

Bug Fixes and Performance Improvements:

• Warehouse is now faster to open
• Getting system information is now faster
• Long running processes no longer freeze the app
• Refreshing is no longer possible when long running processes are happening

Are you loosing the mounts after a reboot? As in, are you mounting via /etc/fstab?

Are you running these llms in containers completely cut off from the internet? My understanding was that the “local first” llms aren’t truly offline and only try and answer base queries offline before contacting their provider for support. This invalidating the privacy argument.

Oh man, this so much. Still debating on tearing everything down.

Just about to relocate my base. Glad I haven’t built an extensive rail network yet

Hey, I’m just starting out. Don’t worry, they’ll go up

Do you by any chance faces a guide on how to get that running?

Do you need to reboot after every update or updates applied live? Only have experience with rpm-ostree on kinoite

AIO is the way

Or use caddy with a dns challenge. No need to open any ports and just use it completely locally without any annoying warning.

Wait until you try out bazzite for gaming or just the regular kinoite ublue images. Both are basically kinoite with more tweaks and added software on top.

You need to set a trigger for tubearchivist-jf to run after you’ve downloaded a video.

To 2.: I only had that issue appear when launching Firefox or Vivaldi. Might have been a custom widget. Wiped my install and now the issue is gone? Sadly wasn’t able to diagnose the issue any further

The docker compose ist almost copy paste. Not quite sure what the difficulty is?

I’ve had major problems for days like half a year ago. Switched to dynv6.net with no issues so far.

Caddy combined with dns challenges are the dream!

Ctop for container monitoring

Sound great and I went the same way for a while. Just be aware that steam on Linux can have issues with ntfs partitions. So I also went the the two drive route, much less of a headache.

Aren’t you going to tell us what the five games could be instead of just dropping some link?