When a regular website is visited through Tor Browser, Tor protects/anonymizes you as a user. If a website is hosted at an onion address, the web server is also protected by Tor, the same way as you are.
When a regular website is visited through Tor Browser, Tor protects/anonymizes you as a user. If a website is hosted at an onion address, the web server is also protected by Tor, the same way as you are.


Well, I’m sorry. I’m not Terry A. Davis.


Lots of things.
I’d start a YouTube channel to document my travel life, but Google.
I’d use LinkedIn to expand my professional network, but Micro$lop.
I’d join communities related to my hobbies that mostly exist in FB groups or subreddits, but, yeah.
There are also things I still do, although differently. Like using Google Maps to view detailed information about places, like accessibility, restaurant reviews etc. But I only do it through a browser, and I use CoMaps for navigation. Or banking apps, due to convenience. Or the GoPro Quik app so I can remotely control my GoPro when I mount it on the outside of my car. Or music streaming services.
Surveillance sucks, but I try to find compromises that I can live with when needed. I can live with some inconvenience, but to a degree.
Both Debian and RHEL-like distros are solid choices. Both are super stable. Debian tends to not always have the newest packages, so if you want that I’d steer away from Debian. Personally I use Rocky Linux for my servers. It’s based on RHEL, meaning each new major version benefits from Red Hat’s 10 years of software support. Debian (and derivates) have better community support I think, but RHEL has very solid documentation (which for the most part applies directly to Rocky, Alma etc.)
Here’s a great article outlining the differences between Alma and Rocky.
But for something simple like running a Go application, both should work just fine, so choose what you’re most comfortable with.
Rocky is available at Scaleway too.
Have you tried screen? AFAIK it’s similar to tmux, but tmux has more bells and whistles, which it sounds like you want to avoid. I use it sometimes to start long running rsync sessions on a server and then periodically SSH in and check it. It does break scrolling though, but I don’t know if there’s some option to make it behave more like a normal terminal.


Well, I looked up your username on Codeberg and assumed https://codeberg.org/codewizard was you, so I thought you’re a developer from the linked website.
Like what @pat_dev@social.linux.pizza said, sites like Codeberg and GitHub are intended to store code repositories, not photographs/albums and other personal files. If you were to host the source code of a website and have some images there that are part of the website, then sure, it’s considered part of the website source.
I’d suggest looking for cloud drive/storage solutions (like we know it from Dropbox etc.) I’ve heard great things about Filen. They’re based in Germany, end-to-end encrypted and their clients are open source. Or, of course, there’s Nextcloud, but it either requires self-hosting skills or knowing someone who will host it for you (there are hosting providers out there).


What kind of images are we talking about? Container images, VM images, or good old images taken with a camera? It’s not really clear from your post.
One simple way to run a Tor bridge: The Snowflake extension. It’s a browser extension that runs whenever you use your browser.


Oh well, they did in the past.


Several of the big privacy people have recommended them online, e.g. Techlore, so I’d say yes. Though it’s been a couple years since I saw those reviews, and I haven’t read up on them recently.
EDIT: Grammar.
Bazzite is the more gaming oriented flavour of Universal Blue’s distros, but take a look at Bluefin if you wanna try something similar (but not focused on gaming, although gaming also works fine on it). I’ve used it for about a year or so myself, and I love it. It’s immutable so it “just works”, but I can still play around and tinker with distroboxes or VMs.
Not really. It’s more similar to if the webserver was connected to the internet through a VPN with it’s HTTP(S) port forwarded through the VPN. You connect to the VPN’s IP address, which forwards to the webserver’s IP which stays hidden. And you yourself are also connected to the internet through a (separate) VPN. Now, instead of a VPN connection, both you and the webserver are connected to the internet through Tor circuits.
This video does a good job of explaining how it works.