A random person on lemmy. Banner art from Deemo switch version
Alt lemmy @[email protected]
Alt kbin: @[email protected]
FMHY (archive): @[email protected]
Update regarding virtual files has more quirks.
Also turns out the reason it was a github release was it is still in alpha 😅 .
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).
Nextcloud desktop client 3.13.0
Edit 2:
You need to grab the release from https://github.com/nextcloud-releases/desktop/releases/tag/v3.13.0
Specifically the vfs version Nextcloud-3.13.0-macOS-vfs.pkg
brew doesn’t really work
This is how it shows up for me on Nextcloud desktop client 3.13.0
Unfortunatly like syncthing nextcloud mac app also has the same file extension sync issue (they use .nextcloud).
Sorry about that (didn’t think that far when making the post 🫠 ).
I updated the title
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.
data source for these vulnerabilities
Are you refering locations for vulnerability disclosure or are you more referring to bug bounty?
Personally, I’d just put everything behind a VPN. The attack surface is much smaller.
Fair enough
I do own a cheap numerical xyz domain (something like 432433.xyz) cost a dollar per year. Only reason I was curious about eu.org is its very short and ends with .org.
I haven’t really bought a proper .com domain since I’m just using them for side hobby projects (not for sharing with other people).