hello_hello

hello_hello [comrade/them] @hexbear.net 2w ago

CW SA

The comic is ostensibly about date r*pe. The artist usually makes these types of gags but this one is justifiably too close to the actual thing that it acts as a trigger. People seeing this on x the everything app and not knowing the artist and they take it personally.

hello_hello [comrade/them] @hexbear.net 2w ago

Over that 11-day period, they estimated that on average, a sexualized image of a child was produced every 41 seconds.

Every 60 seconds on X, the everything app, a minute passes. Also child abuse material, but we already knew that.

hello_hello [comrade/them] @hexbear.net 2w ago

We choose humanity, we choose collective power.

Just put the security updates into Firefox, come on man. Ain't nobody need you for anything.

Now where the hell is my split view? I like the vertical tabs, but give me my split view.

hello_hello [comrade/them] @hexbear.net 2w ago

Another Poettering W

8

hello_hello [comrade/them] @hexbear.net 2w ago

What they'll do is arrest someone on bogus charges and then get their phone (legally via a plea or illegally whatever works). Since signal links your account with a phone number they can cross reference the contacts sync with the signal profiles and work their way up that way.

Best thing to mitigate this is to use a communications app that doesnt link to any personal details like SimpleX or GNU Jami, that way if one person gets booked then the entire network can be more resilient.

Signal is an upgrade from SMS but the phone number linking makes it impossible to create disposable identities. Signal is what you use outside of organizing talking to colleagues and family because WhatsApp is a slop mess and its fairly well known that you have an easier chance on getting people on board.

5

hello_hello [comrade/them] @hexbear.net 2w ago

https://www.youtube.com/watch?v=Nzb3dqRaN_8

hello_hello [comrade/them] @hexbear.net 2w ago

+1 on using guix on a foreign distribution. It gives you some flexibility in how to set up software. For example, I'm on an asahi macbook so a lot of ARM platform packages on the default CI server haven't been compiled or there isn't support yet (for example openjdk on arm has no substitutes).

In those cases you can then decide to either package a binary release of said software or use containers, and if both of those don't work then install distro packages systemwide.

1

hello_hello [comrade/them] @hexbear.net 2w ago

The adobe Photoshop installer parses data in XML but it turns out that the XML it reads is malformed. Wine correctly rejects this malformed XML in its counterpart to the windows XML reader but windows will actually just ignore the invalid XML and thus the installer still works on windows.

Turns out the software from a billion dollar company couldn't be run on Linux because of bad code on adobe's end. One must wonder if this was intentional on adobes part to rely on undefined behavior to fuck over anyone trying to use their software outside of what porky wants.

Anyway we have Photoshop on GNU/Linux so the excuses for hesitating on using Linux are shrinking, 2026 year of the Photoshop on Linux desktop.

hello_hello [comrade/them] @hexbear.net 2w ago

The guix manual is a good starting point. SystemCrafters has articles on guix and guile but they're more like blogs and can be outdated. Guix cookbook has some good examples to check out.

Guix source code is also a good way to learn, since most everything is written in self describing lisp you can learn by example. Theres a lot more rough patches in guix than what you'd get with nixos ootb, I'd recommend looking into universal blue first and then augmenting that with guix if you can.

hello_hello [comrade/them] @hexbear.net 2w ago

Works on LLM grooming but is in a band suggestively named after a underage girl who was a victim of bullying.

Never change potterheads.

hello_hello [comrade/them] @hexbear.net 2w ago

Overstreet murders btrfs devs, declaring their filesystem unfit for human consumption. Only bcachefs gives you the right amount of nutrients and carbs for a balanced diet.

1

hello_hello [comrade/them] @hexbear.net 2w ago

Rust on Linux has left the experimental stage and is in the kernel proper but it was a bumpy ride. Hector Marcan (former asahi project leader) had to retire from the project because there were dipshits nacking their patches after multiple reviews. Not to mention the other rust for Linux person who resigned due to nontechnical nonsense.

Not to mention that abusive and inflammatory language was and still is tolerated in the mailing list. Tbh Overstreet just seems to be a product of the chud hacker culture that should be purged entirely.

3

hello_hello [comrade/them] @hexbear.net 2w ago

