self @ self @awful.systems

Posts

99

Comments

2,012

Joined

2 yr. ago

Moderating

---

froztbyte’s criticism crossed the line by a bit for a couple of admins who weighed in, and they’ve been warned to ease up. reporting a post like that isn’t bannable; we’ve got more context for a report like that than we do for some rando doing a drive-by report for a tone rule that doesn’t exist, for example.

blue misused the report system in a way that wasn’t accidental or incidental, and we felt the best course of action was a cooling off period. given that they’re welcome back in less than 4 days, I’d prefer to leave it at that.

the public modlog, linked from the instance sidebar:

lightly used thinkpads are the classic choice for this — IT departments buy high spec ones then dump them for cheap a few years later in surplus sales or on eBay, and there are usually repair manuals and spare parts readily available. usually you can type the specific model and generation into a search and get a wiki page or at least a couple blog posts reporting how well they’re supported under linux, and Lenovo seems to intentionally do very well on compatibility since Linux compatibility is a nice checkbox for an enterprise laptop to have. just be careful you don’t get bamboozled into buying any of Lenovo’s consumer laptops, since they tend to be a fair bit cheaper and don’t have the same compatibility guarantees, repairability, or ample spare parts availability.

you know, I shouldn't be surprised by the extremely toxic lead developer to prompt enthusiast pipeline, but... slopcode in gzDoom of all things? fucking why?

uggggh yep sorry, I meant to deploy some changes that would mitigate this a couple nights ago but had a bunch of things crop up. I’ll do my best to work it in tonight!

some specifics for the changes to expect:

• iocaine finally
• some better nginx settings to kill likely scraper connections faster

today in I fucking called it fedora aka mostly red hat has decided to allow slop code in a way that violates even their utterly mid stated principles around the tech

if you’re downstream from any fedora packages (and I don’t know the scope of this policy so it might be safe to consider anything owned by red hat in general to be tainted — yes I realize most of us are downstream from a bunch of red hat shit) it might be time to evaluate an alternative if available

of course the organization I know primarily for platforming fascists and astroturfing on YouTube was secretly an even worse grift and somehow tied in with Yarvin, why wouldn’t it be

given that Rossmann’s at the head of this thing too, I’m starting to regret not taking GrapheneOS (who, notably, were also a target for this grift) seriously when they said Rossmann’s involved in a bunch of terrible shit. the right to repair deserves a better figurehead.

sometimes crime pizza is fucking fantastic! they just let somebody’s grandpa cook and consider more expensive ingredients an investment in their cover. same idea as Capone’s soup kitchens but much easier to hide money with

well there you have it

bitter winter adult it is

nah sorry about that, the scrapers took the opportunity to knock us offline again so I did a little bit of impromptu maintenance to make us more rugged against the same type of failure in the future

the next work I do around this will be significantly more planned because it’ll be iocaine

what an unpleasant asshat

if you post a thread about intolerable dickheads, the most intolerable dickheads on Lemmy will post some shit like “intolerable dickhead checking in, how fucking dare you”

it’s like catnip for the Reddit-brained, and by catnip I mean meth

like moths to a flame

So long as you keep your bullshit detector well-maintained, check the sources—and actually use an AI that cites it’s sources—I see nothing wrong with them. The tech is still in its infancy; it’ll improve with time.

fuck off asshat

fresh openwashed proprietary license hell just (well as of 2 years ago, but I’m sneering at it now) dropped:

Harmful free-riding is the sort of free-riding that leads to the free-rider problem

[…]

Examples of such goods are public roads or public libraries or services or other goods of a communal nature. Free riders are a problem for common pool resources because they may overuse it by not paying for the good (either directly through fees or tolls or indirectly through taxes).

from the fucking asshats who made Sentry proprietary under the BUSL but wanted an even more nonsensical license:

Sentry started life in 2008 as an unlicensed, 71-line Django plugin. The next year we began publishing it under BSD-3, and ten years later we switched to the Business Source License (BSL or BUSL)

