eleijeep

Long time lurker

Joined: a week ago

Can you use DNS challenges instead? That would just require that you can create a TXT record in your domain.

Using an LLM to do a database migration is like asking your neighbour’s kid to file your taxes.

Vibe-coded slop is horribly insecure and the dev doesn’t understand the codebase?

shocked_pikachu.png

Where is the documentation for self-hosting it?

Get a UPS.

The great thing about Lemmy is that if we don’t like the moderation policies of an existing community, we can just make a new one with the same name on another instance. With blackjack and VPSs.

You need to look at the DNS server used by whatever client is resolving that name. If it’s going to an external recursive resolver instead of using your own internal DNS server then you could be leaking lookups to the wider internet.

Is it now handing out IPs in a different subnet? Check the IP given to your client.

my ISP was hijacking my DNS queries and changing it to their own DNS server

Which ISP? Name and shame!

What does hashwash mean? I googled it but I just get instructions on how to wash my hash.

Get a job in pizza delivery, you’re sure to meet some interesting characters that way.

> Joined 3 hours ago
> first post is concern trolling

You wrote this shit with an LLM, didn’t you?

The FreedomBox project started in 2010, and it’s a Debian-based plug and play device that lets you easily self-host useful network services.

This is just an ad for “Viduli, The AI-native cloud platform”

The discussion itself is off-topic for this community anyway. Who would even think about using “serverless” for self-hosting?

Ah, docker compose makes it easy! Thanks.

I just configure them to use the network stack from that container.

Can you explain how you do this (or link to a guide that you found useful)? Thanks

You get incremental backups (snapshots) by using

--link-dest=DIR         hardlink to files in DIR when unchanged

To use this you pass in the previous snapshot location as DIR and use a new destination directory for the current snapshot. This creates hard links in the new snapshot to the files which were unchanged from the previous snapshot, so only the new files are transferred, and there is no duplication of data on disk (for whole-file matches).

This does of course require that all of the snapshots exist in the same filesystem, since you cannot hard-link across filesystems.