Ana Meisel

@anmeisel
208 Followers
128 Following
50 Posts
||""''✿'""||
||_.♥._||
====== 0
with a luddite heart
Websitehttps://ana.help/
Githubhttps://github.com/anmeisel
Sourcehuthttps://sr.ht/~anmeisel/
Pronounsshe/they

I wanted to work on an are.na replacement and instead I wrote 'goblin.sh', a bash utility for collecting and managing a stash of items (notes, files, or web things).

https://codeberg.org/thgie/goblin.sh

Writing the script made me realize what I liked and disliked about other such tools, and what kind of relationship I actually want with such computing activities.

Much thanks to @anmeisel, who gave a fantastic workshop on the intersection of #Permacomputing, literate programming, and repair manuals. I took 'goblin.sh' with to that event and I was really motivated to rewrite the whole thing and wrap it in a proper README.

Next step, learning Lua!

#Goblin #Bash

goblin.sh

bash utility for collecting, categorizing, and managing a stash of items (notes, files, or web things) in a simple local file structure and database

Codeberg.org

there is no event sign up, so just pop by! the workshop will be held from 11:00–16:00 at unsorted.love on sunday.

all you need to bring is -
* one sample of working code or a creative tech project that makes you feel something...
* a computer capable of running Python 3 (we will use literate programming tools which require this).
* any text or code editor of your choice.
* any additional artistic tools that help you tell its story!

here’s more info about the event: https://www.instagram.com/p/DUQHVkJiJgF/

Younger Sibling on Instagram: "Literary Manuals Coding Workshop Storytelling for the Service and Repair of Code with the London Permacomputing Club 15 February 2026, 11:00–16:00 at unsorted.love Workshop Introduction & Goals
 “Repair, after all, is a social activity.” – Shannon Mattern
 This workshop explores code as a medium for communicating methodology to human readers. Through practices of Literate Programming and explanatory storytelling, we will examine the “repair manual” as a form and the relationships we develop with our functional digital possessions. Participants will look at the history of home-repair manuals and consider the boundaries of traditional code documentation. We will work together through an example piece of code or a digital project and develop a literate manual that explains its theory of operation. Attendees will produce similar resources using whatever literary or artistic methods best clarify their chosen piece, contributing to a collective anthology.

 What Participants Will Be Doing * Discuss the role of code as a communicative tool. * Study examples of manuals and documentation practices. * Create a literate, story-driven explanation of a code sample or digital artefact. * Collaborate in groups and produce materials for a compiled anthology on software repair. 
Practical Requirements
 Participants should bring at least one sample of working code or a creative tech project (their own or someone else’s) to include in the activity. This could be a project you enjoy explaining or something you want to explore more deeply.
The literate programming tools demonstrated will require: * A computer capable of running Python 3 * Any text or code editor of your choice Feel free to bring additional artistic tools if they help you tell the story of your chosen piece—we will assist in integrating these into the final work. 
The workshop will be held in English and is free of charge, funded by Arts Council England - Developing Your Creative Practice Grant. With: Ana Meisel. Ana Meisel is one of the organisers of the London Permacomputing Club, based at SET Social in Peckham, UK. #permacomputing #coding"

136 likes, 1 comments - younger_sibling__ on February 2, 2026: "Literary Manuals Coding Workshop Storytelling for the Service and Repair of Code with the London Permacomputing Club 15 February 2026, 11:00–16:00 at unsorted.love Workshop Introduction & Goals
 “Repair, after all, is a social activity.” – Shannon Mattern
 This workshop explores code as a medium for communicating methodology to human readers. Through practices of Literate Programming and explanatory storytelling, we will examine the “repair manual” as a form and the relationships we develop with our functional digital possessions. Participants will look at the history of home-repair manuals and consider the boundaries of traditional code documentation. We will work together through an example piece of code or a digital project and develop a literate manual that explains its theory of operation. Attendees will produce similar resources using whatever literary or artistic methods best clarify their chosen piece, contributing to a collective anthology.

 What Participants Will Be Doing * Discuss the role of code as a communicative tool. * Study examples of manuals and documentation practices. * Create a literate, story-driven explanation of a code sample or digital artefact. * Collaborate in groups and produce materials for a compiled anthology on software repair. 
Practical Requirements
 Participants should bring at least one sample of working code or a creative tech project (their own or someone else’s) to include in the activity. This could be a project you enjoy explaining or something you want to explore more deeply.
The literate programming tools demonstrated will require: * A computer capable of running Python 3 * Any text or code editor of your choice Feel free to bring additional artistic tools if they help you tell the story of your chosen piece—we will assist in integrating these into the final work. 
The workshop will be held in English and is free of charge, funded by Arts Council England - Developing Your Creative Practice Grant. With: Ana Meisel. Ana Meisel is one of the organisers of the London Permacomputing Club, based at SET Social in Peckham, UK. #permacomputing #coding".

Instagram
I'll be doing another iteration (last one 😢) of the literate programming workshop in Zurich on the 15th! At https://unsorted.love <3 come by if you're in the area 🤖
I'm a software developer with 40 years' professional experience, lucky enough to be considering early retirement. I love writing code and don't want to stop. I'm keen to give something back and contribute to one or more open source projects.

The questions are, to what shall I contribute, and how do I get started?

My skills are mainly C++, having spent much of the past decade programmatically dismantling and reassembling Microsoft Office files. I'm quite happy to learn Rust or Go, but don't really like webby front-endy ux stuff.

Any suggestions for a worthy project to which I could contribute? Please boost if you can.

#SoftwareEngineering #SoftwareDevelopment #SoftwareDev #OpenSource #FreeSoftware
@lukasfx @foyglgezang nice to see @praxeology in this! ❤️‍🔥
@tunera this is great <3
trying to get as much info as possible for this mildly niche and recent topic obsession of mine - pls give me any book recommendations for tech history during and post- eastern bloc.. ideally about diy tech, #piracy, folk culture, #self-hosting collectives and laws & regulations around technology use in countries that were aligned with the soviet union ??

UPDATE: Thanks to @doriane we now have a section that quickly summarizes what is permacomputing and *also* a printable PDF zine of the score/guide. 🎉 🖨️

Do you want to start a permacomputing collective?  

In the past months, and with support from @Error417 we have developed a small score/guide/recipe that can hopefully inspire you to get started with this topic.

https://brewing.permacomputing.net

The text of the guide was written by anna andrejew (https://annaandrejew.com), @praxeology and @latentspace based on interviews with @anmeisel (London Permacomputing Club), @archipielago (Middle America Archipiélago I community servers), @colm (Wilderland permacomputing group), @cmos4040 and @decentral1se (rotterdam.permacomputing.net), @praxeology (Berlin Permacomputing Meet Up), @michal (Node9), @sister0 (Autoluminescence Institute), @freebliss (permacomputing Vienna), and Steve McLaughlin (Philly permacomputing + solar punk meetups at @iffybooks hosted together with Dave Slinger).

Copy editing and advice by @l03s and myself. Design for the dedicated website and PDF by @doriane with illustrations from @raquelmeyers

#permacomputing #community #collective #organisation

"too dirty to be trained" · Make your data too dirty for '#AI'. Can we opt out from being trained by becoming unqualified? @jwn

👉🏻 https://too-dirty-to-be-trained.net

in ljubljana this weekend at osmo/za for some more #permacomputing !! join us to write markdown, living documentation and literate programming together <33
more info here: https://www.osmoza.si/en/event/pocket-infrastructure :)