Replies: 2 comments
|
Interesting! the automatic local -> local server might be sort of complicated, but I will have a feature where you can export whatever data you want out soon. |
|
Thanks for the quick response — I'm really glad to hear you're planning export functionality soon! I just wanted to clarify my use case a bit more: while manual exports are helpful for personal use, what I really need is automation, something that runs without any user interaction. So I truly believe a small addition to the upcoming exporting feature will do the magic — if the exporting can be run on a periodical manner, I can write a script to retrieve the data and complete my workflow. Let me know if that makes sense — I’d be happy to help test or give feedback as you develop this further. |
Uh oh!
There was an error while loading. Please reload this page.
I’ve been happily using Dayflow on my workstation, and it works very well for my personal purpose. Now, I’d like to set it up on my kid’s computer—of course with his explicit consent—so I can monitor his activity. To make this process seamless, I believe there’s a minimal set of features that could be implemented quickly by Dayflow.
In my vision, Dayflow could automatically and periodically send summarized result data to a local server in my house. Since the raw video footage is not useful to me, I’d prefer a clean, structured output like JSON or a similar lightweight format which is easy to consume and integrate, and I’ll handle the rest. That's it.
I think based on that, you can polish the product and go commercialized easily in the feature (huge demand for home and enterprise purposes). What do you think?
All reactions