12:00 <tankf33der> today i think plio via pipes is ok

12:00 <tankf33der> as is.

12:07 <razzy> tankf33der: figured out how to use it?

12:08 <tankf33der> already used.

15:36 <rick42> sup peeps

15:36 <Regenaxer> Hi rick42!

15:36 <rick42> hi Regenaxer! :)

15:36 <Regenaxer> :)

15:39 <rick42> i saw namra's question about org mode (ob-picolisp), but i don't understand what the problem is.

15:40 <Regenaxer> Oh, and I understand it even a lot less

15:40 <rick42> haha

15:42 <Regenaxer> Lets see, semms he intends to post something to the list

16:04 <rick42> thorsten is the author of the ob-picolisp that is already included in emacs. no need to install third-party tool. neat

16:08 <rick42> never used it before, but i just tried it and it's working fine

16:35 <rick42> basic idea: https://i.imgur.com/5aUAnvo.png

16:41 <freemint> rick42, do you want to add that into vip or add that to emacs?

16:41 <freemint> Is seombody here interested/using Telegram?

16:45 <Regenaxer> cool

16:46 <freemint> I was looking at the Telegram API and adding a minimal PicoLisp backend would be very easy.

16:53 <freemint> if there is some interest in the community i would push it a bit higher on my priority list and i would like to discuss what is wanted

16:56 <Regenaxer> Sounds very interesting! What could be done with the Telegram API?

16:58 <Regenaxer> However, I would use Briar in the future and not stat with yet another messenger

16:58 <freemint> send messages to person and groups on telegram with *rich* content (pictures, videos, html5 games(?)), do questionaires (constraint user input, like only a number, or from a few choices), make payments.

17:00 <rick42> freemint: it's already in emacs. the window in the foreground is an emacs buffer; in the background is the browser's (Firefox in this case) rendering of the html exported by emacs (from that source in the emacs window).

17:00 <freemint> It is a simple web api, which allows to interact with a powerful client (the telegram app)

17:00 <rick42> briar looks very cool

17:03 <Regenaxer> yeah

17:03 <razzy> i am having blast with picolisp :]

17:03 <razzy> colapse-able code did the trick for me.

17:03 <Regenaxer> What kind of blast?

17:04 <razzy> through code.

17:04 <Regenaxer> good :)

17:05 <freemint> my ideas are for the telegram bot are 1. dumb interface (message "bla") '*Group1) 2. an http_server like setup (text is parsed in to commands triggering functions) 3. 2 but with addtional times/conditions/IFTT(if this then that) to make use out the "push" side of messaging and domain specific language to manage all that.

17:06 <Regenaxer> Dumb interface is the most useful I believe

17:08 <freemint> or to express in existing picolisp analoges: 1. 'client 2. @lib/http.l 3. @lib/form.l

17:18 <freemint> Well a 'client like wrapper is not very "interesting" if somebody has strong ideas about a Telegram bot send them even when i am not online. If not it ends up in the queue of ideas.

17:18 <freemint> afk