I’m still learning about Solid and getting familiar with it, so I’m not sure if this all makes sense. But I’m the lead developer of a federated blogging platform (via ActivityPub), called WriteFreely, and I’m thinking it could be interesting to add support for Solid.
I’m imagining the real draw would be in owning / maintaining control over the content you publish, whether it’s public blog posts or private notes. And if we’re storing posts in a Solid pod, it’d be very easy for other apps to interact with them – everything is stored as plain text / Markdown.
Does this make sense? Is there anything I’m missing, or something more that could be done with an app like this?
Ooh wow, that makes you something of a celebrity! Yes, that would be very interesting. The primary thing to keep in mind when working with Solid is that the app has no control over the server, i.e. you can’t control the server and get it to do e.g. custom server-to-server interactions, at this point in time.
So there are two general strategies you could use:
You store the posts as plain text/Markdown on the Pod, and readers use a (web) app to access it, such as WriteFreely. Disadvantage is that you’ll have to have some way to point the app to the relevant posts to display, which can lead to somewhat cumbersome URLs (e.g. https://writefreely.instance/blog=https://my.pod/blog).
Besides storing the source text/Markdown files, you also compile them into HTML using the app, and then store those to the Pod.
To also provide e.g. RSS feeds, you’d need to go with an approach like #2 as well, or a server somewhere should be willing to do the work of fetching the blog posts from a Pod and serving that up as an RSS feed.
I do imagine the application doing plenty of heavy lifting for things like rendering Markdown into HTML, generating RSS feeds, etc. And ideally, the application would be able to associate a Pod with a user on the backend, so it could fetch posts and display them on a clean URL. But I think I can use this information to at least get started with everything.
Thanks for sharing this! Will definitely try to attend those events, and will read over those discussions – those ideas seem totally in line with the kinds of things I’m thinking for WriteFreely.
Ah of course, Write.as does have a back-end. That does make things easier in the sense that it could do the rendering on the fly, and possibly keep its own index of Pods/Solid-powered blogs for less cumbersome URLs - although then of course you are once again bound to that instance.
(I think the main mindset change between the Fediverse and Solid is that you don’t need an “instance” - an app doesn’t need a server. So whereas people have e.g. a Mastodon account and a Pixelfed account, with Solid, they’d just have their Pod, and Mastodon and Pixelfed would be apps that use the same Pod account.)
Anyway, feel free to drop by with further questions any time!
These are also points of possible alignment between our communities, I think, though I’m not deeply up to par on technical details. There’s research into moving fediverse into hybrid decentralization (federated + p2p), using content-based addressing, different schemes than HTTP, and to implement roaming identity.
Oh absolutely, lots of alignment between the communities (unfortunately I don’t have the bandwidth to be as active in both; I don’t know how you do it ) - I was mainly talking about one’s mode of thinking while working on support for the different technologies when building an app, today.
Unfortunately - because I find it so very important and someone has to do it - I spend a lot of time in advocacy and rallying for community engagement, but to the detriment of my own more technical aspirations Community work vs. “deep work” don’t go well together…