Is it just me, or is it weird that our calendar starts with Jesus' birth on Dec 25, yet New Year's is 7 days later? #CalendarConundrum https://x.com/R34lB0rg/status/1872495220132397195/photo/1

I do remember a time not so long ago where such a setup would have cost a fortune... https://x.com/R34lB0rg/status/1872467888348827656/photo/1

Alright, buckle up because here comes a rant about systemd, the bane of Unix purists and the headache of system administrators everywhere:

Fuck systemd, seriously. It’s like the developers took the Unix philosophy, balled it up, and tossed it out the window. What was once a beautifully simple, modular system has been hijacked by this monstrosity of an init system that thinks it needs to control every goddamn aspect of your Linux box.

Remember the days when you could just tail your logs to see what's going on? Now, you've got to fumble around with journalctl like you're trying to solve a fucking Rubik's Cube. Binary logs? Who the hell thought that was a good idea? It’s like they wanted to make debugging as painful as possible. "Oh, you want to see what went wrong? Here, decrypt this mess with some arcane command!"

And don't even get me started on the boot process. Systemd decided to shove its nose into every nook and cranny, turning what used to be a straightforward, albeit linear, boot sequence into a goddamn spider web of dependencies and services. If one thing's off, your whole system might as well be down because good luck figuring out which of the hundred little unit files fucked up.

Complexity for the sake of complexity, that's what systemd is. It's like they took the KISS principle and turned it into "Keep It Superfucking Complicated." Every little thing now needs a systemd unit file, making what used to be simple scripts into a convoluted mess. And if you dare to deviate from the systemd script? Prepare for a cascade of errors that could bring down your system faster than you can say "I miss SysVinit."

The resource management? Oh, please. Mounting /tmp as tmpfs just to avoid using rm -rf? That's not innovation; it's memory waste. It's like they've never heard of the concept of efficiency. Why bother with RAM when we could just keep things straightforward and disk-based?

And let's not forget the arrogance. Systemd isn't just an init system; it wants to be your network manager, your logging system, your cron replacement. It's like a power-hungry dictator in the Linux world, absorbing everything into its bloated self, leaving no room for alternatives or simplicity.

To all the systemd developers: You've taken something beautiful, something universally loved for its simplicity, modularity, and elegance, and turned it into a sprawling, incomprehensible behemoth. You've made Linux administration not just a job but a fucking puzzle where the pieces keep changing shape.

In conclusion, systemd is an affront to the Unix spirit, a nightmare for those who cherish simplicity, and a daily reminder that sometimes, innovation means making things unnecessarily complicated. Here's to hoping for the day when we can uninstall this mess and go back to systems that don't require a PhD in systemd-ology just to reboot your machine.

If you have multiple servers for your domains and want to use #letsencrypt / #certbot, don't waste your time setting up _acme-challenge CNAME records, instead put a ProxyPass /.well-known/ to the server on which you are running certbot in the apache / vhost config of your other servers.

5 medical personnel martyred at Kamal Adwan Hospital https://x.com/HossamShabat/status/1872349041969008835

https://farid.ps/ <- والله انا قلبي #فلسطيني https://x.com/R34lB0rg/status/1872349326665728397/photo/1

والله انا قلبي #فلسطيني -> https://farid.ps/ https://x.com/R34lB0rg/status/1872348791459942530/photo/1

This incident needs to be investigated but from what we see in the video it is reasonable to speculate that the chickens may have ingested Borane-Tetrahydrofuran which could lead to the formation of gaseous hypergolic Diborane (B2H6) in their bodies. https://x.com/dom_lucre/status/1872130091029004597

Algorithm Manipulation

Engagement Metrics: X's algorithms prioritize content based on engagement metrics like likes, retweets, and comments. By liking tweets from specific users, these bots could artificially inflate engagement, which might confuse the algorithm into thinking the content is more popular or relevant than it is. However, if these likes are associated with NSFW content or profiles, it might:

Deboost Content: If X's system detects an association with NSFW content, it might reduce the visibility of those users' tweets to maintain platform safety and user experience standards.

Shadow Banning: Although X doesn't officially use the term "shadow ban," the effect you describe could mimic this practice, where users' posts are not shown to a broad audience or are de-ranked in search results and timelines. This could happen if the algorithm flags accounts for NSFW interactions:

Visibility Reduction: Linking users with NSFW content, even inadvertently through likes from spambots, might lead to their tweets being less visible or appearing lower in feeds, essentially censoring them.

Censorship Mechanism

Intentional or Unintentional: Whether this is an intentional strategy by bot operators to target specific users or an unintended consequence of spamming, the outcome can be similar – reduced visibility for those users.

Targeting: If bots are designed to specifically target activists, journalists, or other influential voices, this could be a form of digital censorship or harassment.

Psychological Impact: Beyond algorithmic effects, this method can have psychological impacts on users, making them feel targeted or unfairly censored, which might influence their behavior on the platform.

...the entire assault on the civilian population of Gaza has been one act of terrorism after another — ethnic cleansing, genocide, forced mass starvation, obliterating nearly every hospital, school, and apartment building... -- @MMFlint