4 ms·

How to implement what OP wants to have: - their content stored on a PouchDB/CouchDB server. blog posts, comments, shared memes, listened songs... anything can

How to implement what OP wants to have: - their content stored on a PouchDB/CouchDB server. blog posts, comments, shared memes, listened songs... anything can be represented as an ActivityStream document - files/attachments can go to an IPFS store - the ability for authenticated users to pull this data, and remix into their own database. That is it. You can then have all kinds of tools to author the content. You can have your static site generator pushing your content there. You can have a audio scrobbler and get last.fm. Any commit to github can become a entry in the journal. You can send pictures from your phone. Saved bookmarks. Shared cooking recipes... So you will have your different sources of truth (git for the text content, your media library for your pictures), you have the database and you have your peers databases as the "remixed" copy of your data.

mxuribe 5y ago
I think Tim Berner-Lee's SOLID project intends to - at least conceptually - provide the needs that you cited: https://solidproject.org/about https://solidproject.org/about Maybe the implementation layer details might differ, but it does seem similar to me...which i should add that i like this approach.
- rglullis 5y ago
  Interesting. I have taken a look at SOLID when it was first announced, but there wasn't much there, there. Now, seems like now they've progressed quite a lot! Multiple server implementations, listing of service providers... for all the talk about how committees can not deliver, it seems they are miles ahead of the Bluesky people in realizing their vision.
- cxr 5y ago
  One of the problems with Solid is that it's definitely guilty of the sort of criticism that surfaced (brought up by a reader) in related to some of the things discussed in an earlier post about "Library JSON" <https://tomcritchlow.com/2020/04/15/library-json/ https://tomcritchlow.com/2020/04/15/library-json/>: > That said, the thing that kills the indieweb is too much enthusiasm for specs, too few[...] implementations, and, ironically, too much focus on the ‘indie’ (building complicated self-hosted everything-machines) and not enough on the ‘web’ (noticing if anyone’s using any of the things you built). So if there’s a killer implementation and good content at the start, then momentum would potentially just carry you through. One thing I'm fond of is a turn of phrase earlier coined by Noel De Martin, a contributor to Solid: "Autonomous Data". The intention to put resources behind "Autonomous Data" as a brand/movement was set aside to focus on the Solid effort instead. I think, though, that the term is well-suited for the rough ideas presented in this post. (Better than "triple entry blogging", in any case. Better than "Solid" or "Zero Data"[1], too, in my opinion.) 1. https://autonomous-data.noeldemartin.com/ https://autonomous-data.noeldemartin.com/ 2. https://0data.app/ https://0data.app/
  - mxuribe 5y ago
    Agreed with your comment on autonomous data; and thanks for sharing that link, info!

mxuribe 5y ago

I think Tim Berner-Lee's SOLID project intends to - at least conceptually - provide the needs that you cited: https://solidproject.org/about https://solidproject.org/about Maybe the implementation layer details might differ, but it does seem similar to me...which i should add that i like this approach.

rglullis 5y ago
Interesting. I have taken a look at SOLID when it was first announced, but there wasn't much there, there. Now, seems like now they've progressed quite a lot! Multiple server implementations, listing of service providers... for all the talk about how committees can not deliver, it seems they are miles ahead of the Bluesky people in realizing their vision.
cxr 5y ago
One of the problems with Solid is that it's definitely guilty of the sort of criticism that surfaced (brought up by a reader) in related to some of the things discussed in an earlier post about "Library JSON" <https://tomcritchlow.com/2020/04/15/library-json/ https://tomcritchlow.com/2020/04/15/library-json/>: > That said, the thing that kills the indieweb is too much enthusiasm for specs, too few[...] implementations, and, ironically, too much focus on the ‘indie’ (building complicated self-hosted everything-machines) and not enough on the ‘web’ (noticing if anyone’s using any of the things you built). So if there’s a killer implementation and good content at the start, then momentum would potentially just carry you through. One thing I'm fond of is a turn of phrase earlier coined by Noel De Martin, a contributor to Solid: "Autonomous Data". The intention to put resources behind "Autonomous Data" as a brand/movement was set aside to focus on the Solid effort instead. I think, though, that the term is well-suited for the rough ideas presented in this post. (Better than "triple entry blogging", in any case. Better than "Solid" or "Zero Data"[1], too, in my opinion.) 1. https://autonomous-data.noeldemartin.com/ https://autonomous-data.noeldemartin.com/ 2. https://0data.app/ https://0data.app/
- mxuribe 5y ago
  Agreed with your comment on autonomous data; and thanks for sharing that link, info!