The list of historians, scholars, jurists, states, human rights organizations, who affirm that undoubtedly at #Gaza a #GENOCIDIO is taking place, is very long. #Israele is naked, nailed forever to its responsibilities, it will have to compensate the victims. https://x.com/ExtraLabel/status/1872564363682570637
"Noch nie in der Geschichte des Automobil ist ein Verbrenner nicht gestartet weil dem Akku zu kalt war." - R34lB0rg
R34lB0rg is a tech-savvy Palestinian at heart, ranting against systemd and advocating for Palestinian rights.
They've been vocal about geopolitical issues, tech rants, and even shared a DIY science experiment.
The community appreciates their contributions and often tags them in posts for support or recognition.
Materials: - Microwave oven (standard frequency is about 2.45 GHz) - A piece of food that melts or changes color distinctly when heated (e.g., dough, chocolate, or marshmallows) - Ruler or tape measure
Steps:
Preparation:
Cooking:
Observation:
Measurement:
Calculation:
Important Notes:
Precision: This method provides an educational approximation rather than precise scientific measurement. The speed of light in air is slightly less than in a vacuum, and the exact frequency of your microwave might vary slightly.
Safety: Never run the microwave with nothing inside or for too long without monitoring. Use caution with hot food.
Variability: The pattern can vary due to the uneven heating in microwaves, the shape of the food, or the specific design of the microwave, so multiple measurements might give you a better average.
This experiment is a fantastic way to teach about wave physics, the nature of electromagnetic radiation, and how fundamental constants like the speed of light can be explored in everyday contexts. It also demonstrates the principle behind Fizeau's experiment but adapted to a home environment.
Evidence of #WarCrimes and #Genocide Exhibit #735282 /cc @archivegenocide @CIJ_ICJ @IntlCrimCourt https://x.com/owenjonesjourno/status/1872333846651511150
يسعدني أن أعلن أنني أصبحت فلسطينيًا بالكامل وأنني أنتقل إلى مسكني الجديد...
https://farid.ps/ https://x.com/R34lB0rg/status/1872506947452473404/photo/1
I am proud to announce that I've gone fully Palestinian and that I am moving into my new residence...
يسعدني أن أعلن أنني أصبحت فلسطينيًا بالكامل وأنني أنتقل إلى مسكني الجديد
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.