51–60 of 183 posts
I argue that this kind of tools are fun to play but in the end is it really helpful? I start my day like every day and on work I just check the calendar. My private calendar has all Information i need. Where is the gap where an Assistent makes sense and where we are just complicating our lives?
I argue that this kind of tools are fun to play but in the end is it really helpful? I start my day like every day and on work I just check the calendar. My private calendar has all Information i need. Where is the gap where an Assistent makes sense and where we are just complicating our lives?
Personally, this appears to be extremely helpful for me, because instead of checking several different spots every day, I can get a coherent summary in one spot, tailored to me and my family. I'm literally checking the same things every day, down to USPS Informed Delivery. This seems to simplify what's already complicated, at least for my use cases.
Is this niche? I don't know and I don't care. It looks useful to me. And the author, obviously, because they wrote it. That's enough.
I can't count the number of useful scripts and apps I've written that nobody else has used, yet I rely on them daily or nearly every day.
This made me think: what if my little utility assistant program that I have, similar to your Stevens, had access to a mailbox? I've got a little utility program that I can tell to get the weather or run common commands unique to my system. It's handy, and I can even cron it to run things regularly, if I'd like. If it had its own email box, I can send it information, it could use AI to parse that info, and possibly se…
Mailgun (and I'm sure many other services like it) can accept emails and POST their content to an url of your choice. I use that for journaling: I made a little system that sends me an email every day; I respond to it and the response is then sent to a page that stores it into a db.
This might not seem like much of a big deal. But as we transition to more of these #nocode automated tools, the idea of having to know how programming works in order to interact with an API will start to seem archaic. I'd compare it to how esoteric the terminal looked after someone saw a GUI like the one used by Apple's Macintosh back in the 1980s.
I looked forward to this day back in the early 2000s when APIs started arriving, but felt even then that something was fishy. I would have preferred that sites had a style-free request format that returned XML or even JSON generated from HTML, rather than having to use a separate API. I have this sense that the way we do it today with a split backend/frontend, distributed state, duplicated validation, etc has been a monumental waste of time.
This made me think: what if my little utility assistant program that I have, similar to your Stevens, had access to a mailbox? I've got a little utility program that I can tell to get the weather or run common commands unique to my system. It's handy, and I can even cron it to run things regularly, if I'd like. If it had its own email box, I can send it information, it could use AI to parse that info, and possibly se…
This project has a pattern just like that to handle the inbound USPS information: https://www.val.town/x/geoffreylitt/stevensDemo/code/importe... I think it would be pretty easy to extend to support other types of inbound email. Also I work for Val Town, happy to answer any questions.
TL;DR I made shortcuts that work on my Apple watch directly to record my voice, transcribe it and store my daily logs on a Notion DB.
All you need are 1) a chatgpt API key and 2) a Notion account (free).
- I made one shortcut in my iPhone to record my voice, use whisper model to transcribe it (done locally using a POST request) and send this transcription to my Notion database (again a POST request on shortcuts)
- I made another shortcut that records my voice, transcribes and reads data from my Notion database to answer questions based on what exists in it. It puts all data from db into the context to answer -- costs a lot but simple and works well.
The best part is -- this workflow works without my iPhone and directly on my Apple Watch. It uses POST requests internally so no need of hosting a server. And Notion API happens to be free for this kind of a use case.
I like logging my day to day activities with just using Siri on my watch and possibly getting insights based on them. Honestly the whisper model is what makes it work because the accuracy is miles ahead of the local transcription model.
I have built something similar that runs without a server. It required just a few lines in Apple shortcuts. TL;DR I made shortcuts that work on my Apple watch directly to record my voice, transcribe it and store my daily logs on a Notion DB. All you need are 1) a chatgpt API key and 2) a Notion account (free). - I made one shortcut in my iPhone to record my voice, use whisper model to transcribe it (done locally usin…
I have built something similar that runs without a server. It required just a few lines in Apple shortcuts. TL;DR I made shortcuts that work on my Apple watch directly to record my voice, transcribe it and store my daily logs on a Notion DB. All you need are 1) a chatgpt API key and 2) a Notion account (free). - I made one shortcut in my iPhone to record my voice, use whisper model to transcribe it (done locally usin…
Nice. Can you share?
On second thought -- apple shortcuts is really brittle. It breaks in non obvious ways and a lot can only be learned by trial and error lol
Edit: I just wrote up something quick https://simianwords.bearblog.dev/how-i-use-my-apple-watch-to...
This made me think: what if my little utility assistant program that I have, similar to your Stevens, had access to a mailbox? I've got a little utility program that I can tell to get the weather or run common commands unique to my system. It's handy, and I can even cron it to run things regularly, if I'd like. If it had its own email box, I can send it information, it could use AI to parse that info, and possibly se…
Mailgun (and I'm sure many other services like it) can accept emails and POST their content to an url of your choice. I use that for journaling: I made a little system that sends me an email every day; I respond to it and the response is then sent to a page that stores it into a db.
Yes. I know note taking and journaling posts are frequent on HN, but I've thought that this is the best way to go, is universal from any client, and very expandable. It's just not generically scaleable for all users, but for the HN reader-types, it'd be perfect.