devinsit

6 ms·

1.
Open Sourcing uFincs(blog.ufincs.com)
11 points by devinsit 4y ago|0 comments
2.
by devinsit 5y ago
This is basically the main reason why I built uFincs ( https://ufincs.com/ ) without any sort of bank integration. As a Canadian myself, the privacy implications of letting a third party like Plaid take my bank password to ge
3.
by devinsit 5y ago
I built uFincs ( https://ufincs.com ) basically because I got fed up with GnuCash's UX. It only supports importing CSVs right now, but I'm open to adding other formats. It's also a web app rather than a desktop app,
4.
by devinsit 5y ago
Thanks, glad to hear you enjoyed it!
5.
I won a month-long hackathon in 3 hours(onmattersconcerningmyexistence.com)
44 points by devinsit 5y ago|19 comments
6.
by devinsit 5y ago
Thank you!
7.
by devinsit 5y ago
Yep, that's basically how it's said.
8.
by devinsit 5y ago
Oh I'm well aware of the disconnect. I just disagree that there are only people who care about privacy to the degree that they have to self-host everything. I believe there's room to ride the line between being 'privacy-fir
9.
by devinsit 5y ago
Firefly III ( https://www.firefly-iii.org/ ) in particular is a pretty good self-hosted solution.
10.
by devinsit 5y ago
I totally understand that. And I knew, when making the decision to not do any integrations, that there's a ton of people just like you that value automating everything as much as possible. But I also made the bet that there would be pe
11.
by devinsit 5y ago
The marketing site ( https://ufincs.com ) uses React + NextJS + Tailwind. The app itself ( https://app.ufincs.com ) uses a design system that I built completely custom (with plain old Sass).
12.
by devinsit 5y ago
I can definitely see where you're coming from regarding the whole syncing thing. Personally, I've gotten into a habit of recording my transactions right after they happen (or at worst, at the end of the day), but somehow I get the
13.
by devinsit 5y ago
Yeah, deciding to go straight-shooter with some of copy was definitely a risk, but thanks for letting me know that you appreciate it :) And yeah, the pricing section could definitely be made clearer on that. Thanks for the feedback.
14.
by devinsit 5y ago
Privacy in the sense that, while the bank may own your data already, third-parties like Plaid do not. And at least up in here Canada, we're a bit weaker on the whole 'bank API' system, so it generally turns into a wonderful g
15.
by devinsit 5y ago
Yep, I agree. If you want perfect security and a 100% trust-less solution, then uFincs certainly isn't it. But I like to think that, at least when put in contrast with other products on the market, choosing to do these privacy/sec
16.
by devinsit 5y ago
Thanks for the feedback on the UI! Definitely put some time into trying to get that right. And yep, we have plans for dedicated mobile/desktop apps for sometime this year. Android will almost certainly come before iOS though.
17.
by devinsit 5y ago
Absolutely none at all! uFincs is all about manual entry (although CSV import + recurring transactions makes things a bit easier). I made a deliberate choice to not support any bank integrations for privacy reasons (although simplicity is a
18.
by devinsit 5y ago
Thanks! The app itself is all React + Redux + TypeScript. Backend API is Node + Feathers + TypeScript. So certainly nothing fancy.
19.
by devinsit 5y ago
Hey HN! I'm excited to (officially) show off the project I've been working on (for far too long): uFincs, a privacy-first personal finance app! https://ufincs.com Yes, it's another personal finance app. Yes, there
20.
Show HN: I built uFincs – a privacy-first, encrypted personal finance app(ufincs.com)
58 points by devinsit 5y ago|33 comments
21.
by devinsit 5y ago
The 'error', as you put it, is that the password change process (i.e. the changing of the KEK and the re-encryption of the DEK into the EDEK) all happens client-side (except for the part where we verify your old password against t
22.
by devinsit 5y ago
Hmm, that's a good question to add to the Security doc! Not quite. See, we make use of a scheme called envelope encryption. That means we have two separate keys: one to encrypt your data (the 'data encryption key' or DEK) and
23.
by devinsit 5y ago
Yep, I agree, it's a pretty big upcharge. That's precisely why our 'free tier' is the 'no account' option ( https://ufincs.com/noaccount ). I'm not kidding when I say it's the full vers
24.
by devinsit 5y ago
As I replied down below ( https://news.ycombinator.com/item?id=26972907 ), I don't have any concrete plans to open-source it at the moment . However, I know this is a pretty big sticking point for some people, so I have
25.
by devinsit 5y ago
It definitely isn't. At least, not yet. I've been thinking through different ways we could handle that aspect, but I don't have any concrete plans to open-source uFincs at the moment.
26.
by devinsit 5y ago
That's the thing, the key isn't controlled by me. The key is derived from your account password. If you want some more technical details, feel free to check out https://ufincs.com/policies/security . tl;dr Y
27.
by devinsit 5y ago
Well, uFincs is a PWA, so you could 'install' it that way. We send a little in-app notification whenever a new update is pushed, so you could theoretically just ignore those and never update to keep using that one version of uFi
28.
by devinsit 5y ago
Thank you!
29.
by devinsit 5y ago
That's exactly what uFincs is, a modern version of GnuCash! I had the exact same thoughts as you did :) The simple tech stack breakdown is that the client-side is React + Redux + TypeScript + Sass. Of note, I use redux-saga, which has
30.
by devinsit 5y ago
I agree. The trend of handing over all your data ( especially your financial data) to some nebulous service isn't exactly my favourite. Which is why I built https://ufincs.com , a nebulous service where you hand over all yo

More ›