He also most likely ruined it for everyone else since now the Linux kernel maintainers are going to be less willing to sponsor up and coming projects.

Literally one of the worst human beings to be around.

2

hello_hello [comrade/them] @hexbear.net 2w ago

I never got into bcachefs because it was so much a bus factor of 1 project all reliant on Overstreet. Its so funny to see him lose his entire life's work in the kernel by just intentionally pissing off everyone.

Pretty sure the guy is also a neo-nazi, it would be incredibly surprising if he wasn't. No well adjusted person would act this way over a filesystem.

hello_hello [comrade/them] @hexbear.net 2w ago

Docker was so successful that rent seeking profit extraction is too difficult to do, now we installed oracle alum as a CEO to do rent seeking.

Death to capitalism.

hello_hello [comrade/them] @hexbear.net 2w ago

Here we go again (channeling the inner Matthias Clasen, one of the lead engineers in GTK)

Many apps handle CSD poorly.

Fix the apps that don't support Linux. There is a difference between porting to GNU/Linux and actual support. Hire formal engineers (not enthusiasts burning the midnight oil) to port to freedesktop and wayland or accept contributions/improve tooling.

libdecor is the worst of both worlds because you get the space inefficiency and lack of integration of a traditional titlebar, with all the inconsistency and lack of user customization of an integrated titlebar.

Agree, apps and toolkits should implement their own libdecor. Libdecor was a stopgap measure for porting applications, but it's not an end all solution.

Supporting SSD would solve this

No, as the compositor cannot make decisions for the app's window bar and thus will choose the least common denominator approach (that being, libdecor). This is what KDE does, it's KDE's decision, but it cannot be everyone's decision.

The issue with doing that on linux is that the design of the titlebar can vary so wildy depending on the environment that having CSD’s that “feel native” is a bit of a losing battle. Offering the option of SSD for non-GNOME apps on GNOME and vice versa would go a long way to making applications feel more native for users that value that sort of thing.

This did not explain why this would be the case. An app's "look and feel" is much more than the titlebar. Padding, font, colors, widget design, animations, sound, etc all play into it. Even the way the settings menu is presented varies differently from app to app, from desktop to desktop.

A lot of users on other desktops are frustrated by GNOME apps not supporting SSD, breaking if SSD is force-enabled.

GNOME applications use the adwaita platform toolkit which explicitly does not want the compositor to force window decorations on it as the window bar of these apps are a design feature. GNOME applications look like GNOME applications, this is intentional. As far as I know there isn't a toolkit that is so similar to adwaita that forcing a different titlebar wouldn't disrupt the application.

GNOME apps optionally supporting SSD would make many users of other desktops very happy indeed.

Customer is always right mindset is not the deciding factor in technical decisions.

This fragmentation only makes the linux desktop less attractive to developers and, importantly, makes application developers less likely to adopt more modern standards such as wayland.

App developers do not have a choice in adopting wayland. Legacy xserver will disappear in only a few years from distributions and xwayland is a stopgap measure. There is no fragmentation, CSD has always been part of wayland and will always be a part of it.

However, wayland was also initally designed without screenshare or global keybinds, standards that GNOME had since adopted.

This is not part of wayland it is part of xdg-desktop-portals which is an abstraction separate from wayland (but used in wayland-based desktops to access desktop resources).

The real problem is the idea that GNOME project shouldn’t cater to the first group. It would be like GNOME not supporting xdg-file-chooser and saying that each app should ship their own file picker. But GNOME does support it, and only apps that wish to implement their own file picker do so.

Ditto with top, this is part of the portal spec but also that some GNOME engineers in passing have mentioned that they don't actually want apps to make the file picker portal the de-jure implementation of file picker, if the app has its own way of doing file picker that's more suited to it than it should use that.

In this scenario, the GNOME app would remove the integrated window title and controls.

Deeply unserious.

GNOME’s lack of support for server side decorations is the single biggest issue with the GNOME desktop environment right now,

If a fake protocol designed to ape proprietary systems that doesn't actually work both in theory and practice is the largest "issue" of GNOME then I would say GNOME has done pretty well.

Anyway article was written in 2022 so L bozo author GNOME will hold the line on Client-side'ist thought.