Unable to parse Unattended-Upgrade::Allowed-Origins.
An error occurred: not enough values to unpack (expected 2, got 1)
// Automatically upgrade packages from these (origin:archive) pairs
//
// Note that in Ubuntu security updates may pull in new dependencies
// from non-security sources (e.g. chromium). By allowing the release
// pocket these get automatically pulled in.
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
"${distro_id}ESMApps:${distro_codename}-apps-security";
"${distro_id}ESM:${distro_codename}-infra-security";
"${distro_id}:${distro_codename}-updates";
// "${distro_id}:${distro_codename}-proposed";
// "${distro_id}:${distro_codename}-backports";
"origin=cloudsmith/caddy/stable";
};
Update the stable client does have proper virtual file sync.
Regarding the previous virtual file sync system (.nextcloud) you had to enable experimental features to get it. The latest stable just has both versions of syncing and I missed the obsious vfs sync option.
The only downside to the new system is there isn't a make file/folder available offline always option in the context menu (you can get around this by manually setting up synced folders but it is a little inconvient).
It sorta does. Nextcloud creates a list of placeholder files with a .nextcloud extension and when you open it nextcloud will auto download the realfile and open it.
remote UI connection passes through the Home Assistant Central servers, the Central servers could maintain that safety database and off switch
I think this is how home assistant handles it. When they put out a cve they can update the insecure version list which makes nabucasa refuse remote forwarding (until you update).
Initially I was just thinking if a open-source project is on github and uses the security disclosure feature if it would be possible to pull data from it and disable remote acess (either by auto shutting down the service or simply disabling routing on a reverse proxy).
Having a system that does without a security disclosure list from a project maintainer would be far mor difficult like having the proxy disable one of your services if it detects a vulnerability in a dependency.
Beeper did mention the DMCA protection on reverse engineering.
That being said regardles if beeper wins or looses. If apple sues and at the same time breaks beeper mini they could run into financial trouble very quickly.
If your willing to deal with self hosting, immich is a great alternative. Its facial recognition and search is practically on par with google photos.
The only downside is it doesnt' have photo editing, and its under active developmeant (it gets weekly updates and you occasionally need to modify docker config though they do give a warning in ui).
Yep this works