3 ms·
We have actually tried to mitigate this with our knowledge-base solution[1] by using multi-parent nesting in addition to hyperlinking + backlinks (zettelkasten)
by fastball 6y ago
We have actually tried to mitigate this with our knowledge-base solution[1] by using multi-parent nesting in addition to hyperlinking + backlinks (zettelkasten).
On our platform, everything is a card (rather than a document), and if you want an actual structured hierarchy, you can nest cards inside other cards. Each card can have multiple parents, so if you are collaborating with others you can easily have the same "card" in different places to keep yourself organized. In that way it works similar to symbolic links in a filesystem, except it's nesting so there are no folders – just cards all the way down.
At the same time, because your cards are not actually siloed into different folders, we have things like the "home", which has all the cards you've ever made so that you can easily filter your entire library by tag / author / etc. and see all of those cards at once.
Unlike the OC solution, however, Supernotes is not self-hosted, and so probably isn't as appealing to a lot of the techie HN crowd.
[1] https://supernotes.app https://supernotes.app
- skinnymuch 6y agoI’m [very] interested. I saw your app before, but it was during my looking at so many different apps, I didn’t look too much into it. Being an HNer working on the product is a pretty big pro for me. Will be showing this specific comment to a few people for reference to Supernotes as well.
- fastball 6y agoGlad to hear it! Knowledge management is definitely a crowded space – probably because it's something that is almost universally useful to humanity if done "correctly". Being around HN for a while has definitely influenced how I think about the product and what I want to build. For a while I was wanting to build Supernotes as a federated service (and at some level I still want to do that), but for now the focus is mostly on making the most seamless UX.
- tmandry 6y agoYou seem to be hitting the nail on the head with regard to seamless UX. I’d gladly pay to support something like this, but the lock-in / “what happens if you go away” problem is real and holds me back from investing all my knowledge and time. Short of an actual federated system, a self hosted option OR just markdown export / backup of an entire database would completely alleviate that for me.
- fastball 6y agoSo we do currently have the ability to export all your cards as one giant markdown file. Obviously the issue with any sort of export with our system is that even if we export as markdown, the relationships don't really carry over into the export. But this is definitely something we are working to make as easy / thorough as possible. Data ownership by our users is very important, which we've spelled out in our terms[1] as well. [1] https://supernotes.app/terms/ https://supernotes.app/terms/
- chiefalchemist 6y agoNice. Very intriguing. Question: Do you have an option where your backend could be used to supply content to a frontend public website? Mind you, given your data structure, I'm not sure how that would work. Let me give you an example. I like to read, mostly long form non-fiction (i.e., books). Naturally, I highlight things of importance. I want to take those ideas and get them into something where I can organize, add categories and tags, etc. Yes. A basic WordPress site would be sufficient. But given a tool like yours, why not try to take up a level? On the backend, my "thoughts" well organized. The frontend some view of that I'd want to share with the public. Thoughts?
- fastball 6y agoThanks! And the answer to your question is yes, absolutely! Hopefully quite soon (we already have a working demo) we will introduce "card pages", which will be public (or semi-private, it'll be configurable) pages that represent either a card itself or that card's children. These pages can then be embedded into any other webpage. The idea is to both support behavior akin to embedding a tweet, where you are just viewing a singular card as a card, but also to allow people to effectively create "documents" on Supernotes (that can then be shared publicly) by displaying the children of a card in "seamless" mode, so that even though it's actually a bunch of cards under the hood, it'll look like a blog post, or wiki article, or readme, or whatever. Every card on Supernotes will be able to have multiple pages, so that you can have a truly publicly-facing representation (which might limit how people can interact with it) but simultaneously embed your card somewhere else that is semi-private (like a Notion doc for your team) and allow people to actually interact / edit the card from there.
- walterbell 6y agoThanks for supporting multiple-parent nesting, previously pioneered in Lotus Agenda and NetManage Ecco Pro. Bear Notes may have this as well.
- fastball 6y agoIt's an incredibly powerful pattern, so much so that I'm surprised by how little you see it in the wild. We've also combined it with collaboration functionality so that cards can not only have multiple parents but can have different parents for different users. This aspect might be novel – I don't think I've seen it elsewhere, but obviously it's hard to know due to the sheer number of productivity tools that have existed (as evidenced by you pointing to Lotus Agenda, which I hadn't heard of til today, thanks!)
- walterbell 6y agoIt's not for lack of demand. Mitch Kapor (Agenda) and Mozilla talent tried an OSS reboot, Chandler. It was so well funded and failed so spectacularly, that there's a book about it. https://www.amazon.com/Dreaming-Code-Programmers-Transcendent-Software/dp/1400082471 https://www.amazon.com/Dreaming-Code-Programmers-Transcenden... https://www.chandlerproject.org/vision/ https://www.chandlerproject.org/vision/ > cards can not only have multiple parents but can have different parents for different users. This aspect might be novel Very nice.