

Tailscale is a kind of VPN (virtual private network) not a VPS (virtual private server).


Tailscale is a kind of VPN (virtual private network) not a VPS (virtual private server).


Run your own Vaultwarden service. Its FOSS, and works with Bitwarden clients.


Do you mean a VPN? Tailscale has a free tier, or you can run a headscale instance on whatever hardware you like.


All in, that’s $152/year. I’m probably going to add another $132/year if/when I can convince the rest of the family to move away from Gmail.
The VPS is for a few services that I don’t want to go down if my home internet connect goes down. And offsite backups are a must for me.


Like all VPN-like things, some amount of data has to flow through their system. But almost everything is encrypted nowadays so it’s generally not too big of a worry.
For Tailscale though, they see way less. They see your IP during device setup, and maybe during use if things are making it hard for them to enable a direct connection. Depending on your DNS setup, they may see some of your DNS requests.
Its also really easy to setup your own headscale sever and then nothing goes to them at all. I recommend a small VPS for that, rather than running it on your home internet connection.


I haven’t smoked in a long time, but I used to love my pipe. It’s been getting more and more tempting to try it again, since I have one of the few health issues where nicotine can sometimes help.


Does Tailscale count as a VPN for you? It’s how I roll. Well, I run my own headscale server, but the free Tailscale tier is going to be fine for any reasonably sized personal project.
In college, my advisor/boss was basically the emacs guy, so I picked up enough to do some basic text editing but didn’t go further because I didn’t feel like spending hours reading man pages.
Later I worked at a place where a shared computer only had vi, so same story. I learned about a half dozen commands and left it with that.
Then I went though a series of other editors and IDEs at different jobs, Notepad++, StyledEdit, CodeWarrior, CodeComposer, some weird proprietary Netbeans based thing, VS Code, etc. I still used vi for minor config editing on the occasional remote machine.
Then I got a job where I would be doing a ton of work on headless remotes, so I decided to get serious about learning something purely terminal based. I tried a couple of things, but ended up with Helix because:
Now I’m all helix all the time and really enjoying it.
Same. Every machine I have control of I install Helix. For the rest, I remember just enough vi to do what I need and get out.


Oh yeah. I’ve had to do a small amount of it on much simpler systems for work from time to time, and it’s always been damn hard. Often rewarding in a weird way, but very difficult.
I had a problem on my work laptop with them about five years ago, but rolling back fixed it. Never on my personal machines.
Edit: TBF, I’ve never had a personal laptop with an nVidia card. I generally prefer to build my own desktops, though I do have a laptop. It has an AMD GPU, also with no problems.


What do you think Project Support is?


I recently did a big expansion on my home networking infrastructure, and backups were one of bigger triggers.
My setup is based on a local NAS + Hetzner storage box. The NAS runs Immich, Paperless, and the arr stack. Immich and Paperless back up to the storage box via borg, along with the configuration and docker files, but not the media. I either have physical copies of that or don’t really care because I can just download it again.
My computers also back up to the storage box via borg, except for the Photos, Music and Video directories, for the same reasons. My partners Mac is currently backing up to an external USB drive, but the plan is to move them to Backblaze for the easy SAF and/or the NAS as a Timemachine target.


There are dozens of us!


Helix when I can install things, vi when I can’t.
Absolutely, there’s a huge difference between thinking about doing something and then letting the thought go compared to doing anything on the path to actually doing it.