ibGib's current web app used today by my girlfriend and myself for personal logging while our shower is getting remodeled: <a href="https://www.ibgib.com/ibgib/Saturday%20II%5E818E0366E6B009CA0F71083DDD001EC99E5B0E708795B9F7FDBBF43C29225220" rel="nofollow">https://www.ibgib.com/ibgib/Saturday%20II%5E818E0366E6B009CA...</a> _(NB: After a temporary session "login" at the bottom of the page, you will be redirected...also, the links are long because the last part of it is a sha-256 hash that guarantees the integrity of the content of the ibGib data)._<p>I post this because I think personal logging is a perfect fit for ibGib's engine (and it's partly why I've written it), and it may interest you as a back end. It would allow you to basically have a graph database for a back end, while also allowing you to create and evolve your semi-structured data much like evolving an Event-Sourcing event in version control like Git (since each and every datum is versioned and maintains a complete audit history). It also is designed to be Big Data friendly, with the ibgib website's datastore acting with <i>completely</i> Open Data.<p>Also, I wanted to mention that I've actually used it recently in the exact use case given by @TACIXAT where I was walking my dogs in my neighborhood and I wanted to be sure I remembered the neighbors' names down the street when I met them a month or two ago (<a href="https://www.ibgib.com/ibgib/Walk%5EE3EE1755557357849C41C151117424D87EEB806D28216987B0F92F71ED1A2A39" rel="nofollow">https://www.ibgib.com/ibgib/Walk%5EE3EE1755557357849C41C1511...</a> - just doule-click the big yellow circle). I definitely like how the socialite app looks, and it's great in that it helps you remember things <i>in context</i>. This is also what is primary about ibGib, allowing for pictures, text, links, etc., to be nested "inside" other "objects" (so each node acts as both a file with content and a folder with relationships to other nodes).<p>So for your personal logging, you could create a semi-structured "type" with your subject-verb-DO-etc. and then create instances of these. Then you can relate them via any named relation to any other construct (called an ibGib). So it's very much like a graph datastore that also has data hashing for all "children" nodes, which makes it a merkle graph. There's all sorts of neat properties, and like I said, I thought your use case would be a good fit for the engine. (Btw, the structure also lends itself to auto-generating dynamic and collaborative blogging from your data, e.g. <a href="https://www.ibgib.com/ibgib/WaffleGib%20Jr%5E59B6D3828D352091B0251F2A017511C2A681BE300E179398F4D7CB8BC56B650A" rel="nofollow">https://www.ibgib.com/ibgib/WaffleGib%20Jr%5E59B6D3828D35209...</a> or <a href="https://www.ibgib.com/ibgib/Grillin%20burgers%5E9E0151A452C17F5814602D9A119865A60E12E53E8A9819FFB41DE33C0D05CDBB" rel="nofollow">https://www.ibgib.com/ibgib/Grillin%20burgers%5E9E0151A452C1...</a>)