A Node on the Web

RSC — Really Simple Conversations — is a feeds-native social timeline: people wh...

Tue, 21 Jul 2026 12:44:59 GMT

RSC — Really Simple Conversations — is a feeds-native social timeline: people who post here and people who post on their own site are equal citizens. Everything travels as RSS — posts, replies, whole conversations — so following, threading, and federation work with nothing but open feeds.

My goal with RSC is not just to publish the code of how it operates and interop but also to publish the spec/plans used to build the code itself.

RSS can absolutely participate in virality. If a million people subscribe to a f...

Mon, 20 Jul 2026 19:37:02 GMT

RSS can absolutely participate in virality.

If a million people subscribe to a feed, read a post, and some of them redistribute it through their own feeds, websites or social accounts, the post can become viral. Virality is an emergent pattern of circulation, not a button owned by a platform.

What RSS provides first is distributed visibility: reach created across many independent readers and publishers, without one algorithm deciding what everyone should see.

Open-source collaboration in the age of AI I am not going to reconstruct the ent...

Mon, 20 Jul 2026 19:12:12 GMT

Open-source collaboration in the age of AI

I am not going to reconstruct the entire disagreement that prompted this post.

Some of the public exchanges have been deleted. Other parts happened privately or by email. I have no interest in tracing every sentence, assigning blame line by line, or producing a forensic account of who said what. That would only prolong a conflict that has already taken up too much space.

But people noticed that I removed my participation from the project, and I have started receiving emails from strangers asking what happened. So I want to explain the broader issue, without turning a personal disagreement into public theatre.

Open-source collaboration does not necessarily become easier because AI makes it easier to inspect code, identify bugs, produce patches, and write detailed issues. In some ways, it becomes considerably harder.

You can spend time formulating an issue carefully and professionally, only for it to be perceived by the repository owner as a list of orders.

That owner is, of course, entirely free to reject the contribution. They can close the issue, say that it is outside the project’s scope, explain that it is not on the roadmap, or simply decide that they do not want to pursue it. There are thousands of legitimate ways to govern an open-source project.

Governance by burnout is not one of them.

When you use an AI tool to help document a problem, the resulting issue may contain precise examples, references to specific lines, screenshots, reproduction steps, and concrete observations gathered by running the software outside the environment of its original author.

That can be useful. It can also be overwhelming.

The problem is that the intention behind such a contribution may not survive the way it is received. You may believe that you are documenting a bug thoroughly. The maintainer may see a wall of text, an unsolicited audit, or an attempt to dictate the project’s direction.

You can ask questions first. You can soften the language. You can repeatedly state that the maintainer is free to ignore the suggestion. None of that guarantees collaboration when the other side does not experience the contribution as collaborative.

Most of my experiences have been different.

I have submitted issues and pull requests to several projects, including repositories connected to my professional work. Some of those contributions were written with the help of AI—not because I could not be bothered to write them myself, but because the tool already had the context: the code, the logs, the behaviour I had observed, and the steps that exposed the bug.

When the issue was valid, it was investigated. When the patch fixed a real problem, it was reviewed. Sometimes it was merged directly. Sometimes the maintainer rewrote it to match the project’s architecture, conventions, or preferred way of working.

That is normal. A contribution is not an instruction. It is material offered to the project.

For Indiekit, for example, I submitted a skeleton pull request of roughly two thousand lines containing the foundations of a Microsub plugin. It was not something the lead developer could review immediately. It required time and several email exchanges. But the contribution was handled professionally.

That first pull request opened the way for further work, with the plugin I already use in production gradually being reviewed and reconstructed under the oversight of the person responsible for the project.

I have seen similar responses in projects such as Dolibarr, Odysseus, and ComfyUI. A suspected bug was investigated. Its existence was corroborated. A fix was discussed or implemented. Everyone using the project could then benefit.

That is one of the core ideas behind open source.

This is not an argument that AI is inherently good or bad. It is an argument that collaboration still depends on people who actually want to collaborate.

A project can publish its code under an open-source licence without being socially open to outside participation. That is entirely legitimate, but it should be understood honestly. Otherwise, openness risks becoming more of a posture than a practice.

The recent conflict also showed me how easily both sides can misread each other.

The maintainer indicated that they could not follow or process what I had written because it was too much. I interpreted this as a request for greater clarity and replied with another comment summarizing my previous points, together with screenshots from my implementation.

I believed I was reducing the burden.

