self

joined 2 years ago
MODERATOR OF
[–] self@awful.systems 56 points 2 weeks ago (9 children)

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

[–] self@awful.systems 20 points 2 weeks ago (4 children)

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

[–] self@awful.systems 8 points 3 weeks ago (4 children)

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)

[–] self@awful.systems 11 points 3 weeks ago

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.

[–] self@awful.systems 8 points 3 weeks ago
[–] self@awful.systems 7 points 3 weeks ago (2 children)

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.

[–] self@awful.systems 9 points 3 weeks ago (1 children)

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

[–] self@awful.systems 8 points 3 weeks ago (1 children)

this is exactly how I look

yes I transform into a car

[–] self@awful.systems 10 points 3 weeks ago (2 children)

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)

[–] self@awful.systems 7 points 3 weeks ago

“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

[–] self@awful.systems 6 points 3 weeks ago

ahaha yeah linking DHH’s fash shit here sure showed us

[–] self@awful.systems 6 points 3 weeks ago (3 children)

vice signal somewhere else dickheads

 

the r/SneerClub archive at awful.systems is welcoming contributors. it's a statically-generated site (from this set of archived posts in JSON format) that uses a unique, high-performance Nix-based static site generation system. the current site desperately needs a new stylesheet (especially on mobile), but one area where I really need advice or contributions is the dataset.

currently, the SneerClub archives only pull in data from the bdfr set, which I generated using Bulk Downloader for Reddit right before Reddit killed its API, but I'd love to merge the SneerClub_comments.jsonl and SneerClub_submissions.jsonl files into the data we're using to generate the site, since those have older data from ArchiveTeam. unfortunately, that data set is in a complete different format from the BDFR data. any advice for tools or techniques to merge those two data sets into one (or offers to contribute a merge script) is greatly appreciated.

 

the software we use to run awful.systems, which @dgerard@awful.systems suggested I call Philthy (and I agreed!), is seeking contributors.

like upstream Lemmy, this consists of a Rust backend and a Typescript+React frontend. contributions to both are welcome; use this thread to discuss ideas and collaborate.

here's some contribution ideas off the top of my head (but all reasonable contributions are welcome):

  • (frontend & backend) actually rebrand to Philthy, to prevent confusion between us and upstream Lemmy
  • (frontend & backend) rewrite README.md to emphasize that this is a fork
  • (frontend) make the page header and footer more configurable; remove various links that aren't relevant to awful.systems
  • (backend) delete posts from Mastodon when they're deleted on our end
  • (frontend & backend) implement The Firehose, a big admin-only list of the posts and content leaving our instance
  • (frontend & backend, ongoing) merge in changes from upstream Lemmy if there are features you wish our instance had

or make suggestions in this thread!

one major blocker preventing folks from contributing to Lemmy-related development I've seen is that a lot of people don't know Rust. if that's the case, I can offer the following:

  • the Lemmy codebase is the worst possible place to learn Rust, but I'd love to start a thread for Rust tutorials and shared learning. it's honestly an excellent language in its own right, so I'd love to teach folks about it even if they don't end up contributing to Philthy.
  • if you're good with React and/or Typescript and the feature you want to implement has a backend component, I don't mind handling the backend portion if I'm able.
 

this is a non-toxic place to collaborate on projects (programming, design, art, or otherwise) and share information; effectively, it's the awful.systems answer to Hacker News. this community has been in the planning phase for a long time, but the xz backdoor recently emphasized how severe the toxicity problem in existing open source communities is, and how important it is that we have a place to collaborate that isn't controlled by toxic personalities or corporate interests.

FreeAssembly is starting its existence as a Lemmy community that enables collaboration on externally-hosted projects, but that doesn't necessarily need to be its final form. as we figure out the needs of this community, we can grow to service needs like code hosting and design collaboration. for now, we recommend hosting code on software forges like Codeberg (and we recommend avoiding github if possible, though it's well-understood that this isn't easy for established projects). we also want to explore the best options for designers and artists to collaborate without making them dependent on large corporate infrastructure.

there are some expectations around posting to FreeAssembly. see the sidebar for details.

 

