Cloudflare’s is a corporate solution from the company that man-in-the-middles half the internet and makes me click shit every fucking time. I see it whenever I make the mistake of following a stackoverflow link.

on SO sites all the difference is a single click. and you have to allow scripts and cookies for both, so no difference there.

oh the find with the hash sum is good advice! I would have done this but manually, maybe with the double commander sync dirs tool.

but also, for configs this might be the best time to move your custom config to ordered dropin files for all things that support it.

just wait until they start vibe coding on their brain implant

its funny. when its anubis, the common opinion is rightly fuck ai, but when its cloudflare, then it is somehow fuck the website.

what a weird world we live in.

on the tablet it should work fine in the browser. maybe that would also work on the TV, that’s exactly what most TV apps do anyway.

what? It’s not like everyone needs to run jellyfin at home. the only thing you need to use is the jellyfin webapp, which I don’t understand how is it more complicated than netflix or any other similar service. you log in, pick a movie and hit play. that’s it.

URL into bookmark, username and password onto paper. Dont tell me they can’t do handwriting anymore.

TV? how did they log into their google account to begin with?
but also: they can log in first on the phone or anywhere else, then use quick connect for the TV… added bonus: phone is now a remote.

I cant comment on dead platform, but did you register on instagram for this reason, or was that an old account? in the former case you don’t have one less accounts. but then one could also argue whether deleting one meta service account and registering another makes a difference

that’s not progress, it is trend. in zero ways it is better.

this is not a kyc requirement imposed on facebook based on laws, but by facebook based on their ToS.

you’ll be woken up by the sirens though. that is, if they work

ok but there’ll still be a lot of idle capacity that can be put to good use. I relatively rarely browse I2P, but I’m happy to contribute bandwidth. It’s safe too, because I only see encrypted traffic coming from one relay and going to another one, and it does not run an “exit node”

I thought that was a modified power supply

Opening a port doesn’t mean you are opening your whole home network just the specific services you want.

until a new high severity vulnerability gets discovered and some bot exploits it on your server, taking it over. and you won’t even know. if they were a bit smart, you won’t notice it ever either.

but there’s more! its not only the reverse proxy that can be exploited! over the past few years, jellyfin has patched a dozen vulnerabilities, some of which allowed execution of arbitrary system commands. one of the maintainers have expressed that nobody should be running those old versions anymore, because they are not safe even only on the LAN. and this was just jellyfin.

the whole point of privacy extensions is that it replaces the MAC with a random something. the address is totally unrelated to the MAC

your day becomes so bad that it overflows and wraps around

if that’s true, I assume it is because they don’t know about the security consequences, nor about more secure ways. and for 99% that is the worst solution, because they won’t tighten security with a read only filesystem, DMZ and whatnot, worse, they won’t be patching their systems on schedule, but maybe in a year.

99% users should not expose any public services other than wireguard or something based on it. on a VPS the risk my be lower, but on a home network, hell no!

all of these run the database in a separate container, not inside the app container. the latter would be hard to fix, but the first is just that way to make documentation easier, to be able to give you a single compose file that is also functional in itself. none of them use their own builds of the database server (though lemmy with its postgres variant may be a bit of an outlier), so they are relatively easy to configure for an existing db server.

all I do in cases like this is look up the database initialization command (in the docker compose file), run that in my primary postgres container, create a new docker network and attach it to the postgres stack and the new app’s stack (stack: the container composition defindd by the docker compose file). and then I tell the app container, usually through envvars or command line parameters embedded in the compose file, that the database server is at xy hostname, and docker’s internal DNS server will know that for xy hostname it should return the IP address of the container that is named xy, through the appropriate docker network. and also the user and pass for connection. from then, from the app’s point of view, my database server in that other container is just like a dedicated physical postgres machine you put on the network with its own cable going to a switch.

unless very special circumstances, where the app needs a custom build of postgres, they can share a single instance just fine. but in that case you would have to run 2 postgres instances even without docker, or migrate to the modified postgres, which is an option with docker too.

I have very rarely ran into such issues. can you give an example of something that works like that? it sounds to be very half-assed by the developer. only pihole comes to mind right now (except for the db part, because I think it uses sqlite)

edit: I now see your examples

It’s not like it’s so hard to rebuild a container for the occasional services that needs it. but it’s still much better than needing to do it with every single service