With the rise of messenger apps it appears that chatbots are becoming (again) a user interface for almost anything.
Now, thanks to the awesome Bot-API which is offered by the cloud based Telegram messenger service and the Telegram.Bot C# API, you can now build your own Telegram chatbots within VVVV using these plugins.
Well, messenger apps are super simple to use and offer quite easy options to capture and send/receive media. By building a chatbot within VVVV you can easily get data in and out from your patches using your mobile phone or whatever Telegram client you are using.
One can think of many applications where a chatbot could be of great use:
Nothing new, to be honest, but the simplicity of the interface of a chatbot is just striking.
All web operations (connect, send, receive) happen asyncronously and most nodes are spreadable with regard to the BotClients.
Have a look at the patches inside for more details.
Telegram.Bot uses Newtonsoft.JSON in version 9 (vvvv-telegram 0.1) and version 11.0.2 (vvvv-telegram 0.2). As some other plugins/packs also use this library (e.g. vvvv-Message, vvvv-Time, ...) there might be dll conflicts resulting in exceptions during use. Be sure to scan your repositories and packs for this dll and remove the older versions. Sorry for this, but it seems there is no other way...
CC-BY by motzi(Matthias Husinsky). If you are using these plugins in an application of yours, be so kind and send me a photo or pointer to a description of your work. I'm just curious how you use this :)
awesommmmmme contrib, opens a lot of possibilities, thanks motzi !
Just one thing : the \plugins folder should be placed inside a \nodes folder, otherwise nodes won't show up in the nodebrowser :)
@sebescudie: thanks for the hint. but iirc putting this into a "nodes" folder is the way to go for a pack. i wanted to release this as plain old plugins that you can put into your contributions plugin folder (the one you can reference in the root patch). in there it should just work (like "vvvvContributions\plugins\vvvv-Telegram\plugins...").
would you think that the nodes would make more sense as a pack?
@motzi oh, sorry, I instinctively assumed it was a pack since I don't use the contribs folder that much.
I don't know if it would make more sense as a pack... there seems to be quite a large amount of nodes and some cool examples that could fit in a \girlpower folder, I guess that's why it felt like a pack to me rather than a simple plugin contrib.
I love Telegram, and this rocks! Thanks a bunch!
wow thank you ¡¡
very easy to use and amazing fun way to interact with vvvv, thx
Can I use Socks5 for bot?
just to let you know
if a disconnection occur and you try to reconnect the BotClient
an error message popup and freeze the patch until you click continue
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Net.WebException: The remote name could not be resolved: 'api.telegram.org'
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
@dr_quatz : sorry for replying late - no socks5 for now, that's not implemented
@guest: are you running an alpha version of VVVV? in betas exceptions should not block the running patch. or you can start an alpha via commandline parameter /showexceptions false (see here commandline parameters)?. does this help?
Beta36 shows the exceptions dialogue no matter what the parameters are.
I tried to run this patch with such versions:
I tried to run on 3 different computers.
I get the same error.
is there a solution to this problem?
@io: i did not run into this issue until now but will look into that. also, i'm working on the next version, based on a newer release of the base-library and VL-based. no ETA though...
Hmmm, this has been working fine for me up through 50beta35.8_x64, but now throws an exception under 50beta38.1_x64. This is on Win10 Enterprise on multiple machines:
Bummer, as running a bot to query status has been incredibly useful.
@mediadog - please check again the newest version 0.2, which should work again from beta37 and later. feedback welcome!
anonymous user login