reply with features and bug fixes you'd like to see in Philthy, the lemmy fork that runs on this instance. no guarantees I'll get to any of them soon, but particularly low-hanging fruit and well-liked features can be prioritized.

the awful.systems server cluster runs on an open infrastructure based on NixOS and Nix flakes, and though it desperately needs cleanup in some places, it's still a pretty good example of how to use a Nix flake to deploy NixOS in production. feel free to browse the repo and ask any questions about how it works, or about Nix in general!

also, if I get hit by a bus, this can be used to redeploy awful.systems elsewhere. an existing admin who isn't in the hospital or the grave can import a database backup and get back up and running!

and as always, contributions are welcome.

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

we’re seeing a bit of spam come in from lemmy.world. if you happen to see any (and a lot of it seems to be in DMs), make sure to flag it. that’ll let both us and the originating instance’s mods know. if we get a bunch of reports and it seems like lemmy.world isn’t cleaning things up properly, we’ll take further steps to limit the amount of spam we get

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)

this one should hopefully fix the remaining token issues folks have been having, though I'm not seeing anything in the commit log about fixes for the other session and pagination issues we've noticed. as always, let me know if anything looks broken. I'm still working on getting Photon deployed, which might be a good workaround for the frontend breakages we've been seeing.