(via https://hachyderm.io/@jbcrawford/112202942593125987, archive: https://archive.is/VnqRZ)

surprise, Amazon’s godawful surveillance grocery stores were just exploiting hidden labor and calling it innovation, and even that was too expensive

even worse, the few times I’ve seen one of these fucking things in the wild, it still had 1-2 employees hovering near the entrance to make sure nobody did the utterly obvious (fuck with the payment system and get free shit), a job that’s also known as a fucking cashier, but with much worse pay, much harder labor (physically stopping shoplifters), and no counter to lean on or opportunity to even sit down

 

Amaranth is a simple-but-expressive hardware description language (the type of language you use to define integrated circuits for FPGAs, ASICs, and similar hardware) implemented as a Python DSL. I'm not the biggest Python fan, but Amaranth is worth it -- even though it's in heavy development and its documentation is incomplete, it's by far the most comprehensible HDL I've ever used, and I've tried many of them.

its documentation is incomplete since the language is under heavy development, but its language guide is still the best gentle introduction to HDL concepts I've read, and its tutorials are written for an older version of the language (sometimes called nMigen) but are still excellent -- in particular, Robert Baruch's tutorials combine design fundamentals with formal verification (which itself is usually considered an advanced technique, but Amaranth streamlines it), and the Vivonomicon RISC-V tutorials are worth a read too

 

You could get a robot limb for your blown-off limb

Later on the same technology could automate your gig, as awesome as it is

Wait, it gets awful: you could split a atom willy-nilly

If it's energy that can be used for killing, then it will be

It's not about a better knife, it's chemistry and genocide

And medicine for tempering the heck in a projector light

Landmines, Agent Orange, leaded gas, cigarettes

Cameras in your favorite corners, plastic in the wilderness

We can not be trusted with the stuff that we come up with

The machinery could eat us, we just really love our buttons, um

Technology, focus on the other shit

3D-printed body parts, dehydrated onion dip

You can buy a Jet Ski from a cell phone on a jumbo jet

T-E-C-H-N-O-L-O-G-Y, it's the ultimate

the subject matter of Aesop Rock's latest album felt relevant to our instance's interests

 

(here’s a Verge article about the Waymo car getting burned during a Chinese New Year celebration)

a self-driving car got destroyed (to a round of applause from the crowd) in San Francisco! will the robot car fans on the orange site take this opportunity to explore why the tech seems to be extremely unpopular among the populations of the cities where it’s deployed?

of course the fuck not, time to spin the wheel of racist dog whistles and see which one we land on! a note to the roving orange site fans (hi, fuck off), these replies are either heavily upvoted or have broad agreement in the thread (or I’m posting them here cause I want to laugh at some stupid shit, you don’t dictate the terms of my enjoyment)

This isn't a revolt against AI. SF attracts anarchist mobs and they'll vandalize buses, trains, police cars, bikes, whatever is around.

we’re off to a strong start with some bullshit straight from musk’s twitter (which he stole from the fever dreams of the conservatives on his platform)

Alternatively: this is San Francisco where on a good day the locals don’t need much excuse to set fire to a car (although I usually associate it with the Giants winning a World Series) and this poor dumb stupid driverless Waymo drove into a celebratory and by the looks of it somewhat drunken crowd on the Streets of Chinatown during the Chinese New Year where in following its prime directive to do no harm, it got itself stuck up the creek without a paddle so to speak. Waymo probably should have accounted for that ahead of time and told their cars not to go near Chinatown this evening.

remember that no matter what, the robot car is the victim here. there’s no chance Waymo was doing anything dangerous or assholeish in the area; much like robocop, the car is an innocent victim of its fucking prime directives??? and you wouldn’t set fire to robocop, would you?

This is a hilarious take. A few youths went bonkers and defaced private property. Has nothing to do with philosophical beliefs or a Big Tech agenda. You should debate the finer points of the Big Tech agenda with them while they run up to you in a maddened rage.

yeah! I can’t wait until these angry mobs set fire to your robot car body! then you’ll see!

Arguments about driverless cars aside, the youth in this country are seriously lost. It only takes one generation of poor parenting and poor civic policies to ruin a culture.

this one is downvoted, but this reply isn’t:

Sounds like they were right. The youth at that point was lost, and are now raising people who will literally burn down a waymo for fun, or because of some horrifically ignorant idea about fairness.

oh you poor woke kids don’t like when shitty dangerous robot cars are on the streets? are you gonna start crying about how it’s “unfair” they’re covering up pedestrian injuries and traffic accidents now? your grandpa would never stand for this

 

(via mastodon)

 

remember, regardless of how outspoken you are in life, nothing will stop the capitalists from reanimating your defiled corpse into a shitheaded centrist zombie if there’s a buck in it:

“I'd just like to say that as much as I think billionaires are destroying the fabric of society with unchecked greed and blatant self-interest at the expense of basic human rights for everyone else, it is a little strange to me that people get mad at them. People are the ones who gave them the money in the first place," the AI Carlin said.

(editor’s note: the above is supposed to be a joke from the comedy special these fucking assholes hijacked Carlin’s corpse to promote. I can’t find the punchline, but it’s supposed to be a joke)

 

we had a previous thread on this thing way back when TechTakes moved here, but it deserves a Buttcoin thread too. observe, for your enjoyment(???), an even worse derivative of the reputedly most worthless W3C standard. when you’ve got nothing of value to write about but you need a spec to be taken seriously so you write stuff like this:

The purpose of DIDComm Messaging is to provide a secure, private communication methodology built atop the decentralized design of DIDs.

It is the second half of this sentence, not the first, that makes DIDComm interesting. “Methodology” implies more than just a mechanism for individual messages, or even for a sequence of them. DIDComm Messaging defines how messages compose into the larger primitive of application-level protocols and workflows, while seamlessly retaining trust. “Built atop … DIDs” emphasizes DIDComm’s connection to the larger decentralized identity movement, with its many attendent virtues.

(that typo in the second paragraph of the spec has been there for at least 6 months, cause if anyone went back to proofread this crap they’d probably delete all of it out of embarrassment)

DIDcomm is what happens when crypto folks get invited to join your standards org, and it does to the spec writing process what crypto and AI did to whitepapers: it’s all extreme filler to mask the lack of an idea, built on top of a spec that famously specifies nothing

 

this is pretty cool. it’s a tutorial with interactive exercises that explores the Nix language as a general-purpose functional programming language, outside of its role as the configuration and package definition language for NixOS. understanding Nix better as a language makes more complicated packages easier to write (and is necessary to understand the guts of nixpkgs and the parts of Nix written in itself), but it also has a number of unique advantages as a programming language within a very specific domain.

 

this has all my favorite grifts in one! crypto, AI, and the one where you re-scam the victims of your other scam by pretending to be the cops!

view more: ‹ prev next ›