Synnr

ROTFLMFAO!!!!

Yes you can but for people that are looking to set one up today, not someone that's been running one for 5 years and has basically a whitelisted reputation, it takes a lot to set it up and keep your domain and IP space reputation solid, along with DKIM/SPF/etc records, all the latest stuff like Google's new mandatory unsubscribe header that will keep coming up. Even if a couple people on your hosting provider start spamming, if they're in the same IP space as you, You're going to be getting filtered more heavily for using a "bad neighbor" host. The big corporate/"nonprofit" guys like Spamhaus and Google and Microsoft are basically those controlling corporations for emails, what they say in their spec pretty much goes. They're making it h em oarder for people to set up and run their own email servers, whether that is the outright intended effect for their mandatory changes or not.

Don't get me started on trying to set up a business newsletter account on your new corporate mail server, holy hell, the warm-up itself is pulling hairs. There's a reason companies like MailChimp, Zapier, et al make so much money.

Facebook was all those things in the beginning.

Reddit was all those things in the beginning.

Twitter was all those things in the beginning.

LinkedIn was all those things in the beginning.

The Internet in general was all those things in the beginning.

I've never used IG/TT but I assume they were all those things in the beginning.

Lemmy will probably be said to be most of those things in the beginning.

With age comes wisdom, which comes once you've seen the pattern happen enough times, which can only come with age.

Sincerely,

One of those old people.

The Y2K38 Epochalypse bug hit 2 years early due to Microsoft's rushed implementation of Windows Subsystem for Linux under CEO Elon Musk, causing all newer systems running Windows to combust due to a combination of the bug, and a cyberattack on Musk's new chip fab plant in the state of Mexas. The only widespread choices after that are WacOS and Ubuntrue, both parent companies owned by Elon Musk after winning in his presidential prelection in 2026 and removing all antitrust legislation. However there is a hobbyist Unix distribution still being passed around called Briarch that fixed the 2038 problem in 2025 when development started, but you have to be in close proximity to someone with it to get it, which is easy in the country of California but not as easy east of the Nutah border, you really have to trust someone to even ask if they have it.

I didn't agree with their decision at all at the time, but now that I realize they made it a little while after it gained widespread adoption and people stopped using it because "Signal isn't actually secure!" ... seems like people were expecting a secure messenger to be, well, secure. So they would chat about anything and everything thinking "I am using a secure messenger, these messages can't be read..." and tech ignorance is a dangerous thing if you're trying to be secure. I would've preferred a colored window and un-closable message for SMS chats, but oh well. I like that they've introduced usernames so you don't have to give out your real number.

What is this, an election for blobfish?

Year of the Linux Desktop! 1999-2035!

I do the same, but I have been trying to build the habit of not doing it.

At that point will you admit I'm right?

Nix this part and you're good, chief.

I have seen a caching (I believe) issue on an nginx/Express service where the POST payload was valid but much larger than normally expected, and it returned all of the companies customer's orders in the queue instead of only ours. On refresh, it was fine. It never did get fixed as far as I know as they had trouble reproducing it even though I provided video and steps multiple times. I wasn't able to produce a PoC script because it was linked to the order/payment process, and wouldn't go through twice without payment. I don't know for sure it was a caching issue in the end, but the similarity should be noted.

Very interesting, did it only last one page load?

You're on a different instance... can you describe what happened when it happened to you?