Original post on social.treehouse.systems

social.treehouse.systems

Original post on mastodon.social

mastodon.social

Original post on mstdn.chrisalemany.ca

mstdn.chrisalemany.ca

A new social me

How the Fediverse has influenced the way I live my (online) social life now.

blog.sturmsucht.de

Original post on gotosocial.thenexus.today

gotosocial.thenexus.today

Why I Left WordPress for BearBlog

Or: How I Bought Myself Some Digital Immortality A bear sitting at a desk typing on a computer. AI This is a re-edited version of a post that first r...

catsandbirdsandstuff.com

Working with the 4Rs of Web Development

## Revolutionary? and self-rewarding! K.I.S.S. and DIY WebDev strategy cripples tech bros, oligarchs, and autocrats _Here at The Fulcrum we cover items and ideas in the Techno Anarchist Manifesto relating to KISS and DIY development for the Open Media Network and Open Social. We preach, promote, and practice keeping your work simple and crafting it yourself. It might require more effort but it's more rewarding. If you follow us, you know that._ _You also know I'm prone to curse. If not, you're now prewarned. Asides over._ In this article we will cover a simple, DIY strategy. In particular, it's about what I call the 4Rs of web development. They are empowering, reduce frustration, and help you feel good about your work (and yourself). You probably got this, but the 4Rs are a riff on **Reduce, Reuse, Recycle** for the consumption of physical goods. And the principle of the four's usage would apply to any type of programming work to a significant degree. And there's the added benefit that this work strategy thwarts democracy and planet destroying tech bros, oligarchs, and autocrats. Moving on, the Techno Anarchism-based 4Rs are: * Resist * Reduce * Reuse * Recirculate If you aren’t self-employed, please try to influence your clients, coworkers, and management to follow or let you follow the 4Rs within your projects. This is not all or nothing. Every little bit helps, even following a few of them. Win the battles you can when laboring (not working) for the necessities in life. You’ll notice I’m using the word “work” a lot. The previous advice necessitates a quick note on the difference between "labor" and "work". The first is what you have to do to earn money to pay for whatever housing, food, utilities, transportation, etc. you need to survive. You’re part of the labor force and to some degree do forced labor. _And I would advise being in a union so you can at least get paid well for putting up with it._ The second is effort you voluntarily choose to exert and which can be a reward in and of itself. If you’re very fortunate this work could also provide income. Then you would be working for yourself whether you're self-employed or not. So, let's get to “work” with the 4Rs. ## Resist Unsurprisingly, as a techno anarchist we recommend resisting all the techshit that is infecting every element of our lives. And it's only getting worse at an exponential rate thanks to all the clueless fucks using AI for any and everything. This is especially true for programming. And even for "real" programmers who should know better. So, resist: * Techno Feudalism * Techno Fascism/Authoritarianism * Generative AI Tools * Non-standard Code * Proprietary Code Yanis Varoufakis came up with the term **Techno Feudalism**. He writes: '“… capitalism is dead, in the sense that its dynamics no longer govern our economies. … that role … has been replaced by something fundamentally different, which I call techno feudalism. … the thing that killed capitalism is capital itself. Not capital as we have known it since the dawn of the industrial revolution, but a new form of capital, a mutation of it that has arisen in the last two decades, so much more powerful that its predecessor that like a stupid, overzealous virus it has killed off its host.” That capital is rent-seeking cloud capital. Use the link above to learn more about techno feudalism, cloud capital, and how not to become a serf. But for web development purposes, resisting techno feudalism involves not having anything to do with big tech's tooling and the benighted efforts of its sub-human oligarch owners and amoral/immoral executive management. That includes not using GitHub, VS Code, CoPilot, Azure, ASP.NET, Edge, React JS, Angular JS, Chrome, Gemini, Ruby on Rails, AWS, xCode, Swift, Safari, Codex, Claude, etc, fucking etc. **Techno Fascism/Authoritarianism** is what the tech oligarch owners/purveyors (of these examples and other techshit) do on a daily basis and hope to achieve. They're trying to maximize their raping and pillaging. So we won't have to kill the evil vikings, let's resist and weaken them in order to drastically reduce their wealth and source of power over us. Without obscene wealth they can't lobby, bribe, or buy our shit politicians. Please don't give them even one penny of your cash or monetization of your attention or time. For **"AI"** , just rinse and repeat as it is an artifact of fascism with very few legitimate uses. Pure and simple. ### Sorry, but I'm going on a quick, spiky rant. For general usage, unless you're disabled (and it enables you) or you're communicating in a second language, try not to be a clueless dipshit and don't use AI. Nobody likes a slop merchant and the shit digital products they "create" suck on a practical level. So, please just don't go there. And don't fucking whine "but it's useful." Chemical weapons are useful for killing people but that doesn't mean you should use them. In any event, these "useful" tools only provide slight improvements, average results, and little ROI compared to their extravagant costs to your wallet and soul. And that doesn't include the more dreadful costs to the place where you live and your neighbors. Most importantly, generative AI is stolen goods being fenced in online pawnshops in order to deskill the workforce and drive down the cost and power of labor. And it's knowingly destroying the environment and local communities every step of the way. If you don't care about that, I'm sorry but you're a cunt. Get off my website and don't come back. So, fuck AI and 98.24% of anything to do with it. Be an asshole luddite like me, not a techno fascist. Sorry, but this shit boils my piss. :( Ok, rant over. Finally, please resist using some idiot's **vibe code** or any other non-standards-based garbage whether it's generated by a LLM or an incompetent human developer. There is plenty of time-tested, community-trusted, high-quality stuff to reuse (as you will see below). There are also practical financial reasons for resisting all this tech bro nonsense. Expensive (in the first place), rent-seeking, and addictive corporate "solutions" will inevitably enshittify and fuck you and your long-term projects over. They are many monetary rewards for avoiding the use of proprietary code, platforms, and systems tooling. Use opensource (but not necessarily free) tools for more financial recourse. I'm sure you're intelligent enough to be able to successfully manage the investment. ## Reduce The second R involves reducing (if not eliminating) the use of overly-complicated clusterfucks like frontend frameworks, most backend frameworks, and development platforms. And it avoids misapplying languages like JavaScript or Python in the first place. This applies to both proprietary and opensource tech. So, no React, Angular, NodeJS, Tailwind, Bootstrap, Atlassian, Jira, GitHub, GitLab, Slack, corporate cloud tech, AI IDEs, Wix, Squarespace, Webflow, etc., etc., etc. for us and our web development work. Please use the simplest tool(s) for each task you have to accomplish. There is no need for 95% of this command-line, CI/CD, deployment, dependency, permissions, builds, API accessing hell. And trying to use one size fits all, enterprise-scale solutions for the smallest tasks is about the most ineffective thing you can do. Plus, simple is more secure as well. The best stack is no stack. Strategically stock your toolbox with long-lasting, effective, and simple tools for achieving the best results for your unique work. You'll find it less frustrating and alienating if a little more time-consuming. Our minds need exercising and skills need using to stay sharp. Again, this is good for our mental health as developers. Reduce your use of over-engineered horseshit and your projects will work years from now and most importantly just work period. Today. ## Reuse Please don't reinvent the wheel. There is nothing that is new under the techno sun. Just use standards-based development's existing tools and techniques for guaranteed success. The best way to do things, is to use things, that already do things the best way. That's the third R. So, reuse/use: * Web Standards * HTML and CSS * Vanilla JavaScript and PHP if needed * Code Snippets * Web Components if needed * Opensource Tools * Protocols You can easily research, find, and reuse standards-based solutions to your challenges because **standards** are well documented by their very nature. Use what works. **Vanilla code** is easier to learn or source for more complicated tasks. This is because it's also well documented and there is lots of readily available training. It's easy to upskill yourself because much of that training is time-tested, evergreen, and free. In other words it uses the fourth R. ;) You should also save and reuse your customized **code snippets** or use those available via helpful code libraries. Store them wherever you want as long as it's free from being scraped. Please don't feed the slop engines and monetize the slop merchants. If truly needed, vanilla **web components** are the shining example of this strategy. Plug and play saves the day for projects that legitimately need extra functionality. But, most of the time you shouldn't even need the majority of these components. Don't use a tap screw where a thumb tack will work. In fact, you should even try to avoid vanilla JavaScript, PHP, and databases whenever you can. There are dozens of simple, readily available, and easy to use **opensource tools** (see the link above) for web development that selflessly serve the community and need your support. Please use them. _And when you do, finance them with small monetary donations or indirectly finance them with code or in-kind contributions. Please, assist them via promotion at a minimum._ They will pay you back ten fold. Other than FTP, **web protocols** are something you rarely need to touch, but if you do need them, use them natively rather than via obfuscated platforms or tools. Remember, even if you're working on a sophisticated PWA, let's avoid clusterfuck tech. ## Recirculate The fourth R involves showing and sharing your work and knowledge so others can benefit from your rewarding experiences. Share quick tips on open social and write how-to articles or produce videos for your community. That is the essence of participating in the Open Media Network. It's even a form of informal documentation. Giving back builds karma and empowers more developers to build more websites and PWAs for everyone to use in place of techno feudalist platforms. It's a virtuous circle. And it feels good to help others. Now, the best form of recirculating is building on/improving existing opensource tools and (of equal importance) formally documenting those efforts. _On that note, please maintain and update your documentation just as much as you do the code. Shit outdated docs defeat the purpose of DIY and recirculation._ _And this could be part of the 1.76% of AI usage that might be justified. That's provided it's opensource AI, locally trained on your information, and hosted on servers or personal computers you totally control._ Alright, enough with the asides. Let's finish this exploration. ## Wrapping it up So, using the 4Rs isn't rocket science. It's just purposely following a simple and sound strategy by building simple sites and apps (yourself). And doing it with simple tools. But their use furthers an incredibly important goal - debilitating oligarchs (whether feudalists or fascist/authoritarians) and the autocrats they buy. Please resist the tech overlords, reduce your consumption of their techshit, reuse proven tech that already exists (in your unique way), and recirculate your improvements, creations, and discoveries. Again, this is not an all or nothing strategy. Like following techno anarchism itself, every little bit you do helps a little bit of everything. If we follow the 4Rs within our web development and PWA work, we can go a long way in defeating techno feudalism, techno fascism/authoritarianism, and tech-bro-ism in general while keeping a smile (or smirk) on our face. We'll also create better projects. Let's get to work with the 4Rs, be proud of what we build, improve our mental health, bring back the web we used to love, and set an example for other programmers! Share on Open Social Media * * * ## CTAs * Please share this article. * Follow us on Surf or at @thefulcrum@thefulcrum.dev on the Fediverse or at @thefulcrum.eurosky.social on the Atmosphere for daily coverage of similar topics. * Read, live, and share The Techno Anarchist Manifesto!

