alt.wesley.crusher.die.die.die would say otherwise.
alt.wesley.crusher.die.die.die would say otherwise.
Borg for local data backups to backup share on nas. Proxmox takes guest snapshots. Rclone all of that to rsync.net. bonus, Borg can use the rcloned remote, if necessary, directly.
Alien isolation stressed me out.
Closed source goals are profit. Open source goals are to solve a problem.
Hack the reader. Install a device that clocks you in and out automatically or remotely. There have been a few defcon talks on how insecure these systems are.
Graylog has been mostly solid here too.
I used to buy used CDs and rip them myself. So I have my own collection. But to discover new music and listen to things I may not wish to own, streaming is the best option.
The solution? A plex server with a music library that points to your own collection. Then get a Tidal subscription through Plex. You then add Tidal music to your own library as if you were downloading or ripping it yourself. Listen with plexamp on a phone connected via bluetooth, or just use plex client on your shield, roku, firestick, etc.
Now you can listen to things both locally and streamed seamlessly. You can do artist radio to discover new music and manage smart playlists on the plex server itself.
If you are hosting your own mail server, a procmail recipe shouldn’t be too difficult. I run mimedefang, so could do it there too, but that’s a whole lot of overkill if you don’t already have that.
I have this installed because my password manager is :X
Plex with a Tidal subscription. Treats tidal as if it is local in your library and seamlessly integrates with your own collection.
Listen with plexamp.
You can’t really do configuration management with a GUI. Or version control. Everything I do I manage with Ansible as much as possible. YAML is self-documenting as well. How much effort is ‘run command with parameter’ documentation vs explaining how to navigate a GUI?
Because marketing dweebs in powerful companies now own the internet.
You can’t drive a helicopter down the freeway. You can’t land one just anywhere.
I don’t like lxc containers, and my build automation works well at the full system level vs containers.
Running your services bare metal these days is insane. If I have a problem, I just restore or rebuild that purpose-built vm from configuration management. This is also a lot more flexible and cost effective vs having separate hardware for each thing.
Redundancy is also easier, should I decide it is worth the hardware investment.
I run proxmox on a System76 Thelio. ZFS mirror, 16 cores, 64GB. Synology NAS for data storage and backup. Dual NICs bonded with ovs for the VMs. The onboard NIC for connecting to proxmox itself. One of the VMs then rclones the backup share to rsync.net
One of the VMs is Plex/Sonarr/Radarr/Transmission. Media is stored via NFS to the NAS.
The new NIST guidance is to have something long. Special characters don’t matter. So a good passphrase that you can remember > short line noise. NIST also recommends against constant password rotation, but to instead audit for dictionary attacks. See also: https://www.netsec.news/summary-of-the-nist-password-recommendations-for-2021/
Yes, it is bad programming. Of course, on the backend you must never store passwords in the clear. You should never grow your own hashing algorithm.
If you have the background and get the right head hunter, you can get sponsored for your TS/SCI. I used to work for a place…
I will tell you, however, that working in a SCIF is not as awesome as it looks on TV.