Hey @organicpu@lemmy.organic-server.org did you use a LLM like Ollama to write your post?

No shade if you did, I just want to make sure we’re categorizing things correctly at our end.

It’s a good thing piefed already has this functionality, then.

Ahh yep, that’ll be it. Thanks.

That I regret link isn’t working for me.

This seems like a good time to ask this.

Are you reading the things you post or is it automated?

Is that a pond and is it supposed to be that colour?

Fuck off Jack

Ahh so bots are finding subdomains by scraping SSL certificates?

If you ever wondered why the green in photos like this (sunlight coming through leaves) is not as vivid as real life, this is why - https://moultano.wordpress.com/2026/06/19/where-to-find-the-colors-your-screen-cant-show-you/

Good question.

A GUI will be easier to get into - you can use a gui file browser app to learn the layout of the file system, you can use a GUI text editor to change config files, that sort of thing. It’ll mean you can do a few basic things intuitively which will be less intimidating. So from a maintaining momentum and morale point of view it might be best to have a GUI initially even though you have to learn all the cli stuff eventually anyway and you’ll most likely be running a headless server on real hardware eventually.

Self-hosting is a very individual journey - everyone wants different things and finds they own way to meet their own requirements. So there isn’t really one guide that covers everything.

Anyway, as a general road map:

1. Create a Virtual Machine on your PC. Install Linux inside the VM.

2. Play around in the VM to learn Linux basics. When you break the OS you can just wipe the VM and reinstall.

3. In the VM, try some docker containers until you’re comfortable-ish with docker.

4. Maybe try Yunohost in the VM. You might find Yunohost saves you a lot of time and hassle.

5. Get hardware suitable for your goals.

6. Install Linux, configure networking and docker containers on real hardware.

Replying to this post with an AI slop comment takes some balls, mate

No obvious signs, nope. It wasn’t until I started using it in earnest that I got suspicious and then when trying to work on the code it became very clear.

Well, yeah. There are lots of reasons. But basic self-interest is something we can all agree on.

I made the mistake of installing Starling recently, not realizing how it was made. I contributed a PR to it, wrote a few issues describing some showstopping bugs, and since then there’s been absolutely no activity from the creator.

That’s fine, they are under no obligation to work for free. But I wouldn’t have installed it if I knew it was abandonware.

You could use apache to create a webdav share. I bet there’s a pre built container for it.

Webdav is really underrated, imo.

Really old CPUs (486 or earlier) lack the computing power to do SSL at any decent speed. So you’re limited to serving http, gopher, nntp, or telnet. Maybe IRC.

You could have a modern computer handle the SSL connection and proxy requests through to the antique but some of the purity of the thing is lost by doing that.

The other day I made a machine learning model that classifies images as either ‘a certain type of undesirable image’ (no, not porn) or ‘any other image’. It is 96.4% accurate and takes 14 ms to classify one image (using CPU only - with a GPU it could be 5x - 10x faster).

I plan to offer this as an API service that social media networks can use to filter posts.

I’d hook up https://easydmarc.com/ for a couple of months to monitor deliverability, just while you’re bedding it in.

deleted by creator