thefulcrum.dev

DrFed on reducing complexity and enabling more people to shape the Fediverse

DrFed is a web-based platform for developing and debugging implementations of ActivityPub – an open standard and protocol for decentralised networking. A team of four people from East Asia is developing DrFed. We interviewed one of them, Hong Minhee, regarding openness, tech, technical specs, the Fediverse’s strengths and limits, language barriers to decentralisation, and far more.

apc.org

Phoneblogging

Of course, for my first post of Blaugust, what would I be writing about other than blogging? In all seriousness though, this is far more about UI/UX and accessibility, and I think it touches on something both important and neglected by the IndieWeb community. In some webweaving circles, you'll see websites created that only work properly on a desktop screen. Sometimes this is due to coding difficulties—I've been there many times myself, media queries in CSS can be a difficult beast to tame! But other times, this is an intentional design choice, which I've seen on certain NeoCities sites, for example. In conjunction with this, in the circles I'm in there's an understanding that the computer (laptop, desktop) is a better user experience compared to a tablet or smartphone. I literally just wrote a post about my adoration for the personal computer, so I'm contributing to the problem. And it is a problem, because globally, around 2 billion people access the internet exclusively via their smartphones, representing half of mobile internet users. In 2019, World Advertising Research Center predicted that number to be 3.7 billion people, and it will most likely continue to increase. In the United States, 16% of adults (tens of millions of people) are smartphone-only internet users who lack home broadband. I believe this is an existential problem for the IndieWeb currently. If people are designing their personal sites to be desktop-only, then they are alienating billions of people who only have a phone to access—and most are living in developing nations and the global south. ## The Real Problem with Phoneblogging But, luckily, this problem is solved by being more mindful that responsive design actually is important, learning how to implement it, and realizing that this is not something you can shrug off simply because you have a personal negative view of smartphones—whether due to your own problematic screentime or usage, or whatever. This isn't the actual problem I want to write about, though. What I want to figure out is how someone can start a blog, or join the IndieWeb from their phone themselves. This is a puzzling UX use case to solve—or at the very least, has been one that has been almost completely neglected. When it comes to taking notes and coming up with a draft for a blog post, then your phone is a fantastic tool. There are numerous note-taking apps for both Android and iOS to choose from, many of which would sync automatically to your desktop—ah, but there's the rub! Cross-platform options like Obsidian, Simplenote, and Google Keep will sync notes across an Android or iOS phone and desktop. If you're inside Apple's walled garden, Bear gives you Markdown-native notes synced via iCloud, and Drafts is built around capturing text fast (and being expensive) and routing it wherever it needs to go next—though neither of those two has an Android counterpart. When it comes to microblogging a thought that's less than a thousand characters, phones are also excellent for that. Whether you're on BlueSky or Threads or using one of the multiple well-designed Mastodon apps like Ivory, Ice Cubes, or Mona on iOS, or Tusky on Android. This isn't the issue I'm trying to tackle. No, I'm talking about full-fledged longform blogging. Rarely, if ever, do you find a comfortable user experience for the writing part. You're either constantly switching to symbols within the on-screen keyboard if you're writing in Markdown, or you're trying to press impossibly small buttons for rich-text formatting. There are workarounds for the limitations of an on-screen keyboard. You could dictate your writing by speaking, or if you can afford a bluetooth keyboard (or one that can connect via your phone's charging port) then that too would vastly improve the experience. And don't get me wrong, there are mobile apps that exist, though they're by and large siloed solutions tied to a single platform: * **WordPress** : the official app (also on Google Play for Android) lets you write, edit, and publish from your phone. * **Ghost** : Ghost has an official Android app but no iOS app. Apple users are stuck with unofficial community builds like Ghost Publisher. * **Medium** : also on Android is fine for reading, and _can_ do serious longform writing. * **Tumblr** : also on Android is still going, still chaotic, and a good blogging platform underneath all the fandom noise, in my opinion. Even Google's Blogger has an Android app. A cursory search on the iOS app store also showed me solutions like Git Blog App, which lets you commit directly to a Git-based static site from your phone. I also want to shout-out here to Pagecord, an independent blogging platform that is focused on giving people as many ways as possible to post. They have post-by-email, an Obsidian plugin, an iA Writer solution, scripts, Shortcuts, or "anything that can make an HTTP request. 🔌" But writing is only one part of blogging. If you blog like me, you'll have dozens of tabs open at the same time—looking things up, adding sources, sharing links—and this only takes a couple key strokes or mouse movements on desktop, but is an infuriating slog on a mobile device switching back and forth constantly. And if you're on a low-end device, there's a good chance of a crash or losing work when RAM automatically tries to free itself up. ## What Others Have to Say I decided to pose the question to my friends on Mastodon to see real-life examples of phoneblogging and was very happy with the diversity of results. Of course, this is purely anecdotal, but it does give a good insight into this. ### 1. No Phoneblogging To start, some people do not partake in blogging on their phone whatsoever: > Nah, writing on a laptop only. I need the commitment of sitting down, taking time out to do it, even if it's a short note. I might make a note on a phone occasionally. > > I use a static site generator, so it would be hard to publish on a phone anyway, but for me that's a plus. > > — Paternoster @paternoster@mas.to > Low vision keeps me from interacting with my phone much. If I use it for anything related to blogging, it is most likely going to be for a photo. > > — Emma @emma > Absolutely no, desktop only. > > Fedi/bsky posts yes, chats yes, blog posts require a lot of concentration to write, and also I'm just not using an OSK [onscreen keyboard] for that. > > — Alice @alice@mk.nyaa.place ### 2. Partial Phoneblogging Then there's a group of people who use their phone for drafts and note-taking, but then transition to finishing the blog post on their desktop: > It depends when the idea hits me. If I'm out and about, I'll sketch or maybe even finish the post in the Notes app on my iPhone. I won't post from my iPhone though, I'll copy and paste when I get to my Mac (unless I'm really away, like a vacation). If I'm at my Mac, I'll probably just start writing directly in the blog editor. > > — James Huff @macmanx > Not really. For a while I used the WordPress app occasionally, but I always had to go back and clean things up from the website afterward. > > Add that my phone typing has gotten worse over time (or maybe the onscreen keyboards have), while my physical keyboarding has gotten better. (That kinda surprised me—after how many decades of typing, suddenly I'm touch-typing more reliably? How? And it's not like I stopped typing on phones either, so why has _that_ changed?) > > I guess the closest I get to blogging from my phone now is when I write a social media post (or thread) that I later fix up or expand, or when I jot down notes that I build on later. I'd much rather connect a tablet to a smallish keyboard than deal with the tiny screen and tinier touch-points if I'm going to write anything longer than, say, this. > > — Kelson @kelson@notes.kvibber.com > I'll sometimes build outlines with it using the app Journelly. I never finish them there though. The outline typically gets imported into the app I use on my computer to finalize things. > > (And to be clear when I say build I mean create and write. It's not AI but typically a bulleted list of notes I make myself in the approximate order I'll want them in the end result) > > — Brandon @mbjones > I don't publish from my phone, but I occasionally like to thought dump on the go. My workflow includes a folder of MD files so I just pop open Obsidian with a template for the date and title, and write in a bullet-point list format. It's easier for future me to edit and reorganize my thought process when it's small chunks. I also prefer to write in simple sentences, since I'm not great at typing longform when I can't catch most of it. > > Sometimes, if I have enough privacy (which isn't often) I do voice-to-text, again for drafts, not final versions. > > — Hatch @binomech > Wouldn't call myself a blogger (relevant to your last blog post haha) so feel free to discard this reply, but the few times I've written something that wasn't (fan)fiction, it depended on where I was, what I was doing, and how long I expected the piece to be. > > I think my Design Philosophy piece was written mostly in Ellipsus on my phone, but I don't really remember: https://www.mrnnki.com/writing.php?id=6 > > I expected it to be longer than it ended up being. > > My Name Is Mrnnki was definitely written on my phone: https://www.mrnnki.com/writing.php?id=12 > > I was at a brew barn listening to some music and thinking about online identities. > > Bluesky Sucks was written on my computer, directly in HTML: https://www.mrnnki.com/writing.php?id=13 > > I was at home and already working on something for my website, determined to rewrite my old Tumblr post into something a bit more accurate. > > Direct publishing to my website from my phone is not something I'd ever do, hah. I'd have to make the admin panel for it myself, and keeping that secure wouldn't be fun > > — Mrnnki @mrnnki@problemeowtic.net ### 3. Full Phoneblogging To my surprise, there are quite a few people who do, in fact, use their phone to blog! And I love their solutions to this: > I do, I have a micropub endpoint for my static site and make use of it a lot. On mobile, I usually only fix typos, add a sentence or two, upload images. For the bulk writing I prefer my laptop, but I'll often prepare drafts on my laptop and then publish later from mobile via micropub. The existing clients could use some love though. I hope it becomes more popular, it's such an underrated protocol IMHO! > > — Ruben @kedara I've set up a Micropub endpoint for my own blog! Funnily enough I haven't ever used it. Silly me. > I do. I write the majority of my notes from a dedicated page that's kinda like a social media post UI (screenshot attached). I occasionally write longer, standard posts from my phone too, but that's rare and usually shorter posts, like the Linkception post from last night—that was written on my phone. > > Most often I use my phone for notes or adding drafts when I have an idea. > > — Kev Quirk @kev@fosstodon.org > Oh, I used to! In 2021 I wrote a blog post about updating my Hugo blog from my phone. After that I moved to a git CI/CD setup with Indiekit to update my blog from my phone... but it was too janky and unreliable; I ended up strongly preferring to just wait until I was at my computer to post. > > — Jessica Smith @jayeless > Absolutely. With the help of #Obsidian. For my Notes I have there a simple creation workflow, with templates and the help of the plugin #Templater. My Posts and their drafts are created on my laptop, but synced to Obsidian to write on wherever I am. With this my phone is just one computer I can use to write. > > — Kristof Zerbe @kiko@indieweb.social > I do it quite a lot, because I'm mostly in bed and getting the laptop out is a hassle. Funnily enough what gave me the confidence that I could do it without a large editing surface and tooling is that I once built a blogging platform to which you can post directly from the terminal as an exercise when I had to learn Rails for work. > > — Anna Miriamsdochter @venite@mastodon.nl > I do. I optimised the wiki for just that. I have an "edit this page" link and a "add to this page" link. Since adding new pages needs a way to type their name before I can edit it, there's a form that provides this, containing the date. When adding to a page that has a name that starts with a date, the addition also starts with a date. When saving a page, links to it are automatically added from the front page and from hashtag pages so no extra edits are required. > > — Alex Schroeder @alex@social.alexschroeder.ch I absolutely love Alex's solution, and the coolest part is that he made it himself! Please check out his project Oddmu ## Results First, I want to take a moment to appreciate these responses. I only sent out this question yesterday, and I received so many responses from writers I admire. I am so grateful for this community and is one of the reasons I am such an advocate for the IndieWeb in the first place. I'm sure there will be more replies by the time I post this. Second, people are creative and resilient, surprise surprise. People find ways to phoneblog despite the limitations and constraints. But these solutions do, for the most part, require technical know-how that most people don't have. I'd love for there to be more accessible, simple ways to blog from your phone while maintaining the IndieWeb ethos. The mobile web is exactly where corporate media platforms thrive. Years and billions of dollars of research have gone into making Instagram, Facebook, TikTok, Twitter and co. as addictive as possible, regardless of the detrimental social consequences that has caused in its wake. I don't like writing about a problem where I have no proposed solution, but I think awareness is a good first step. The IndieWeb must make mobile-first a priority, not something to scoff at. We must find sustainable, accessible ways to make phoneblogging fun! ### Coda During my research for this post, I found an even more astonishing fact. 3.4 billion people still don't have access to the Internet _at all_. Nearly half the world remains offline. It is completely incorrect to assume the Internet connects us all. We still have so much work to do.

