fanieldanara

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.

[1] https://www.ynab.com/blog/ynab-four-rules-less-stress

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>”.

[0] https://www.rfc-editor.org/rfc/rfc6750

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!

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!

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.

Thanks for sharing! SaaS only for the time being, but that could change in the long run. I'll send you an email, let's chat :)

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.

This is insightful for the long term, good thinking! Thanks for your feedback here.

Thanks for letting me know about the verification email going to spam, I will look into this. Other currencies are in the works! I'm considering other export options and I'll note your vote for CSV!

Thank you for your feedback!

Thank you for your feedback, this is in the pipeline but won't be ready until a later date. This is definitely a use case I have considered and would like to address.

I'll let anyone else chime in if they would like, but I wanted to note that Collections would be a good use case for this. If you add all of your work gear, you can add it to a "Work Assets" collection, that would be tagged on all of those items.

Thanks for your feedback! Currently USD is the default (and only) denomination, but I will be adding support for other denominations in the future!

Thank you for your interest! Happy to address your questions:

1. HomeSheet is currently free so I can gauge user interest and receive user feedback (Like yours, which I appreciate so much). After the early access period, I'm considering an annual subscription, and likely a free tier. This all depends on the infrastructure costs, etc moving forward.

2. I'm committed to a PDF export option to generate visual reports of your items. This isn't quite ready yet but it's in the works! Currently, I am able to provide a sqlite export of your data and a zip of your assets via a support request at this time, but I would like this export option directly in the app so it is available to you 24/7.

Encryption is an interesting use case I haven't considered yet. I'd be happy to explore what this would look like. My first thought would be to allow for client side encryption of any documents attached to your items, so things like vehicle registrations, bill of sales, etc. would all be encrypted client side. This is something I'll have to explore more, and likely would be added at a later date. I'm definitely interested though!

You could check out the LCD screens used by mSLA (Resin) 3D printers. They typically work by masking off UV light with an LCD