https://chrisdown.name/2026/03/24/zswap-vs-zram-when-to-use-what.html

Chick sexers are an old example of this phenomenon. Surprised it was left out from the article despite it being widely known for it.

https://www.youtube.com/watch?v=6m8id5wHblY

Mine sits at about 50-60W

same but it doesn’t change with load, whether it’s idle or maxed out, it’s in that watt range

I knew it …

As far as I can see it is still just postman but the request and api definitions are stored in textfiles (and there are multiple projects that do exactly that already).

It seems to me that the blog author is talking about something beyond that.

Sounds great in theory, but without a concerte suggestion on how that might actually work and be implemented it’s basically a scifi daydreaming nothingburger. (Or the pitch for the writers upcoming startup)

I’ve been running it for 2 years.

The swarm support integration is first class, but there is not much to do in the gui, you can add nodes and see basic info about them and thats it basically.

Most of the stuff happens in the compose files where you can define how many copies of a container you run and what nodes you want to restrict them to. etc.

I’m not sure about the moving features tbh. It should move them automatically when a node is down. In my setup I don’t use that at all, all my containers are pinned to specific nodes by feature flags (one node has lots of hdd storage, another has more ram, another has a gpu).

You can see the container logs, but you have to select “swarm” in a dropdown when the container is not on your master node.

And also when deploying a new app you have to select “Compose” and then in a further dropdown “Swarm”.

I’d save up +30€ and wait for the steam controller to be available

deleted by creator

I’m running dokploy in swarm mode on 3 nodes.

The only downside is the development of swarm is basically halted and some features are missing (like passing /dev devices to a container, you have to use dirty workarounds) but otherwise it just works.

not yet and it doesn’t look like microslop feels like adding it.

Dirt Rally 2 and AC Evo seem like good alternatives with VR support.

Should have used agpl if they wanted to be noble.

But this is just a corpo moating strategy.

Mostly the uutils.

• MIT license isn’t nice.
• They have way more CVEs than the core utils they replace.
• They don’t have feature parity yet, so if you use some rare flags in your scripts, those will break.

https://www.youtube.com/watch?v=tG2ZMvBT8W4

4:25

(sorry my third party youtube frontend can’t share timestamp links)

tldw:

• more CVEs than the old core utils that have been tested and in prod for over 30years
• no feature parity, so existing stuff that uses them will suddenly misbehave, when certain flags are missing
• different license, MIT instead of copyleft, so it’s more friendly for companies to use it for profit, while abusing the work of volunteer contributors

Depending on where you live, going to IT events and conferences to connect to people in person is even more powerful. Ask them about their work and talk passionately about related stuff that you have some knowledge/skill in. Exchange contacts, say you’re looking for work.

For example, next month is DEVWORLD in amsterdam. They always give away free tickets close to the start of the event. I’m sure there are a ton more like this around the world.

As for writing applications: For me writing very high quality applications did the trick.

• only apply to companies/positions that you are REALLY interested in
• research the position
• research the company
• if you can find somebody that works there in a similar position, ask them some questions
• use the info you gathered to show interest in your appplication
• write everything yourself, no AI writing. Be a genuine human.
• But you can use AI to give it the position and your application and tell it to make a hiring decision with pro/con arguments and rework it based on that
• make a small demo project that shows off your relevant skills and tell them about the challanges you had and what you learned to overcome them

(About the last point: I found that talking about relevant hobby projects I did and showing the code made a huge difference)

It usually takes me about a week to write one such application. But I only sent out 3 before hearing back from 2 of the companies and getting signed on by one.

I know it’s a lot more hoops then just clicking “auto apply” or “apply with AI”, but the effort pays off.

Contrary to that I often see people complaining online about how they wrote 100 applications in a month and got no job interviews… yeah buddy. (And I was initially one of those people)

https://en.wikipedia.org/wiki/Anthropic#U.S._military_and_intelligence

Also netcup has really good deals during the winter holidays

The problem could be anywhere in between the internet and your server.

Ofc. it could be your routet. But I think the following is more likely:

It might also be your internet service provider that doesn’t allow those ports for inbound connections.

Or you’re behind a CGNAT so your real external ip is different from the one you think it is. (look up online how to test this)

Sounds good.

Hmm next you probably should confirm ports 80 and 443 are actually reachable from the internet.

Use an online port checker like https://canyouseeme.org/

After that you should check your apache config like somebody else already suggested. I haven’t used apache in a while but if I remember correctly:

Ensure it says: Listen 80 NOT: Listen 127.0.0.1:80

(and same with 443)

Also check your VirtualHost — it should look something like:

<VirtualHost *:80>
    ServerName yourdomain.com
    DocumentRoot /var/www/wordpress
    # ... other settings
</VirtualHost>

(and same with 443)

Njalla’s default TTL for DNS records is 3600 seconds (1 hour). If you just created or modified the A record, it can take up to that full hour for the change to propagate across the internet, which would perfectly explain why Certbot is connecting to the right IP but failing to fetch the file (the request might be hitting an old IP or a cached null response).

Before changing any more configurations, you should verify what the rest of the internet is actually seeing for your domain right now.

Check the current DNS record

You can usedig to see exactly what IP your domain is resolving to, and importantly, the remaining TTL on that record.

From your local machine (or any computer), run:

dig yourdomain.com +noall +answer

This will output something like:

yourdomain.com.    3412    IN      A       203.0.113.45

The second column (3412) is the remaining TTL in seconds. If that number is counting down from 3600, the record is still propagating. If the IP address shown there doesn’t match your server’s current public IP, the change hasn’t taken effect yet for that DNS server.

Check from a different perspective

To ensure it’s not just your local ISP or router cache serving an old record, query an external public DNS server directly:

dig yourdomain.com @1.1.1.1 +noall +answer
dig yourdomain.com @8.8.8.8 +noall +answer

If these external servers show the correct IP but Certbot still fails, the DNS is fine, and the problem is somewhere in your network routing or web server config. If they show a wrong IP or no record at all, you simply need to wait for the TTL to expire.