Good luck! I did the same recently. I wrote my own blog system, though. I can share it with you, but I’m not sure it’s the best for anyone else, there were some shortcuts taken given I did not intend to share it.

You can check out my blog and let me know whether you want to try it: https://chrastecky.dev/ (or federated: !programming@chrastecky.dev, !3d-printing@chrastecky.dev, !gaming@chrastecky.dev).

Ah, so reporting stuff he said as if it was true, even though this is not a Signal security issue, but his incompetence is fine in your book?

So what, if Trump says random bullshit, every news piece about it should sound like they actually agree with what he said?

Okay, enjoy your articles about Signal security issues.

I don’t particularly care about your fish or your frying.

And are you going to call both a “bank security issue”?

So you’re gonna pretend that’s your first interpretation of the meaning of the sentence, huh?

Edit: Also, that’s wrong interpretation of what happened either way, guess the title doesn’t work even if you’re intentionally obtuse.

Nope, it’s not. The part saying “the only glitch in two months” is indicated as a quote, but overall the title sounds like there’s a security issue in Signal and Trump chose to dismiss it because it’s the only glitch in the last two months.

Sure, but I don’t really care what that idiot thinks. When I read an article about there being a “Signal security failure,” I expect there to be a Signal security failure.

Nah, the idiot is the one who spreads misinformation by using misleading titles. In what world did a “Signal security failure” occur? The title is extremely misleading and one can only hope it was incompetence; not intent.

What Trump calls things should be irrelevant to a news site.

Which idiot created the title?

For anyone interested: there wasn’t any Signal security failure, someone sent stuff via Signal to people they shouldn’t have.

It’s a cluster of workers where everyone can generate images/text using workers connected to the service.

So if you ran a worker, people could generate stuff using your PC. For that you would gain kudos, which in turn you can use to generate stuff on other people’s computers.

Basically you do two things: help common people without access to powerful machines and use your capacity when you have time to use the kudos whenever you want, even on the road where you can’t turn on your PC if you fancy so.

Try running an AI Horde worker, it’s a really great service!

It’s such a classic, I say it every day to myself when I wake up.

You can use https://schedule.lemmings.world/ to automate the posts. Or, given the community we’re in, you can selfhost it!

This week I’ve been doing some work on my GOG Downloader to finally back up all my GOG stuff when I buy new disks, that’s pretty much it for my selfhost/homeserver stuff this week.

I only ever used SSH, so I don’t know.

IIRC, that’s exactly it. You can either use their GUI (which is not half bad) or you can use the docker command in the terminal after you install the package.

The easiest would be using docker, you can set up the container to always restart, that way it will be started automatically on NAS restart.

You can also download node.js from the Synology software center and manually add a cronjob to run after reboot, but the docker way is probably the best way to go.

IIRC, you can’t control to which port it’s bound which is not that useful.

As others have said, you have bound your host port 8080 to container port 9090 and then you use caddy to reverse proxy to container port 8080, which doesn’t exist.

As for DNS, it’s just a translation system - you send a domain, it returns its IP (for A or AAAA), everything else is done on server. So your current setup works.

Yes, you can deactivate the port, if you’re not gonna use it on the host, you don’t need it. Since you’re connecting via the internal network, you’re not using the bound ports.

As a side note, use some firewall and disable everything but 80, 443 and 22, you should not leave other ports open, especially if you’re binding all the ports in docker like that.

And perhaps make it a good habit to bind ports to 127.0.0.1 by default, that way no one outside the local server can access them. You can do it like this: “127.0.0.1:8080:9090”

Depending on how much you want to donate, you could also pay for a server somewhere. For example Hetzner hosting starts pretty cheap. That way you can self-host without having to host it on a physical machine.

Honestly, you already have the image locally if you’ve pulled it.

I guess not everyone treats their PC as an ephemeral storage, huh? I don’t trust anything that’s available only locally to survive.

Hmm, seems like my definition of “secret” is way different than Bill Gates’.