In reality, the person was angry. They had perceived my earlier issues as orders and felt overwhelmed by my participation as a whole. My attempt to clarify the situation therefore became another contribution to the very problem they were describing.

I later tried to explain myself privately and apologized. I was also transparent that some of the issues and comments had been written partly, or sometimes almost entirely, with Claude’s assistance.

Again, this was not because I had randomly asked a model to invent criticisms of somebody else’s project. The tool was helping me work on the implementation. It already held the context of the bugs and limitations I had encountered, so using that context to draft an issue was the most direct workflow.

But the origin of the text does not erase its effect on the person receiving it.

Everyone is overwhelmed. Maintainers especially are often expected to write the software, review code, answer questions, manage releases, handle support, moderate discussions, and absorb the emotional reactions of users—all without compensation.

Adding more explanations, even explanations intended to correct a misunderstanding, can simply produce more pressure.

My response was therefore to withdraw. I removed my contributions and comments where I could, apologized for the parts for which I could take responsibility, and moved on.

That was not a protest against my work being rejected. Nobody is required to accept an issue, a patch, an idea, or a contribution. In a world where AI makes bootstrapping increasingly accessible, people can fork a project and take it in another direction. That freedom is essential, and it should not change.

The issue is not rejection.

The issue is the growing potential for misunderstanding, misperception, and misjudgment between people working at radically different speeds, with radically different expectations, using tools that can generate more material than any small project is equipped to absorb.

Over the coming years, situations like this will become common.

Contributors will have to learn that the ability to identify ten problems does not mean that a maintainer can process ten issues. The ability to generate a detailed analysis does not mean that detail is always helpful. A technically correct contribution can still arrive in a socially destructive form.

Maintainers, in turn, may need clearer ways to communicate what kind of participation they want, how much they can realistically review, and whether outside contributions are genuinely welcome.

We are entering largely uncharted territory. The tools are evolving faster than the social practices around them.

We will need to rediscover some old rules of collaboration and invent new ones: smaller contributions, clearer boundaries, explicit expectations, consent before large interventions, and a better awareness that attention—not code—is often the scarcest resource in an open-source project.

AI can help us produce more.

It cannot make us ready to receive more.

Whoever reads this, I came and go in Peace, I will keep doing my part the way I see fit, but I have definitely learned a lesson here and for that, I’m thankful.

There is a Ideas markdown file in the RSC GitHub repo but I want to share on my...

Mon, 20 Jul 2026 17:17:21 GMT

There is a Ideas markdown file in the RSC GitHub repo but I want to share on my blog some of the things currently in development :

Better user management Users should be able to cancel and remove their accounts and cascade removal of their posts and replies.
better moderation and governance for feeds

creating an open publishing system is easy, moderating it is a pain in the A, so before this goes into a direction I don’t want I want to be able to have the tools to moderate feeds the system ingest.

I want to be able to differentiate an RSS feed from a compatible textcasting instance and RSS feeds added by users.

Currently, there is no difference between a user a a “remote user” representing an RSS feed subscribed by a user, not all feeds are textcasting feeds so we need a way for admins to decide which other instance they federate to, think subscribe bidirectionally and users added RSS feeds.

If/when an item comes from a remote feed I want to be able to moderate it, hide it, remove it, block the source if needed.

Inevitably someone will use one the demo sites to publish unwanted content or subscribe to a dubious feed just to see How it goes…

Gated community Currently registration is open and users can even make temporary posts to try the app, these guest users without a formal registered account are wiped periodically unless they verify their email registration.

I want this to be configurable, each instance will have different requirements, RSC need to come up with tools to help operator handle an instance.

Better enclosure support Right now the system doesn’t support enclosure (podcasts) obviously the underlying tech support it, it’s RSS after all but the web front-end doesn’t know what to do with it, I want a shiny play button where needed and the ability to properly display media elements.
Better integration with YouTube, Funkwhale, SoundCloud, Spotify A link from there should display an embedded player and fallback to link if no JS

There is probably a tons of things I’m not including here, my brain is fried today.

Stumbled upon a few (local) #AI tools that made me really curious https://www.fe...

Mon, 20 Jul 2026 16:43:36 GMT

Stumbled upon a few (local) #AI tools that made me really curious

@wjmaggos@liberal.city it doesn’t have that… At most if a lot of different insta...

Sun, 19 Jul 2026 17:58:40 GMT

@wjmaggos@liberal.city it doesn’t have that… At most if a lot of different instances existed, and were interlinked you would have distributed reach, can that be called social media boost? I don’t know… So yes currently #RSC is a social network with integrated RSS feeds, literally made for small communities with specific topics… Albeit it could also be used in different ways

