

This is a nod to the “year of the Linux desktop” meme


This is a nod to the “year of the Linux desktop” meme


So 2026 is “the year of the AI PC”?
Lol
Here is Shelly-Anne Fraser-Pryce (multiple Olympic medals as well as world championships in sprinting) running in a school parent’s race vs. other moms.
To all of you who make their own pizza but hate the crust:
There is no rule that you can’t just pour the sauce right up to the edges and sprinkle the cheese even further.
Then you have a cheesy crust but no dry/hard dough crust.
He means before the wish.
Also she hasn’t wished for anything, so…
Meh, slop.


You’re technically correct, but missing my point.
Yes, it’s both ‘a cloud’ but a VPS is much cheaper and needs way less configuration compared to a so-called ‘cloud provider’ like AWS, Azure or Alphabet (or other companies starting with the letter A, I guess).


No. You see, it’s much easier doing the same thing in some cloud like aws and paying a small fortune for a slower server than on a vps.

Why not also post a link?


This looks cool. If a friend asks me, how to deploy the stack, I’ll refer them to this. Good work.
Just use the !s bang in your ddg search. It forwards your search to startpage, a google proxy. Same results but more protection.

The paradox disappears the moment, you handle tolerance differently.
Handle it like a social contract that everyone is automatically part of. All are tolerated until they stop tolerating people who are also part of the contract.
Whoever stops tolerating people who are part of the contract loses their “being tolerated privileges”.
“Sir, what are your thoughts on the current situation in the middle east?”


Sorry I misread your comment.
You are right, this definition is wrong.


The article literakky says “a huge number of IPs”. Do you have more information?


Apache has the better open source tooling IMO.
I use both, but at work I prefer apache simply for its relative ease of setting up our SSO solution. There is probably a tool for that in nginx as well, but its either proprietary or hard to find (and I did try to find it, but setting up and learning apache and then SSO was actually easier for me).
Absolutely not. Cyber attacks are not comparable with real attacks, when it comes to counterattacking.
I mean, how would that even work?
Let’s do an example: A hospital has a cyber attack.
Assumption 1: We notice the attack.
This may sound stupid, but maybe we don’t even notice, that data is stolen and no one ever notices.
But they want to destroy shit, so they do!
Okay, let’s say we notice the attack.
Assumption 2: We notice the attack in time.
What does that mean, they destroyed stuff, right?
Yes, but when? Some attacks delete backups for weeks and then destroy the data. We are talking about a government and not a money hungry hacker group here, they have time.
Maybe all traces of the attack are deleted, before all goes black?
But we’re the good ones, the smart ones, we notice it in time. Cool.
Assumption 3: it’s possible to trace the origin.
Again, how do we do that? Does the code look russian? Maybe Isreal just knows how to trick us. We maybe have no IP, since it came in via USB or CD?
Okay, we’ll ignore that. We have an IP.
Assumption 4: The IP tells us, who it was.
An IP from Israel attacks an american hospital. Clear case, let’s attack back. Right? Wrong.
The IP is private, so it could be some random dude and you just attacked a country for one person doing a crime? Great job.
Even worse, maybe the person has a hacked smart fridge and the attack came from Russia. How would you know?
Okay, let’s say the IP is from a datacenter. Bad example, they rent their servers…
Okay, the IP is from a government agency. Now we’re talking. They don’t rent; it’s unrealistic, they were hacked. We can attack back!
Assumption 5: We know, what to do next.
(This is not a strong argument, but it stills stands)
But what do we attack? One of their hospitals? Do we start a war with them? Call the embassy?
All of this on all the prior assumptions…