I like logseq because the "primitive" where they store/organize the data called a "block" which is pretty well thought out. It's just an object with content and a pointer to a parent. Seems like you could content hash it and store it on ipfs forever. Haven't fully thought out what that would look like yet though. It could be developed as a plugin for logseq. Seems like it could scale, lots of other problems like search though.
{:block/uuid #uuid "62a8318e-ff36-4f97-9ef5-f19c3f3041bf",
:block/left {:db/id 67152},
:block/format :markdown,
:block/content
"Users create a bio under a page called `[[logseq-social/profile]]`",
:db/id 67144,
:block/path-refs [{:db/id 20}],
:block/parent {:db/id 67160},
:block/unordered true,
:block/page {:db/id 20}}
The other dapp "primitive" I'm interested in is dChat. Seems like there could be some overlap between blocks and chat built on the same primitive.
For now, I'm mostly focused on getting technical users to just make their own personal sites since it's really easy with logseq and netlify.
I'm not a dapp expert at all (though I do host my traditional static site on ipfs https://gateway.pinata.cloud/ipfs/QmRDPhzAjBdBovPhhPKt4tanFp...)
Happy to hear from you and I'll definitely look into the lens protocol!