I hadn’t heard of this, reading about it now. If you’re referring to the same thing, it seems they refused DNS service for a website that hosted videos showing extreme violence, because it violated their ToS. If they really did not release the domain immediately, that’s a bit questionable, but personally I don’t think it’s a big scandal or anything, as far as tech companies go.
- 0 Posts
- 18 Comments
I set up a mailserver in NixOS. It was a bit of time investment because I really wanted to write it myself and understand how it all fits together, but maintenance is not an issue; I haven’t touched it through 3 distribution upgrades. A friend just copied my config on a VPS and it works for them as well.
There’s also a turnkey mailserver nix project that I haven’t tried but it seems to just work: https://nixos-mailserver.readthedocs.io/en/nixos-26.05/
(I realize that NixOS is the new Arch, actually, but this sort of stuff is where it really shines.)
I self host but I used namecheap’s private email before and it was fine: https://www.namecheap.com/hosting/email/
rm -rf /(don’t actually do this obv)
a14o@feddit.orgto
Privacy@lemmy.ml•Slackware Says No to Age Verification, But Fedora Linux Says Yes
17·8 months agoOff-topic, but isn’t Fedora technically upstream from RHEL?
a14o@feddit.orgto
Selfhosted@lemmy.world•My thoughts shopping around for a wiki solutionEnglish
7·9 months agoHave you tried
Outline?
I recently set it up and I’m very impressed.
a14o@feddit.orgto
Selfhosted@lemmy.world•Caddy reverse proxy fails with a login pageEnglish
5·9 months agoSeems like the router doesn’t like how the headers are passed on. You could try:
login.router.lan { reverse_proxy 192.168.1.1:80 { header_up Host {upstream_hostport} } }https://caddyserver.com/docs/caddyfile/directives/reverse_proxy#headers
I have a very similar setup and it’s been running without major hiccups for years.
I’ve been hearing the same tales of caution ever since I got my hands on that SUSE CD-ROM. I’m definitely much more careful when touching the setup compared to other stuff I self host, but it’s not impossible or anything.
It’s not something one should hurry. Read up on all the standards and documentation, set them up step by step with a throwaway domain. Avoid the big no-nos from the very beginning: Make sure to never accept relay submissions from unauthenticated users, and don’t bounce anything off-server.
It’s been a fun journey for me, and I always find it a bit sad when people who might be interested to learn are immediately discouraged. If you feel like giving it try, go for it!
Oh I’m sure it runs perfectly fine in a container, it’s just not my preferred setup.
It’s a good idea in theory, but it’s a challenging concept to have to explain to immigration officials at the airport.
I don’t know of such an alternative. A quick solution would be to use something like GeoNotes to take geolocated notes.
As far as a self-hosted solution goes, I’d just like to point out that you wouldn’t need a self-hosted database of places. You could query Ouverture (or Google, OSM, etc.) for places near you, and you’d just need to store the check-in on your server with a basic API. This is an interesting problem, and not super hard to implement.
I think you’re spot on: Markdown files with SyncThing. That’s my setup as well, you just can’t beat markdown files as a back-end for flexibility and future-safety in my opinion.
Some things to consider:
- Editor: The obvious no-nos are editors with built-in AI support or cloud storage. FOSS editors are highly recommended. If you find a good offline FOSS WYSIWYG-style markdown editor, let us know. I use Neovim myself, but I’m often asked for recommendations by non-geeks.
- Operating system: You should be fine on MacOS (for now), but Linux is a great option for desktop. Windows is a loose canon with their AI snapshot approach, definitely avoid. What are you syncing to? Mobile devices are a lot more difficult to keep control of.
- Encrypted devices: Make sure you have full disk encryption on all devices and on all your backups.
That depends on your threat model. It’s a useful strategy to hide your traffic from your local network admin (e.g. at the workplace) and your ISP, but it’s a bad strategy for hiding your identity from the sites you’re visiting.
I’m sure you’re a great couple but if your concern is future-proofness consider separate domains.
Privacy is a trade-off against convenience, and there is no perfect privacy.
VPNs are a mediocre privacy tool, because they presuppose trust in the VPN provider. Tor is flawed because it is open to correlation attacks.
There are low-hanging fruit that everybody should be using like sensible cookie policies, HTTPS-only mode, and DNS over HTTPS.
If you are looking for a solution on the far end of privacy/inconvenience you could look into I2P and use that situationally.
Should really be prefaced by: Don’t bring your phone. Write the phone number you plan to call if arrested on your lower arm in sharpie. If for some reason you have to bring your phone, read the following.

It’s just a hetzner box. I think the most important consideration is not changing the IP if you can avoid it.