oranki

mDNS refers to multicast DNS (.local), while similar you should not mix it up with Tailscale’s MagicDNS, which is entirely a Tailscale thing, dependent on their APIs.

mDNS also seems to be what you’re after too. For the hostname-only resolution to work, you need to have Avahi or equivalent mDNS daemon running on the hosts, and add .local to the search domains. Setting search domains can be done manually on each host or via DHCP network-wide.

With mDNS and .local in the search domains, when you try e.g. http://myhost/ in the browser, the browser first tries myhost, then adds each search domain, e.g. myhost.local. Since .local is reserved for mDNS, querying it results in an mDNS query in your network, and if there’s a device with a matching name, it will respond with it’s IP address.

Note that if you have Tailscale and MagicDNS active, your tailnet’s domain will (or should) be the first one on the search domains list, and your DNS server is set to 100.100.100.100, which is a dummy address on which the tailscale daemon runs the internal DNS server for Tailscale, including MagicDNS.

Multicast DNS / Avahi is a little bit error prone in my experience, but when nothing goes wrong, this would give you what you’re looking for.

There are other options, like your router automatically registering DNS entries for DHCP hosts, or running a separate DNS server anf manually adding records for the hosts you need this for.

If it’s worth doing, it’s worth overdoing!

No, I haven’t tried OC. Lot of people still prefer it over NC. I think both have come quite a long way since then.

I wouldn’t say Nextcloud is hard to maintain, even less so if you keep the number of apps to a minimum. The initial setup may require some work, but small instances are mostly plug and play.

Note that I’ve never used AIO. If going for containers, the community images are better, despite AIO advertised as the official method. I recommend using Podman, check out

https://github.com/0ranki/nextcloud-previews

Also a blog post: https://oranki.net/posts/2025-01-02-self-hosting-my-way5-nextcloud/

Nextcloud, despite you’re not considering it. You can disable or not install the apps you don’t need, like Calendar, Contacts, Photos, Dashboard, Activity, etc.

There’s also a fork of Filebrowser, called Filebrowser Quantum, which I’ve been interested in, though haven’t tried yet: https://github.com/gtsteffaniak/filebrowser

The Universal Blue people emphasize containerized stuff a little too much. It’s perfectly possible to add non-flatpak software to ostree distros, it just slows update processing down a little bit.

Since abraunegg onedrive is available as an RPM, you can just layer it on top of Bazzite; download the rpm and and then rpm-ostree install ./onedrive.rpm

If the RPM works on Fedora it will work in ostree distros too. Besides, if it foesn’t work, you can just rpm-ostree rollback and it’s like you never installed it, apart from things in your $HOME like config files.

The recommendation is to avoid layering wherever possible, not that you can’t do it. Many apps are still a bit wonky as flatpaks, even if available.

I set the color theme to as black and white as possible, then use the themed icons because it makes the phone less attractive to look at. Contemplating on setting grayscale mode on full time.

So yes, I don’t like it either.

I only use Ublock origin and Bitwarden, so that narrows the list down if so. I’m also using Flatpak.

It might coincide with FF upgrades. Can’t pinpoint enough to even make a bug report.

+1 on this. Been trying to search if anyone else runs into this, but you’re the first one who has had the same issue.

Can’t say it’s consistent, but happens maybe every week or two.

I haven’t tried an OG Mastodon server, but currently running a GotoSocial instance, just for me.

With mostly the default retention etc. settings, the instance takes at most a couple gigs of storage space. If some image has been rotated, it will be refetched if you view the post again.

As for Federation, a single user instance is probably not a good idea if you’re just starting with the Fediverse. Only content from accounts a user on your server follows will reach your server, including posts boosted by the people someone follows. I was already following about 150 accounts when I set it up, so I didn’t really notice much difference in the home feed.

OG Mastodon can utilize relays, which will help with the lack of content.

For following topics, I made another user that follows some hashtag bots from fedi.buzz. The bots boost all posts with specific hashtags, so the posts reach my server.

If I were to do this again, I’d probably go with full Mastodon instead of GtS, just because I like the UI. There are other niceties too.

I think there’s no way to keep the same domain while changing the underlying server software, without breaking federation. If someone knows a way I’d be really interested.

There aren’t that many providers who have gmail-like labelling functionality, but luckily Gmail serves labels as folders over IMAP. May cause a lot of duplicates, though.

Thanks. Last time I tried it was just after bookworm released, and on ARM, so it has probably got better

It’s a really solid combo, but if you’re not familiar with CoreOS I wouldn’t change both at once. Meaning migrate the services to Podman first, then switch the OS. I’ve meant to switch from Alma 9 to CoreOS a long time, but haven’t found the time.

I noticed you run Nextcloud AIO, just so you know, that’s one of those “mount the docker socket” monstrosities. I’d look into switching to the community NC image and separate containers managed yourself. AIO is easy, but if someone gets shell to the NC container, it’s basically giving root to your host.

Either way, you’re going to have trouble running AIO with Podman.

I’m very much biased towards Podman, but from what I understand rootless Docker is a bit of an afterthought, while Podman has been developed from the ground up with rootless in mind. That should be reason enough.

The very few things Docker can do that Podman struggles a bit with are stuff that usually involves mounting the Docker socket in the container or other stupid things. Since you care about security, you wouldn’t do that anyway. Not to mention there’s also rootful Podman, when you need that level of access.

I’d recommend an RPM-based distro with Podman, the few times I’ve tried Podman on a deb distro, there’s always been something wonky. It’s been a while, though.

I have to join the choir, what do you mean dying and doesn’t work? If proprietary apps don’t support it, it’s just because it’s one of the best ways to lock people in.

You need the G account to be able to install apps from Play Store, I don’t believe the private space itself requires it.

Not sure if there’s some Play “integrity check” on stock ROMs, but on GOS I was able to create the private space and download&install F-droid or other APKs just fine, without a Google account.

I’ve never used Portainer, but does it have an option to only notify of available updates?

For things that I don’t mind breaking, I use latest. For the services that matter, use a specific version. Take Immich for example, in the 2-3 months I’ve kept it running, there’s been 3 breaking changes that would prevent startup after update without manual intervention. Immich is an extreme though, some other projects have been working fine with latest without touching them for years.

I follow the important projects’ releases (subacribe if possible), and update manually when they publish an image with a new version. I’d see it as either updating manually and being OK about possibly being a version behind every now and then, or using latest+auto updates and being OK with waking up to broken services every now and then. Which might never happen.

Maybe you get the possibility of routing all traffic from a container (or all the containers in that namespace/network) over the tailnet this way? With the host method, you’d need the host to use the exit node too.

Have you considered lowering the unprivileged port limit instead?

sudo sysctl -w net.ipv4.ip_unprivileged_port_start=53 | sudo tee -a /etc/sysctl.conf  

Then remove the firewall rule and bind to port 53.

Edit: typo