I just fixed a bug in the instance blocking, I hope it helps!

Ah, I just found a bug here - the instance blocking wasn’t checking the instance of the author, only the instance of the community. It checks both now.

Thanks for bringing this up!

deleted by creator

Yes although when you post in a remote community the remote instance will send your content wherever. They don’t know who you’ve blocked.

That’s one of the reasons I post in local communities more, these days.

Fuck off Jack

“AI is a tool” is a thought-terminating cliche. The phrase is intended to foreclose other ways of framing the discussion.

Yep. Assume the worst, imo

Ahh so bots are finding subdomains by scraping SSL certificates?

afaik it was always a land-grab / gold rush mentality - capture the market, then figure out how to make money later. Now, it’s later.

Yep. Everything on that site is AI generated. Another one for the block list!

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.

If you’ve ever spent 10 minutes using an AI agent, you’d know that there’s no way to predict how many tokens it’s going to use before you give it a task. It can be $0.20 worth sometimes or $20 other times. Or anything, really.

It’s only after watching it churn away for a few minutes that you can assume it’s gotten stuck and have the option of pulling the plug before the bill gets run up too high. But you need to watch it like a hawk and you need to be the one paying the bill otherwise you’re not going to care (e.g. workers using AI at work aren’t paying for it, their company is).

Taken in aggregate across a month, that unpredictability might average out or it might explode.

I love that a joke candidate has more chance of beating Farage than a real one.

I would love it even more if real candidates had a chance of beating Farage but let’s be realistic about the state of UK politics. I’ll take my love where I can get it.

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.

The train that crosses Siberia takes 4 days to cross it, running 24 hours a day (with 30 min stops once or twice a day).

The author’s video is a good intro to theming KDE, I learned a lot from it.