This is probably naive and looking forward to a correction; isn't sending your info to Claude's API (or really any "AI API") is a violation of your safeguarded privacy data?
Using AWS Bedrock is the choice I've seen made to eliminate this problem.
A hackable AI assistant using a single SQLite table and a handful of cron jobs
31–40 of 183 posts
Re: A hackable AI assistant using a single SQLite table and a handful of cron jobs
#32> It’s rudimentary, but already more useful to me than Siri! For me, that is an extremely low barrier to cross. I find Siri useful for exactly two things at the moment: setting timers and calling people while I am driving. For these two things it is really useful, but even in these niches, when it comes to calling people, despite it having been around me for years now it insist on stupid things like telling me there…
Clearly you need to make some slight spelling changes to your contacts... ;)
Re: A hackable AI assistant using a single SQLite table and a handful of cron jobs
#33> It’s rudimentary, but already more useful to me than Siri! For me, that is an extremely low barrier to cross. I find Siri useful for exactly two things at the moment: setting timers and calling people while I am driving. For these two things it is really useful, but even in these niches, when it comes to calling people, despite it having been around me for years now it insist on stupid things like telling me there…
I've had the same issues of decay. I used to be able to say "call Mom" but now it will call some kid's mom who I have in Contacts as "[some kid's] mom". What is the underlying architecture that simple heuristic things like this can get worse? Are they gradually slipping in AI?
Re: A hackable AI assistant using a single SQLite table and a handful of cron jobs
#34This is brilliant !
I am wondering, how powerful the AI model need to be to power this app?
Would a selfhosted Llama-3.2-1B, Qwen2.5-0.5B or Qwen2.5-1.5B on a phone be enough?
Re: A hackable AI assistant using a single SQLite table and a handful of cron jobs
#35This 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.
Re: A hackable AI assistant using a single SQLite table and a handful of cron jobs
#36This 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.
Re: A hackable AI assistant using a single SQLite table and a handful of cron jobs
#37Lately I have been experimenting with ways to work around the "context token sweet spot" of This works really effectively with thinking models, because the thinking eats up tons of context, but also produces very good "summary documents". So you can kind of reap the rewards of thinking without having to sacrifice that juicy sub 50k context. The database also provides a form of fallback, or RAG I suppose, for situatio…
I am excitedly waiting for the first company (guessing / hoping it'll be anthropic) to invest heavily in improvements to caching.
The big ones that come to mind are cheap long term caching, and innovations in compaction, differential stuff - like is there a way to only use the parts of the cached input context we need?
Re: A hackable AI assistant using a single SQLite table and a handful of cron jobs
#38This 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…
Ages ago, I proposed that the best CMS for a company would be one which used e-mail as the front-end: - all attachments are stripped out and stored on a server in an hierarchical structure based on sender/recipient/subject line - all discussions are archived based on similar criteria, and can be reviewed EDIT: and edited like to a wiki
My one concern there would be edits: a CMS needs to support easily making edits to content (fixing typos etc) - editing existing posts via email sounds like it would be pretty fiddly.
Re: A hackable AI assistant using a single SQLite table and a handful of cron jobs
#39This 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…
Ages ago, I proposed that the best CMS for a company would be one which used e-mail as the front-end: - all attachments are stripped out and stored on a server in an hierarchical structure based on sender/recipient/subject line - all discussions are archived based on similar criteria, and can be reviewed EDIT: and edited like to a wiki
Ha! I had the exact same idea! I still think it would be nice.
Re: A hackable AI assistant using a single SQLite table and a handful of cron jobs
#40This is probably naive and looking forward to a correction; isn't sending your info to Claude's API (or really any "AI API") is a violation of your safeguarded privacy data?
Only if you don't believe the AI vendors when they promise that they won't train on your data.
(Or you don't trust them not to have security breaches that grant attackers access to logged data, which remains a genuine thread, albeit one that's true of any other cloud service.)