Excuse me, it's amateur mathematician to you.
Ah, right, it's nonstandard markdown. According to Jerboa's issue tracker, missing spoiler block rendering was reported in June of 2023 and solved a few days later. ~~Is it possible that you're using an outdated version, or that you have to enable nonstandard markdown in the settings?~~ Scratch that, I just checked and confirmed that it is still an issue. If you can, you should open an issue on Jerboa's github.
I'm using the standard Lemmy web UI (version 0.19.3 hosted by LW) on a desktop browser. I've just checked Alexandrite, Photon, Voyager, and the old.reddit-style UI, and they all work fine.
Hope she likes reading -----BEGIN PGP MESSAGE-----
...or even just consistency in their immorality.
nah my dude, we didn't (:
I inherited my predecessor's fuck-ups that are slowly revealing themselves
You mean I could lose even more data when it inevitably craps out?
(don't mind me, I'm dealing with a failed RAID5 array with one disk dead and one dying, I need to vent)
Another one from Saxony.
A man drives his car to the junkyard, looking for replacement parts. He greets the owner and asks:
"Windshield wiper for a Trabant?"
The junkyard owner thinks for a moment, then replies:
"Sure, sounds like a fair exchange."
corpoposting
I think it would be best to define those terms. I have a vague idea of what "corpoposting" means, but rules should be concrete and subject to as little interpretation as possible.
If you want to keep the neat list format, you could use :::spoiler tags to create rollouts that contain a detailed description. For example:
Avoid corpoposting.
Avoid subjects that glorify the excessive exploitation of people or resources.
Bigotry is not allowed.
This includes (but is not limited to):
- Discrimination based on gender identity or preference (homophobia, transphobia, etc);
- Discrimination based on race, ethnicity, nationality, language, or religion;
- Discrimination based on a person's physical or mental capabilities, or of differently-abled people.
In the early 80s, American scientists and engineers produced the smallest precision drill bit ever created. With great pride and fanfare, they sent it to their West German colleagues for study and reproduction.
Just days later, the engineering team received a parcel. In it, a note: "Thank you for letting us test our equipment" and the original drill bit with a hole drilled through its center.
I can't believe you forgot to mention the worst offender.
Packaging.
For some reason, Linux insists on the asinine practice of hypercentralisation where you're only allowed to install programs from a single approved website. The rest of us are living in 2025 but Linuxists seem to be stuck in 1984. It is literally baked into the system (with a healthy dose of trademark infringement (I mean, Pacman? Seriously?)). Besides the obvious restrictions on user freedom, it would only take one bad actor to call into question the safety of the whole walled garden. Trust is the user's prerogative. A truly open ecosystem would let the user decide whether to get their software from Microsoft, from a third-party Russian website, the seven seas, from a lost-and-found USB stick, whatever.
(also, I don't want to be That Guy, but not having a large language model baked into the kernel for optimal performance in 2025 is fucking stupid)
For context: https://sh.itjust.works/post/29595487 https://lemm.ee/post/50197116
(actual life-ruining gambling is okay though, as long as you give the slot machine a thematic paint job)
Original: https://files.catbox.moe/ouf9k7.png Alt tonemapping: https://files.catbox.moe/g7mg0q.png
Made in Blender.
Original (full story in German): https://feddit.org/post/5322260
Derailment during a shunting operation, caused by the driver's negligence.
This place needs better memes.
Explanation
In the Wayland protocol development process, an authorized representative of a large project has the power to issue a NACK (negative acknowledgement) if they think that a protocol or its implementation is harmful to the Wayland project, which essentially kills that protocol, or at least its current implementation. GNOME has been very actively NACKing protocols that they don't find useful (even if they would be for other compositors). It got to the point where the entire ACK/NACK process was restructured to prevent such abuse.
This is a simple shader node group that breaks up the visual repetition of tiled textures. It uses a Voronoi texture's cell colors to apply a random translation and/or rotation to an image texture's vector input to produce an irregular pattern.
I primarily made it for landscape materials. The cells' borders are still sharp, so certain materials, like bricks, wood, or fabric, will not look good.
Explanation: https://en.wikipedia.org/wiki/Charon_(moon)#Name
view more: next ›
"Here's $20M, keep the change."