hyprland is not fascist. Ladybird being fascist is IMO very debatable. But on the whole, the idea of having your OS itself tell you not to use software for political reason is not going to work in our favor and, if done in an hyperbolic way like this, it will make the left look really dumb

this charlie kirk saga is teaching me that the left-wing community is roughly just as bad as the right-wing one when it comes to fact-checking and not providing convenient but uncertain possibilities as correct

it’s really weird how this asshole needs us to believe fascists aren’t fascist and keeps going out of his way to talk about how dumb the left is, isn’t it.

for anyone wondering what the rest of the toxicity in the Wayland ecosystem that isn’t hyprland looks like, it’s dickheads like this controlling every conversation and technical decision. if you dig into the accounts this dickhead interacts with, you’ll see plenty of KDE and GNOME profiles clapping along to this shit. Wayland isn’t the way it is by accident.

fsck

cringe

Tangara is an open source project made by a fediverse hardware hacker with contributions from other fediverse personalities. it’s reputedly pretty good, though all the reviews I’ve seen are from other fediverse posters so it may be worth looking at some independent reviews to confirm it’s not just homegrown optimism.

at the risk of going open source reply guy and making a recommendation you can’t follow up on, I’ve had a lot of success with Jellyfin as a media library/local streaming host and the beta version of Jellyfin as an app that lets me stream FLACs on my local network and seamlessly download them onto my phone. a VPN or a Jellyfin library on a VPS can let you stream your stuff almost anywhere in much higher quality than Spotify.

I don’t own a Tangara though I do want one, and I’m fairly sure they don’t support the Jellyfin API yet, but if you end up missing a more Spotify-style listening experience then it might be worth inquiring if there’s any Jellyfin client projects in progress.

I collected some mastodon links so you know roughly what to look for:

• here’s a game developer unable to do window positioning, multi-monitor, display type detection, hi-DPI… in portable ways on Wayland. window positioning in particular bites game developers hard, and is still unfixed for, gonna be honest, horseshit security reasons.
• this entire thread is kind of an excellent summary
• screen recording on Wayland sucks, and what’s interesting about that thread is the smug person replying gets it (to my memory) wrong, portals for screen recording are a hack
• in fact here’s the post where Ariadne told me I was wrong about portals; it’s also a good starting point if you want to see what protocol discussions look like
• here’s one of the jwz threads out of many

in conclusion: how dare I. don’t I know these are just poor, mostly corporate-backed volunteers

for Wayland, the issue is unfortunately outside of the core protocol. the core protocol doesn’t implement everything you need for a functional desktop, and some of the omissions are utterly obvious things. the ecosystem makes up for that with protocol extensions, but some (all?) of the important ones are proprietary to a particular compositor and considered part of its internal API. also, because Wayland has a frankly pretty broken security model (everything is utterly locked down and as far as I can tell no exceptions are possible via permission modals or any other mechanism), some types of applications are only possible via fragile hacks. gnome has many of these proprietary protocols because Wayland is essentially under the same umbrella and so it has a privileged position; KDE is in a close second. every other compositor has severely reduced functionality.

for more details, see jwz’s recent blog posts where he failed to port xscreensaver to Wayland because some of the utterly basic functionality he needed was compositor-specific. the hyprland wiki’s compatibility page is also relevant because all of those problems tend to be rooted in this too, though I of course don’t recommend trusting them as a source. Asahi Linux also has a ton of issues on their github around hyprland that I believe boil down to protocol issues. unfortunately these issues tend to be hidden from public view because they’re spread out across a hundred rants and a hundred discussions in FreeDesktop’s Wayland protocol committee; a properly formatted Mastodon search might also be informative.

(counting down the seconds until some Wayland dev wanders in and tells me I’m completely wrong about everything because an uncharitable reading of one of the paragraphs above reveals I’m wrong about some minor point and besides what am I saying, everyone should be on xlibre? toxic little fucks)

“As a Nixos user myself”: god it makes so much sense that you went from being a NixOS user who loves anduril to spamming up this thread defending DHH. posting his blog here semi-critically won’t save your posts by the way