I use chezmoi and chezmoi_modify_manager to keep my dotfiles (including some KDE configs) in a Git repo, and it works well enough.
I like Pushover too. I've been using it for over 10 years now.
Maybe they've cast Jack Black as Ganondorf lol
Chrome's had it for five years, and I don't recall any Webserial-specific vulnerabilities in it (but I could be wrong!)
you need at least two NICs to properly setup a firewall.
I'm not sure I'd recommend it, but two (or more) VLANs on a single NIC would work fine too. This setup is usually referred to as "router on a stick"
I'm not sure about other OSes or Linux distros, but it's easy to add multiple VLANs on Debian. You load the 8021q kernel module, then add interfaces suffixed with the VLAN ID (e.g. if your NIC is ens3, you'd add ens3.10 to /etc/network/interfaces for VLAN 10). You'd also need to make sure the switch port is configured to allow VLAN10.
Older NICs lead to regular crashes and/or slow network speeds.
but the ones you're suggesting (I350-T2 and -T4) are 12 years old.
I have some colleagues from Singapore, and from what I've heard, they have to do something similar there.
The weird thing to me in the US is that they're making the enrollment for Selective Service automatic, but they can't make enrollment for voting automatic. 🤔
not dependent on the server
It doesn't have to be - a developer could also provide a HTML file that the user can download and open locally.
And to be honest, if someone had to build a user-friendly cross-platform GUI app for connecting to some sort of serial device, they'd probably just end up using web technologies (Electron or Tauri) anyways. May as well avoid the extra overhead of Electron.
You can completely disable the API in Chrome... I assume Firefox will allow this too.
IMO it's fine since you need to explicitly grant permission for the site to use it, and also explicitly choose a device to allow it to communicate with. You can also configure your browser to always reject requests to use the API, if you never want to use it.
WebSerial is useful for the developer as they can build their webapp once and it'll work consistently across platforms, and it's useful for the user since the same interface will work across all OSes.
I prefer it over the other common approach for communicating with serial devices, which is often to only make a Windows app and to have some convoluted setup process involving sketchy-looking drivers, which then breaks when you have different devices that require different versions of the flashing software or drivers.
Why install a native app when a website can do it? It's very common to use a website to flash ESPHome for example.
My guess is that they'd have a pool of accounts, and cache the most popular songs rather than streaming them from Tidal every time.
view more: next ›
Do you have any actual problems with systemd, or do you just want SysV init scripts to stick around forever?
Maybe systemd isn't the best, but it's way better than a bunch of mostly unstructured shell scripts, and more secure (it's pretty easy to reduce privileges, sandbox the filesystem, restrict syscalls, etc per service just by editing the unit file)