self

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.

(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!

to help kick off the new federated home of sneering at crypto and meme stocks, enjoy a mask off look at what these fucking fools intend to do to the nocoiners if they’re ever given an ounce of actual geopolitical power