Show HN: System for Private Data Management
github.com
github.com
I've used a few variants for "personal CRM / personal tracking"
(a) "Unix" approach: csv files & encrypted text files (e.g. credentials) with gpg. Searching using grep. Edit with Vim.
PROS: compatibility, CLI tools. cons: gets out of sync across devices, poor experience on mobile.
(b) tiddlywiki: pros: works on desktops, good search, cons: poor sync to mobile, poor ux on mobile.
(c) "Google Ecosystem" e.g. Keep (notes), Contacts, Keep (todos), Calendar – Pros: syncs everywhere, cons: apps are slow and limited; also lock in
(d) "Apple Ecosystem" – Notes, Contacts, Calendar, Keychain – Pros: good sync, responsive apps, Cons: lock-in.
A few "killer features" that I've been working on: (1) A dynamic "daily dashboard" that is a mix of metric graph along with easily manipulated spaces (like sticky notes, diagrams etc). Currently I use Quip for this.
(2) Cyclical relationship reminders (like fitbit exercise reminders, but for your relationships). e.g. "jenny's birthday is in 3 days" or "you haven't called your uncle in 3 weeks, schedule a call". A ring-based interface would be idea, with colors representing the health of that cycle.
I've thought on this a lot. Some key pillars (1) trust – the most privileged data deserves the highest level of protection
(1b) dynamic – users can manipulate and personalize as they would their home desktop & office space
(2) responsiveness – adding a contact or note should take < 100ms . Zero latency – as fast as a pen and paper
(3) cross-device consistency : a change should instantly sync across devices
(4) comprehensive search
(5) polished UX
(6) mind-map : notes, contacts, events, reminders, photos should all link into each other.Can you talk more about your flow, including what tools you use ? I'm mostly curious about editing text gracefully on mobile devices.
Keeping a node online is the hardest part, I used an old phone previously, now an old laptop as a nearly-always-on-node.
Since this is how I'm used to keeping track of code and configurations, the friction has been surprisingly low; I'd even go so far as to say I find it fun. I'm sure my specific setup is not what's right for everyone but it feels right for me and I think that's the whole point.
I track and note in the same way. This system let's you maintain you data in your private Github repo or local text files (which you can manage using Git, or anything else, yourself).
Note - still kind of work in progress software but worth checking out.
It's only for the testing purpose now, please don't write any serious notes without login."
I've tried managing a personal CRM in text files, but I struggle on getting a future proof structure. I'll have basic questions like: Should I have one file per relationship/person, or a directory containing files per encounter? An example from someone who has used it for some time would be great to have.
There is a lot of overlap in this category with the note-taking apps (Notion, Roam, zettelkasten) which have also seen a lot of activity recently... you can think of both of those categories as existing on a two-dimensional continuum of structured vs free-form and statically structured vs dynamically structured data; the OPs app is near the statically structured corner of this space, and "just a bunch of text files" in the dynamic free-form corner. The other two corners may be defined by more dynamically structured note-taking/outlining apps and on the static free-form side we might have things like "private data clouds" (Nextcloud for Open Source).
I’d argue that Docker just shifts the problem slightly, while introducing a new set of challenges. It’s unclear if the net benefit is even a positive number.
Even if one doesn’t intend to contribute to the core project, it’s going to be necessary to get a bit intimate with the stack over time: upgrades, the inevitable bug that requires some troubleshooting, etc.
I found the parent comment both reasonable and constructive.
You may not have the same concerns, and that’s perfectly ok.
That's normal, i know some ppl that use Node as Core, some Java as core, each one takes his own stack i guess.
433 (number of files in project with .php extension)
> Isn't this more of a proof of concept.
Was that a question, or a statement of fact?
That off topic point aside, the point of doing this would be to own your data (at least that’s my attraction to setting this up). Why set this up in Notion?
P.S. apparently you can just use admin/admin and this will log into a demo session, wasn't clear from the login form!