Show HN: Personal Data Management Dashboard
volmarg.github.io
volmarg.github.io
> The end goal is to have an application running on terminal or raspberry 24/7 plugged into my home network, without access to internet.
As far as I understand you're using it as the primary interface for all your data, but in case you want to import some external data sources too, you might be interested in a project I started [0]. You can take periodic snapshots of you online data, and then use it as a fully offline programmatic API to integrate with other services, and potentially use in your dashboard as well. Perhaps if you glance at the diagram [1] it might become clearer how it fits :)
i've done some similar kind of stuff with peloton / strava metrics.
EDIT: Also, you have a typo in "Powered by Symfony and Typscript"... missing the "e" in "Typescript".
You piqued my curiosity. Perusing the web I found a fun "typscript" job opening [0]. "Tyescript" also seems to be a hot topic [1].
[0] https://www.dice.com/jobs/detail/2608c733240961fea68d0c803a3...
[1] https://stackoverflow.com/questions/40863252/tyescript-how-t...
Might want to consider other acronyms.
But at the same time, giving the author a heads-up that they might inadvertently sort themselves in that group is, I think, a kindness.
As a woman, my first reaction to something being named "PMS", I'd book it in the "insensitive" category. I know lots of other women will too. We've heard a few too many PMS remarks from men to not have a reaction.
It's not just insensitive if it's insensitive to you.
Own it!
They should play on the acronym in very subtle ways. Icons that semi look like tampons and pads, slightly reddish hues, etc.
But keep it subtle.
You are in a super crowded market, and using something people are uncomfortable about, that they shouldn't be uncomfortable about is a great way to attract attention and keep you at the top of peoples minds.
I hate to bring node-bashing to this thread, but this further cements my dislike for the platform. I don't know why, but this happens much more often with node than Python or most other languages.
JS (and as such, node) developers seem to love breaking everything down into little tiny bits and then having enormous dependency fan-outs for everything.
With so many different parts written by different people, the likelyhood that any project with have a part that can be affected by any eratta change increases substantially.
------
I have a casual hypothesis that each person tends to settle with a subset of each programming language that they deeply internalize. As such, unless that one person is deliberately trying to, they're unlikely to write code that hits lots of the odd implementation corner cases that are natural in any language/implementation.
However, the subset each person settles on is different, so if you don't have some sort of overarching style/quality management, you will trend towards a project being sensitive to any change in any implementation corner as you increase the number of dependencies.
Dependency management (and possibly more critical, dependency quality) is becoming more and more important as things become more complex, and the tooling is not keeping up either.
I was wondering, are the tasks/notes/calendars/contacts all in your own system? Or can they be bridged using open protocols like CalDAV/CardDAV/iCal?
My current approach for building something like this is to build only the processing/dashboard side, and keep using Todoist for storing tasks, Google Calendar for calendars etc, and then piece by piece migrate to fully self-hosted solutions like Owncloud/Nextcloud that provide standard protocol based storage.
The main reason for my approach is that I do not want to implement Todo/Calendar/etc from scratch with UI's for every platform. Todoist works fine (and other open source CalDAV apps too), same with Google Calendar, so I want to get up and running using those apps on my phone, but still track the combined data in my own system.
Perhaps use different encryption types and password recovery mechanisms for different kinds of data. For example encrypt your forum passwords with an easily resetable pin, encrypt your Web banking details with a secure password(or 2fa) you can reset with a key you can print out and store in a safe. - Finally, support scripting so you can extend the app's functionality.
The one thing that will keep me using Monica instead of this is the ability to access my contact info and their birthdays using CardDav and CalDav. CalDav for the Calendar would also be very useful.
I recommend using 1password though. It has issues but is a solid piece of software that syncs to multiple devices.
Bitwarden has the advantage of being both self-hostable and being available hosted, and I found it to be similar enough to 1password to not substantially interrupt my workflow. In fact I was missing the URL matching feature in 1password (and their ages-old version of the public suffix list too).
If you're comfortable in the UNIX world, it's easy to migrate from all the big players, it's trivial to host the encrypted passwords on gitlab.com or git@tunnel-to-your-lan.com.
To me, the key differentiating feature, that made it better than bitwarden + co, is that it implements nothing on its own, it's just a wrapper around git, gnupg, etc. This also means that, 10 years from now, if you want to migrate to a hosted solution, you can (since everything is plaintext at the deepest level, migration-out should be easy).
It has mobile clients / multiple-device-sync, too. And it's easy to manage, because it's just git under the hood.
I hadn't heard of them before doing some deep searching in this space recently. It's a product with zero marketing budget, but a good-sized community, so you wouldn't hear of it unless you were googling search terms in the space.
First, the clients are open source, so you can scrutinize them to your heart's content. (also true with bitwarden, but the code surface area for BW broader)
The only compromising snippets would be code that tries to do i/o with a decrypted password, which shouldn't be too hard to grep the codebase for. But, yes, this is an insurmountably high barrier to entry for most people.
On the other hand, BW requires constant communication with an API Server, which is much easier to hide compromising code within. Using git to synchronize state, so that no network traffic with an API server is required, is an elegant security advantage to `pass`, imo. The trade-off is that your encrypted secrets are in each of your clients, and the implications of that should be understood.
So, you're comfortable with the code as it is today. What about a nefarious update, that introduces some offensive code? Since the apps are dead-simple, you can comfortably block the app from being automatically upgraded on your phone.
You'll bump into problems when you need to upgrade the app to be compatible with the latest OS, which means you have to redo your audit once-per-year at worst. But at that point, you should be able to do a `git diff`.
In the absolute worst case, you can fork the client, load the app, and make the necessary upgrades yourself. Although, again, this is an insurmountable barrier for most people.
I think self-hosted Bitwarden still has a large attack surface, because they're a .NET + SQLServer application, instead of a dumb wrapper around UNIX tools. Don't get me wrong, UNIX tools have a big surface area, but we're screwed in countless other ways if we assume they're compromised.
I think the trade-offs are pretty debatable in both directions, reasonable people can disagree on the best solution, and the right solution probably depends on the administrator.
Yup, I feel the same and Bitwarden checked the box hard for me long ago.
It would be awesome to link with Apple Health, since it already aggregates a lot of personal information.
The acronym "pms" just reminds me of "pre menstrual syndrome", and "personal management system" is not a very memorable, original or catchy name.
The logo of the product looks a bit akward as it reminds of a car company logo, and doesnt really communicate anything related to a management system.
The page doesnt look very coherent, with cartoonish drawings, a unmatching color scheme, several typos, and a logo which doesnt fit with the general look neither.
I dont mean to tear down the page, but I hope this can help you to design it to give a better first impression.
Edit: typos
Yeap I got this feeling about the logo as well, I was thinking about changing it, still might do. But the name remains :D
Thx.
It's designed for families and couples, more of a "household data management" solution.
Also, since this is HN, I'm looking for a marketing cofounder. And if any VC is interested, we are looking to raise our first funding round. Contact info is in my profile.
This thread on Reddit was enough to put off: https://www.reddit.com/r/selfhosted/comments/m9nfsi/self_hos...