Well, you can’t get updates from other instances without it being connected to the internet and reachable. So for your usecase you do need it connected to the internet. On the LAN you will only be able to see other instances on the same LAN.

Lemmynsfw uses a custom version that that removes the blur for nsfw images but that’s it I think.

It is still very young and I don’t yet see any advantages over Rust, except that they want to have out of the box interoperability with C++. Let’s see where they are in 3 years or so.

Yeah I meant the intentional degradation. Good to know they don’t do that anymore.

Unlike Apple, Android phones do not kill their battery life after 3 years. On the contrary, I swapped my S9’s battery myself and have it a longer life as a secondary phone for traveling or backup. With the restored battery that old exynos chip is still good enough to run most apps to my satisfaction. Even my newer one is not a current gen model. For me, the only reason to upgrade anymore is security updates and most users don’t even care about that. Okay, maybe the cameras still keep getting better but only marginally.

Isn’t there a whole weird world of ipv6/V4 tunneling schemes that try to connect the two? https://en.m.wikipedia.org/wiki/IPv6_transition_mechanism Not sure if anyone supports these though

Oof, imagine having to put a single 9 into your SLA. You would be laughed out of the room in a commercial setting.

Voidtools’ Everything for Android would be cool indeed. But iirc androids filesystem already has a global database of files, no? So shouldn’t any file manager be able to quickly find anything in there without walking the hierarchy?

This could mean that multiple lemmy processes can share that folder but it would be a stretch to assume that a single process can serve multiple domains.

You need to run one Lemmy per domain then. I would like to see the parts of the doc that suggest that this is supported.

I would suggest not separating the storage from the server that far. It would probably be wiser to run the app with less latency to the storage and accept more latency on the web frontend. In short: use your VPS as a gateway only and put the actual host for the respective app into your home behind a VPN.

What do you mean by site? Having one process serve multiple instances with different domains? Or do you just want to define custom styling per community?

The daemon script is simpler, true. but usually you can just point your router at some dyndns URL and you could put an internal IP for that.

I think using the cloudflare API is the way to go. You could probably set up an internal service that translates your home router’s dyndns request to a cloudflare API call.

Now add a link “you want to go here” that links to gihtub.com

classic

Out of curiosity: why are you putting vaultwarden behind a cloudflare tunnel?