ReVanced is a FOSS project, including the patches.

Use the normal YouTube app, and patch it with reVanced (on your phone). Doesn’t directly support peer tube, but it’s an ad free experience that you can tailor to your needs (including sponsor block and more).

Long-term cause it has at this point been around for actual decades.

If you’re gonna use an overlay network like Tailscale I would highly recommend also taking a look at netbird. Similar concept, but fully self hostable if the need arises (but not recommended unless you have a specific need).

My various servers, firewall and nas are relatively power optimized. Everything including switches (most with some 10g ports) and access points is 160 W or so. I can’t give you monthly usage, as I’ve got solar+battery so it’s frequently just 0 kWh for some days. It’s also rather hard to separate from the other power usage in the house when solar doesn’t fit cover it.

Mailbox.org is another candidate worth looking into.

These universal statements are almost never true. What means “most”? All 3 that I have are more, some up to 25W. If they are “new”, maybe. Not many that you can get on eBay are old enough that they will draw a noticeable amount. Add always, “it depends”.

Lemmy has relatively good search, usually if you remember bits of the title that works?

In any case: Both n100/n150 and raspi are in the <10W range. Obviously raspi is lower, but also A LOT slower and much worse connectivity. As the price is roughly comparable, I’d go for the much more capable N100/N150. Only go the full ‘minipc’ route if you don’t mind the (probably) higher power usage, which can depend highly on model. Older (but cheap on eBay) models can be 25W on idle.

Depending on what you actually need, I’d setup a Sync thing or NextCloud or something and go from there.

A VPS is like 5 bucks. Which isn’t nothing but when used as a redundancy or place to send (reasonably sized) backups, it’s cheaper than most alternatives. It’s also still a form of “self hosting”, at least for me.

Exporting, maybe on a schedule, to a keepass to keep somewhere, also works of course. But when hosting the only/main instance at home you’ll have at least one single point of failure, most likely many. Internet connection, server, network/switches, …

For me personally an ad is when I’m being sold something. I can’t be sold something that is free and open. So someone showcasing their paid (but self hosted) service is an ad. Someone telling me about their (open) project is not.

And when someone wants to use either and asks for help, is also (obviously) not an ad. Unless we see a flood of accounts posting trivial questions about a paid service to draw attention to it, but I kinda doubt it.

While I’m fine with people wanting to self-host stuff with closed software (this includes Windows and Plex, btw), I personally am not interested in having ads of any kind in the community.

To me self hosting is about controlling your data. While I wouldn’t use proprietary software myself for this, I just want to make it clear that I’m fine with people asking for help it advice about it. Just not ads, of any kind.

Also very unlikely, as (unmounted) network shares are accessed very differently from Windows and from Linux.

But maybe the right developer was working in that area of the code for a small fix or something, and happened to see what the issue was on Windows and knew how to fix it.

Can’t be, since it’s labeled as a Windows bug and the Linux challenge is obviously not on Windows.

Until very recently, I exclusively used the /56 prefix I get from my ISP exclusively. This is still relatively annoying in my case as this prefix changes at least daily for some reason. Clients get their IP via SLAAC.

I’ve added ULA literally less than a week ago as I have a local reverse proxy I want to handle both local and external request, in both v6 and v4. Obviously more hosts should be accessible from local clients. But I can’t tell local clients apart except by IP, and since the prefix is unstable this would require some sort of hook to update the proxy with that new prefix (might be possible, but seems like a real hassle). So here we are.

Yes, and I don’t know if it could even be classed as a collaboration. They just buy them and resell them with different firmware, basically?

I assume some part of acceptance is required for that in practice, but it isn’t like Fairphone ever advertised them as an official option (as far as I can tell or saw).

The arch package has to be built somehow. You could look at that packages source to figure out how to manually do it on your system, or wait/hope the deb is being maintained and gets fixed.

It’s likely mostly some plumbing, like a systemd service with it’s configuration, to get the audio routed properly.

If you’re using a keepass database, Keepass2Android can natively sync with many cloud options including self hosted and generic ones, even without specific “companion” apps. That’s what I use. In my case, it’s backed by my NextCloud, but it used to be Google drive before.

Just also sync the file on your PC, merging changes from different clients is part of the keepass database format and “just works”.

Also VaultWarden works great if your can self host it, but I prefer keepass for a variety of features and integrations.

Forgejo was soft forked from Gitea after they went commercial and changed the license (I think). If there aren’t any so far, expect pay walled features eventually.

Forgejo turned into a hard fork after communication issues between the teams. I haven’t looked too deeply into it (as I don’t really care about the fact that it’s a hard fork now). This means while it used to be a drop-in replacement allowing you to go back and forth between the two, it’s now an active conversion, I think.

All normal PCs run CachyOS, includes gaming PCs, laptops and media PCs. All servers run some form of Debian (includes Proxmox) or a dedicated distro for their use (TRUE WAS, technically also Debian based).

Maybe look onto OwnCloud. That’s the project NextCloud was forked from many years ago. It’s very much still around and had a very different philosophy, a much more minimalistic approach with focus on stability. That’s actually the reason the people behind NextCloud had to fork it, cause all their additional features (bloat) wasn’t accepted upstream.