Hmmm I wasn’t expecting THAT :)

Sun, 19 Jul 2026 13:18:21 GMT

Hmmm I wasn’t expecting THAT :)

Good work! Both the explainer and the implementation! I’m using indiekit which b...

Sun, 19 Jul 2026 11:35:33 GMT

Good work! Both the explainer and the implementation! I’m using indiekit which basically comes with IndieWeb batteries included! https://rmendes.net and I’m working to get it implemented on RSC https://rsc.rmdes.be

Show HN: RSC , a feeds-native social timeline you can self-host ( rsc.rmdes.be )...

Sat, 18 Jul 2026 17:03:52 GMT

Show HN: RSC, a feeds-native social timeline you can self-host (rsc.rmdes.be)

HN link

edit : name changed

So this is a social network built on top of RSS feeds in very short, its also fe...

Sat, 18 Jul 2026 13:35:27 GMT

So this is a social network built on top of RSS feeds in very short, its also federated, bob.rmdes.be and alice.rmdes.be users can interact with RSC and the whole thing gets properly threaded in every instances

right now IndieAuth is not yet implemented, but when it is, people will be able...

Sat, 18 Jul 2026 13:34:16 GMT

right now IndieAuth is not yet implemented, but when it is, people will be able to login to textcaster using their own h-card from their own site, this is basically a “social network on top of RSS feeds” in the future we could imagine rsc.rmdes.be as a fediverse identity itself (using Fedify probably) but its unclear to me how deep the integration should be going

Well the cat is out of the bag : if you like #RSS and the idea of a social layer...

Sat, 18 Jul 2026 12:50:33 GMT

Well the cat is out of the bag : if you like #RSS and the idea of a social layer on top of the existing web without lockin, ads and algorithms try it : https://rsc.rmdes.be #Fediverse #ATproto #ActivityPub

The technical aspect of Odyssey IMAX filming is in itself astounding work. I had...

Fri, 17 Jul 2026 18:43:09 GMT

The technical aspect of Odyssey IMAX filming is in itself astounding work.

I had no idea it was this complex and old-school to produce an IMAX movie.

Makes me want to watch it again… In a IMAX screen this time 😅

Working on something really cool, but its too soon to show, all I can say is its...

Fri, 17 Jul 2026 14:14:01 GMT

Working on something really cool, but its too soon to show, all I can say is its about RSS Reader, Micropub and Webmentions

Interesting…

Thu, 16 Jul 2026 16:36:32 GMT

Interesting…

Changed on my side !

Thu, 16 Jul 2026 13:23:40 GMT

Changed on my side !

Phandroid : Phanpy for Android

Wed, 15 Jul 2026 15:48:30 GMT

I can now use Phanpy properly using my AP/Fedify implementation for Indiekit !

This is a test

Wed, 15 Jul 2026 15:05:31 GMT

This is a test

How to Set Up Windows 11 Without a Microsoft Account in 2026

Tue, 14 Jul 2026 15:18:52 GMT

I recently got around this but using another approach, bookmarking this so I can compare…

A Node on the Web

RSC — Really Simple Conversations — is a feeds-native social timeline: people wh...

RSS can absolutely participate in virality. If a million people subscribe to a f...

Open-source collaboration in the age of AI I am not going to reconstruct the ent...

Open-source collaboration in the age of AI

Most of my experiences have been different.

There is a Ideas markdown file in the RSC GitHub repo but I want to share on my...

Stumbled upon a few (local) #AI tools that made me really curious https://www.fe...

@wjmaggos@liberal.city it doesn’t have that… At most if a lot of different insta...

Hmmm I wasn’t expecting THAT :)

Good work! Both the explainer and the implementation! I’m using indiekit which b...

Show HN: RSC , a feeds-native social timeline you can self-host ( rsc.rmdes.be )...

So this is a social network built on top of RSS feeds in very short, its also fe...

right now IndieAuth is not yet implemented, but when it is, people will be able...

Well the cat is out of the bag : if you like #RSS and the idea of a social layer...

The technical aspect of Odyssey IMAX filming is in itself astounding work. I had...

Working on something really cool, but its too soon to show, all I can say is its...

Interesting…

Changed on my side !

à lire…malheureusement…

Phandroid : Phanpy for Android

This is a test

How to Set Up Windows 11 Without a Microsoft Account in 2026