| Past devlog notes | https://jg10.solidcommunity.net/devlog/home.html |
| Github code mirror | https://github.com/jg10-mastodon-social |
| Now | https://jg10.solidcommunity.net/devlog/home.html#now |
| Bridged on BlueSky | https://bsky.app/profile/jg10.solidcommunity.net |
I just started working on a new project to see how far I can take AI with Solid and local models. If you're curious, make sure to follow along!
#PodOS will be presented at #Solid Symposium 2026 in #London 🎉
From Apps to Autonomy: Operating Systems for True Data Ownership
Even in open ecosystems like Solid, users often face a choice between the convenience of specialized apps and the flexibility of direct data manipulation. Solid-based operating systems and toolboxes aim to bridge this gap, providing a layer that makes personal data both accessible and actionable.
Browsing your data using PodOS is great, but nothing compares to an app that is tailor-made for the task. That's why PodOS Brower now allows you to open a resource in another app. We also have some exciting new features for dashboards builders.
https://pod-os.org/blog/2026/03/04/podos-202603-open-with-conditional-rendering-and-reactivity/
RE: https://mastodon.xyz/@NGIZero/116160055128846646
Several #SolidProject initiatives funded!
I've been exploring opening #SolidProject files from desktop file manager/Android intents
There's a few tensions to resolve for RDF documents:
1) base uri is commonly inferred when documents are dereferenced, i.e. it's not in the document contents
2) the origin of a document may be ambiguous, particularly as Android makes it easy to share content and hard to access files
3) files with identical relative URL content can be different in absolute terms, so file deduplication needs to be RDF-aware
I finally have a git setup I'm happy with when coding on mobile on a #SolidProject pod
PUTting .git/COMMIT_EDITMSG triggers add & commit via a Solid Notifications webhook
Using vitest for unit testing with ESM support.
Getting closer to TDD in the browser.
New blog post! Apparently, the term "Vibe-coding" was coined a year ago from today. I have some thoughts about it.
https://noeldemartin.com/blog/software-ideals-in-the-age-of-ai
In the last few weeks, there has been a lot of talk about the end of software development. We're entering a period where software is easier to make than ever before, and many are proclaiming that soon we won't need to look at code anymore. I'm also very excited by the idea that anyone can make their own software, but there is a problem. The design choices that come baked-in with most of these tools are not great. If you ask an LLM to vibe-code an app, it's going to inherit all the faults of the previous generation. In the age of AI, we need better defaults.
With the latest PodOS release, we are taking a big leap towards modularity and extensibility. You can now dynamically load Solid Data Modules to add new features to the core system.
https://pod-os.org/blog/2026/01/28/podos-202601-adds-dynamic-module-loading/
There’s a tension between being semantically rich (using your own terms and definitions), and being semantically aligned, in which you try to reuse terms from other vocabularies.
I think we need a new concept: eventual #interoperability. I propose to start rich with your own vocabularies, and only make alignments when there’s a concrete reason for building those.
https://pietercolpaert.be/interoperability/2026/01/08/eventual-interoperability
Noel De Martin
PodOS
Pieter Colpaert