tasankovasara

Whatever you end up using, have JACK sync 'em up. I used to have two Macs, one for recording with Nuendo and one for doing MIDI sequencing and programming. They synced via MIDI sync and there was always issues. Now I have everything on one Linux machine (Ardour records and mixes, Reaper sequences MIDI and Renoise does beats and other sampling related stuff) and with JACK the sync is seamless <3

Are you starting the server and laptop Syncthings as systemd user units? You'll see stuff asking for 'systemctl status syncthing@yourusername' if you are. That way it works (and has worked for years now) for me. I've kept the config really simple because I only have it syncing at home, so no encryption or discovery. If you also only have it working on a trusted network, maybe ditch the complications...?

The Android side is tough because of all the restrictions. I'd imagine that's what is troubling your phone Syncthing.

It's hopeless, you're quackered.

I'm thinking Waydroid or something alike with Gapps installed with a burner G account. That can be spun up when parking app or work benefits app are needed, as these are the only two normie apps in my life that require the googly bits. Same drill as I do with GrapheneOS now - second user profile with Google enabled that only runs a minute if i need to pay for parking or a meal :)

Ok, interested. Looks like a project to support with real money. I'm in.

If the price of their product feels steep, it's not that bad actually. I paid over 600 € to f@ckin' Google for a device to run GrapheneOS on :o)

Yes, or SSH keys or any other means of user authentication. The cool thing in this technique is that it's twofold and you (as an attacker) can cherry-pick the info given. If you walk up locally to someone's running system, you could skip the first half and go with the 'hey, can you resize this XFS image for me' bit.

The technique described here is only a concern if the 'bad actor' has access to a user account on your machine in the first place.

The dev's VSCode application installs a helper package in /root/.vscode-server. Separate copy for every user that connects. It runs a bunch of 'node' processes that often stack up more used CPU time than MySQL. I'm not a fan...

Thanks, that'll come in handy!

I guess it's worth mentioning that once (only once) I've seen ripgrep bring a whole LAMP stack production server to a full tilt. A dev using VSCode (which has rg as part of its 'trojan horse' vscode-server it installs and runs as root on any server it's used to edit) did a search and ripgrep went into some kind of death loop hogging 100% of all cpu cores. Probably rare, but kind of shocked me. All our servers now babysit vscode-server with cgroups...

The sharp uptick of crap flown around 2.6 piques my interest. As does someone's introduction of 'retard' into the vocabulary shortly prior. Must have been popcorn times.

Just wanted to fly a less popular flag in this conversation. When I was choosing my first bike, my first crush was the Honda Silver Wing, a maxi scooter. Loved the looks and the practicality, loads of storage even without panniers and such...

But I didn't follow my heart and got a dual sport, which was great fun for 24000 km. However, I missed the practicality. One djembe drum was ruined as it wiggled loose from straps and took burns off the exhaust.

A couple of years ago I got a 250 Vespa as my second bike. Already much more practical. I also prefer the longer service intervals compared to cogs and chains. As much a I enjoy that thing, first crush is still in the back of my head...

What am I rambling about? Don't disregard scooters, they're great too :D

The only caveat here is the fire-hazard non-removable lithium batteries.