b

🔒 Manual approval
View original page

@b@mrrp.place · Joined ⁨Sep⁩ ⁨2025⁩

mrrraow !!!!
trans woman girlthing, kbity, hacker, musician
i make things with computers and synthesizers and guitars and solder

neurodivergent, disabled (hEDS, POTS, chronic fatigue, also vestibular migraines now???)
i wear an n95 everywhere because covid is not over

Palestine will be free 🇵🇸

i only post/boost things with alt text, or an image description provided by someone (often me) in the replies

https://justmytoots.com/@b@mrrp.place

pronouns
she/it
species
cat
adult?
yes
location
portland, or

Replying to @⁨liaizon@wake.st⁩

@liaizon no, for many reasons:

  • i don't have the free time to do that. i have a full-time job and way too many projects already, activism-related and otherwise
  • i'm not seeing any info from them on how to get involved with their projects, or any indication they want help
  • i'm not sure how productive working with them would be given they seem pretty enthusiastic about AI
  • i don't think something written in large part by an LLM could be saved, i think it would need to be rewritten

also, yes I know others are using AI, but that doesn't make it ok for them to! especially since they're supposed to be a radical leftist organization and AI use greatly conflicts with their stated values!
and i would be much more confident in the security of vibe-coded software with hundreds of thousands of users and a large developer community than vibe-coded software with one user/developer

brief PSA: there's a good chance you've seen sabot media's "become the thousand servers" guide being boosted around fedi recently, as well as their posts about autistici/inventati. unfortunately, sabot media are heavy users of AI and it seems likely that the guide was written at least in part by an LLM.[1] in addition, they're using the guide to recommend their own vibe-coded CMS (called "colophon"), putting it as the first entry under "software options worth comparing" (even before wordpress and ghost).[2] given how LLMs tend to generate incredibly insecure code, their recommendation is deeply irresponsible and could get people hurt.

please disregard sabot media's advice and do not follow their guide.

  1. they have very visibly vibe-coded pages on their site, and the guide has a very similar writing style and a similar interface. happy to elaborate on this if anyone needs ↩︎

  2. i have zero doubt it was produced by an llm; looking at this markdown file in their repo will make it clear to anyone who's familiar with the output of claude code (there's also plenty of claudish, docs talking about the project owner "requesting" things, etc) ↩︎

Black-and-white DIY zine-style poster for Become the Thousand Servers. A large illustrated octopus rises behind several server racks, with tentacles curling around the machines and cables. A laptop marked with an anarchist “A” sits on top. A ribbon across the servers reads “Each one, teach one.” An astronaut floats below among looping cords, plugs, lightning bolts, radio towers, and transmission symbols. Large text at left reads “Become the Thousand Servers.” The bottom banner gives the URL: sabot.media/guides/become-the-thousand-servers.kolektiva.socialSabot Media (@AberdeenLocal1312@kolektiva.social)Attached: 1 image ITS HERE: BECOME THE THOUSAND SERVERS Autistici/Inventati’s shutdown left a pretty obvious question behind: what happens when infrastructure movements depend on disappears? We spent the last couple weeks turning that question into a practical field course on autonomous movement infrastructure. This is not a guide telling every collective to buy a VPS and become its own ISP. It’s about understanding the systems we already depend on well enough to map them, maintain them, back them up, move them, preserve what matters, and pass that knowledge on. The course has 13 guide sections and 12 practical lessons. You’ll map the dependencies behind a real project, investigate DNS, SSH into a disposable Linux machine, put something online, inspect what you exposed, make and restore a real backup, destroy and rebuild a service, migrate it, stop being the only administrator, preserve published work, troubleshoot a local network, experiment with another networking model, and te