brennan.day

Original post on gotosocial.thenexus.today

gotosocial.thenexus.today

The Programmer's Fulcrum 31 July, 2026

Welcome to your weekly curation of the essential news in the Open Media Network and Open Social development communities with a focus on devastating big tech via Techno Anarchism.

thefulcrum.dev

Original post on mastodon.iftas.org

mastodon.iftas.org

It doesn’t matter if it works | Henry From Online

The personal site & portfolio of creative web developer Henry from Online

henry.codes

The Programmer's Fulcrum 31 July, 2026

Welcome to this week's The Programmer's Fulcrum. It's your weekly curation of the essential news in the Open Media Network and Open Social development communities with a focus on devastating big tech via Techno Anarchism. **As usual, we aim to provide actionable content you can use to destroy Techno Feudalism each week.** It has the additional benefit of weakening authoritarianism. IMHO, the best way to do that is to use tools from the Techno Anarchist Manifesto to build your own site(s) to participate in the Open Media Network. Then you should share it (them) via Real Simple Syndication (RSS), Open Social, and possibly a newsletter or podcast. This approach is similar to what some call the IndieWeb and its POSSE philosophy. The second best strategy is to have accounts on open social and use the hell out of them. And do the same with a RSS feed reader. We publish TPF on Fridays so you can enjoy it over your weekend. There's good stuff in all of our categories, so please take the time to enjoy and bookmark the items most relevant to your goals. We hope you are inspired to create new ones. Or you can jump straight to your favorite section. * Sites/Blogs/CMSs * Techno Anarchist / OMN Tools * OMN Programming * ActivityPub * Fediverse * More **FYI, my opinions will be in bold. And may involve cursing. Because humans. Especially tech bros. And fascists. Fuck´em.** ### Follow us on the Fediverse ## Follow us on Eurosky * * * ## Featured Item(s) **Rest of World writes:** A growing pushback against big tech companies, and greater awareness of the value of data, is spurring interest in data collectives and cooperatives, which give communities control over the collection, management, and distribution of their data. This alternative allows creators to benefit from data sets that may otherwise be ignored or misused. Fed up with Big Tech, communities turn to data collectives for control **This works well with my diminishing hopes for Manade. ;) See the Fediverse section below.** **Henry Codes writes:** The widespread deployment of AI/LLMs constitutes an existential threat to labor whether or not it is an adept move by the adoptive industries. Thus it is essential for workers to stop asking whether or not AI works and start asking who ultimately benefits from its deployment. It doesn’t matter if it works **Speaking of this horseshit, Zuzai.org writes:** I'll begin with something obvious: things made with AI tools are proliferating in lots of places where lots of people don't want them. Not so obvious: we don't have a good, crisp word to indicate that something is **NOT** one of these things, in other words, that it is free of AI. We need a new word. How about ... zuzai? **As in this website is zuzai. We're all in.** * * * ## CMSs Kyrylo Silin says: The favicon survived the web Germ's mama, Anna asks: Why websites? Typemill announces: Typemill 2.25.0: Relaunch and Small Improvements Pagecord announces: Classic just got a lot better ### Bear The Hour is Blue explores: Writing for Readers, Not Algorithms **The same goes for MCPs.** xIre reflects on: One Year On Bear **Good advice.** ### Leaflet Leaflet announces: An option to switch navigation direction for browsing older vs. newer posts from the post footer And Leaflet Lab announces: Piloting paid memberships for the open social web **Going the Ghost and SuckStack route.** ### Write.as / WriteFreely Write.As has: A small but helpful fix is out for federated blogs! Back to top 👆🏼 * * * ## Tools 404 Media reports: Being a Luddite Is Fun Again On a related note, Rafael says: Let me put in a plug for our dear old sdf.org/ **Tres cool.** ### Chat / Team Chat AboutSignal announces: Scheduled messages in Note to self now work as reminders in Signal for Android **Useful.** Signal is working on registration without a phone number. But what form will it take? Germ announces: Germ is Now Quantum Secure **Unfortunately, its iOS only.** ### Browsers Waterfox announces: 6.7.0-beta.3- Ultra Protection returns and Linux package repositories ### Search Ecosia announces: Your Ecosia searches in Germany just became more independent ### Cloud Nextcloud asks: Do I belong at the Nextcloud Community Conference 2026? The answer is yes. ### Writing LibreOffice has: LibreOffice, yours for a lifetime 9to5Linux reports: Calibre 9.12 E-Book Manager Adds Option to Convert GIF Images to JPEG/WebP ### Creative Rolle examines: Getting my photos Google-free – how to move from Google Photos to PixelUnion and quickly host your photo albums in Europe ### Linux / Open Android PostmarketOS announces: New dependencies, requirements, and recommended workarounds for kernels GrapheneOS announces: GrapheneOS protections against data extraction from locked devices 9to5Linux reports: Ubuntu Touch OTA 2.0 Officially Released for Supported Linux Phones and Tablets F-Droid has: This Week in F-Droid ### Hosting / Serving MauveRant examines: Self-Hosting S3 object-storage with Garage **Interesting concept and demonstration.** ### _This week's featured OMN tool_ #### The Techno Anarchist Manifesto The TAM is now available as a PDF, ebook, and website. The Techno Anarchist Manifesto Back to top 👆🏼 * * * ## Programming SIV shares: Verifiable Web Code — Why It's So Exciting The Zone explains: What software freedom means today Shin's Psychedelic World examines: Cooperative Software Dave Rupert reviews: The new yet familiar CodePen 2.0 **See the Stolon note below as well.** ### Git For all the AI butthurt Codeberg whiners: A slop peddler has started a slop-friendly Forgejo instance On a related note, Do Flamengos know they're Pink has: Open Source Is Indefensible **Here's a great quote:** We don't need to defend _the freedom to take from everyone all the time_. _Our freedom to associate, our freedom to refuse, and our freedom to decide over infrastructure we reasonably control_ all need defending though, and all of that is outside the jurisdiction of licences and code. Thank you Codeberg for reminding us it was there all along. Tangled is: Introducing Bobbin And Ricard Torres is: Moving away from GitHub to self hosted Gitea ### HTML That HTML Blog asks: Are y'all ready for HTMLDay? SelfHTML.blog has: Spickzettel zum schnellen Nachschlagen The Art of Not Asking Why? shares: Style & Emacs Config: A Semantic HTML Reckoning ### CSS Master.dev advises: When You Need To Make a Triangle, Think Conic Gradients Botmonster Tech says: CSS @starting-style lets you animate elements on entry without JavaScript ### Web Components Raphaël Bastide shares: Stolon has been updated, big time! **Cool tool.** ### JavaScript Evil Martians (with the best site design on earth) shows us: The secure way to release an NPM package in 2026 Master.dev looks at: Same Name, Different Component with Scoped Custom Element Registries ### AI Brno Hat explains: How AI Is Changing Open Source **And it's not in a good way.** Ivan Enderlin shares: GCC declines any legally significant contributions which include LLM-generated content or are derived from LLM-generated content **Good.** ### Other XWiki shares its: Release Notes for XWiki 18.6.0 ### _This week's featured programming tool_ ### In honor of their telling the slopmerchants and cryptobros to fuck off, it's Codeberg A community-led effort that provides Git hosting for free/open source projects. Codeberg Back to top 👆🏼 * * * ## ActivityPub ActivityPub.Space is: Reflecting on the existence of httpsig.org Ethan Black notes: Development is being done in GitLab to add ActivityPub support! ### _This week's featured ActivityPub featured tool_ #### Fedify Fedify is a Typescript framework that lets you build for the fediverse but skip the boilerplate. Fedify Back to top 👆🏼 * * * ### Permanent aside here (unfortunately) **This is a perpetual pet peeve because many people aren't able to comprehend ⬇️:** * **_The Fediverse_ is for communities (private, semi-private, formal, informal, or otherwise)** * **and _the Atmosphere_ is for the masses (unwashed, washed, or otherwise).** * **and _Corporate social media_ is for naive fools and intentional cunts.** **So, recognize their natures and don't ask the two protocols to go against them. This is also why we have accounts on both platforms and use them differently.** ## Fediverse The Nexus of Privacy says: The time is right: Organizing against the surveillance-industrial complex in the ATmosphere and the fediverses **This is literally what we're going for here at The Fulcrum.** ### Bonfire Bonfire is: Announcing Bonfire for communities: groups and tools to organise together Sharing a case study Back to top 👆🏼 * * * ## More AmalDev answers: Tech Explained: What Survives an Internet Shutdown? ### ATProto Paul's Blog has: Starting from scale in the design of the AT Protocol Nick's Blog continues a series: Permissioned Data Shapes: Feeds Permissioned Data Shapes: Notifications Chris's Corner looks at: The disconnect between web pages and the social filesystem ### Atmosphere Leaflet Labs asks and answers: What is the Atmosphere? **For potential users.** Wreckage/Salvage is: Launching a Cloud Atlas Standard Reader asks: What is Standard.Site? Next gen RSS? Cosmik Labs explores: Sensors, not just bookmarks (Patterns of Sensemaking #1) **Quite interesting.** Babesky says: Reclaim Your Algorithm And Colibri.Social says: If NVIDIA can un-launch a GPU, we can delay an app launch **Unfortunate, though smart.** ### P2P After the Distortion Field explores: The Antithesis: Why Freenet and Serverless Networks Are Reclaiming Digital Sovereignty ### RSS Jared Lemler AT Protocol & RSS **A new way to build RSS clients?** Karthikeyen NG looks at: RSS in 2026 — the best distribution channel nobody uses **Use it, mes amis.** Terry Godier announces: Current Now Supports Feedly in v1.0.15 ### XMPP XMPP previews: XMPP at FOSSY 2026 Nicoco shares: Quicksy ferme les inscriptions Georg (not George) Lucas asks: Are Emojis Allowed in XMPP Addresses? * * * ## CTAs * That’s it for this week. Please share The Programmer's Fulcrum. * Follow us on Surf or at @thefulcrum@thefulcrum.dev on the Fediverse or at @thefulcrum.eurosky.social on ATProto for daily coverage. * Read, live, and share The Techno Anarchist Manifesto! **And please build something for a community! We're painfully nurturing Manade.** Share on Open Social Media * * * ## Blasts from the past Previous Battalion Posts Previous Symfony Station Posts

thefulcrum.dev

Original post on thefulcrum.dev

thefulcrum.dev

Fed up with Big Tech, communities turn to data collectives for control

Data collectives and cooperatives, which let creators control the collection and distribution of their data, are emerging as preferred alternatives to big tech companies.

restofworld.org

Verifiable Web Code — Why It's So Exciting

Browsers are beginning to be able to guarantee that the code running on a page is actually the code its developers published — no silent tampering, no trusting the server. We think the payoff is huge:

blog.siv.org

Original post on social.coop

social.coop

What is Digital Sovereignty

Digital sovereignty is not about owning everything, it is about ensuring that nothing essential can be taken away. That single line settles more arguments than it first appears to, because it disqualifies the two positions that dominate the debate. One side imagines sovereignty as control. The other imagines it as

blog.documentfoundation.org

Original post on fosstodon.org

fosstodon.org