krash

The car garages. I never drove a car in Japan, but it looked like there was a system and some kind of futuristic hydraulic automation thingy to put your car in an available slot??

But in general, I got a lot of retrofuturism vibes in Japan.

Also, while not technology, it is worth mentioning that people there are incredibly polite and friendly - even in Tokyo rush hour.

There's so much you could do.

• have a reverse proxy for your services, as containers
• connect then through netbyrd or nebula if you want the FOSS route (or headacalescale)
• set up an IDPS, such as fail2ban, snort, etc
• Set up a backup job, there's many projects that does this well - check out Borg and kopia.
• since we're on linux, try out different shells. Zsh or fish are pretty popular and pretty to look at.

I didn't really see the benefit of this besides having a snapshot or backup of my home folder for my use case (I don't have that many config/text files that needs tracking), but I can recommend chezmoi for those interested.

Matrix, I'd you want something truly open and respects user privacy.

Like you said, "it depends" 😁

I have a huge datablob that I mirror off-site once monthly. I have a few services that provides things for my family, I take a backup of them nightly (and run a "backup-restoration" scenario every six months). For my desktop, none at all - but I have my most critical data synched / documented so they can be restored to a functional state.

I really look forward to spin this up tomorrow. Awesome release as always!

I second obsidian. I was on the verge to jump onto logseq, but found its way of handling notes to be... different. I also felt a dislike of anytype where I don't really have control over my notes. Obsidian clicked with me from the start and felt right. So I went with it, even though it's not FOSS (which is usually a hard requirement from me).

Never heard of falco, why would you recommended it over other similar solutions out there?

But this is by design, snap containers aren't allowed to read data outside of their confinements. Same goes for flatpak and OCI-containers.

I don't use snap myself, but it does have its uses. Bashing it just because it's popular to hate on snap won't yield a healthy discussion on how it could be improved.

Just make sure about what you're getting yourself into: features such as IR facial detection and stylus input isn't supported on all models OOTB by the surface kernel. Also, it is a bit messy with how surface handles booting.

Linux on surface works (I got Ubuntu on both my Go gen 1 and pro 7) but expect to put in time to tinker and manage unexpected issues.

How is C more secure than Rust? Doesn't it lack features such as safe memory handling?

This is a great personal quality you're wielding. Welcome aboard to Linux land!