Almond – The Open Virtual Assistant
almond.stanford.edu
almond.stanford.edu
> Do away with the complex UIs of IFTTT or Zapier
The interfaces on those sites can be complicated because the services they interact with can be complicated.
This was my demo experience with Almond:
> me: post a tweet about cats
> Almond: What caption do you want? [list of boxes of choices]
The choices are: - Use the image id from Thecatapi - Use URL from Thecatapi - Use description - Use the link from Thecatapi - None of the above
To me that is a "complicated UI". If I'm non-technical I have no idea what a URL is. Even as a technical person I don't know how "link" and "url" are different. I have no idea what "Thecatapi" is, why it was chosen to fulfill my request, or what it will tweet about.
I can see how this may be useful for tech people but this strikes me as more of a super high level programming language than an actual assistant.
"NOTE: using the embedded Thingpedia is not recommended. Instead, you should rely on the publicly available instance at https://thingpedia.stanford.edu."
While I'm happier relying on an institution such as Stanford rather than a random company, I'd rather self host everything - doesn't that kinda defeat the point of this?
I was hoping it would be "easier to set up than ifttt" as well as allowing live commands.
But it seems way too rough to be working properly. But it didn't connect to google contacts, an SMS=> Email integration with gmail failed, I can't get crypto currencies...
I cannot tell if Almond is fully OSS.
From Almond's website: > Almond is free software, and is available on Github. You can download, distribute or modify Almond as you see fit.
I couldn't find it now.
ALSO: commits actually go back to 2016, so it's been worked on for a while.