Ditto on YNAB! I started using YNAB a couple years ago now and it has fundamentally changed my perspective and relationship with money. The 4 rules of YNAB [1] really helped me conceptualize how to best take advantage of it.
Bearer indicates the type of credential being supplied in the Authorization header. Bearer tokens are a type of credential, introduced in RFC6750 [0]. Essentially the OpenAI api key you’re using is a form of bearer token, and that’s why the Bearer type should be included there.
Other authentication methods (like username/password or “Basic”) use the Authorization header too, but specify “Authorization: Basic <base64 encoded credentials>”.
I appreciate your perspective from already creating something similar, I'll consider this moving forward. More verbose audit logs are a great idea and I'll add that to the feature board, thanks!
I hear you loud and clear! This is the type of information I think everyone should have in their fire safe. The PDF reporting feature I'm working is great for the print it and put it in the fire safe use case. I've also come to learn that many others are interested in spreadsheet exports, too. This is a use case I want to not only support, but also encourage.
I can provide sqlite exports of your data via a support request at any time, additional export options are a priority for my next release cycle. If you want to shoot me an email at daniel@fanara.co, I'd be happy to reach out and let you know when these features go live!
The PDF export feature sounds great - but even something simpler like a CSV, JSON, heck even XML would give others a lot more freedom to handle the data however which they choose.
I'm definitely considering this, especially to enhance the in-app search for finding your items quickly. I like that you mentioned book ISBNs specifically as that's not something I had considered yet. Thank you for your feedback, I'll keep it in mind going forward!
FYI, most barcode readers just “type” the keys into the keyboard buffer or HID. You could literally just have a text input box (that honors enter key) to make it barcode enabled. Of course x-reference this info with something like the “what” database and you’d have great input.
I recall the "zbar" library being (relatively) easy to integrate and working damn well out of the box, on both iOS and Android, back in 2011 or 2012. I'd expect it's gotten even easier, if anything. It's been a while but IIRC you just find a way to hand it bitmaps from your camera, and it does the rest, spotting and decoding QR and bar codes.
Syncing between websites is certainly a long term feature that isn't quite on the roadmap yet, but data exporting certainly is. Right now I'm committed to PDF reporting, and I can also provide you a sqlite copy of your data via a support request (Although I am working to make this option available to users 24/7). I've also had others mention the desire for a CSV format, so I'll also be sure to think that one over as well. Thank you for your feedback!
This is a very interesting use case I hadn't considered. I think seeding and getting a working database of these types of attributes would be an incredibly large task, but I definitely see the value in being as specific as possible here. This may be a good opportunity for some user education on how to document their belongings, what types of attributes to note, etc. I'll keep thinking on this, thanks for your feedback.
this can be something where SaaS model works in your favor. Allow people to manually input qualities for an item, and then when someone else inputs the same product code it suggests those qualities to them
this way you can build a community consensus on top of whatever youre able to data-mine
I really like this idea and the idea of knowing exactly where all the rarely-used possessions are. Admittedly, this is a little bit outside of HomeSheet's use case, but I'll certainly keep this perspective in mind.
[1] https://www.ynab.com/blog/ynab-four-rules-less-stress
reply