TT,

I think I understand the point you are making, but being aware of the 
further shore is important, to ensure we do not compromise the future. Some 
one can set off for that shore when they please, but to know its there 
permits us to choose if we wish to learn to build a boat.

I am yet to understand the scripts on which it is driven but I would like 
to see it respond to content. Even just simply "how are you today?" "I am 
good and in edit mode", or "who are you", "I am wikititle".



On Sunday, July 19, 2020 at 10:59:25 PM UTC+10, TiddlyTweeter wrote:
>
> TW Tones
>
> As ever you reach for the further shore. In this case it is maybe 
> premature.
>
> The *.rive* scripting is well mature. The documentation is excellent. The 
> plugin simply instantiates it.
>
> The issue you getting at is whether we need "more".
>
> SO let us pragmatically see!
>
> My one practical comment to CB was to add a macro so we could do *<<chatbot 
> "$:/inter-act.rive">>.*
>
> I think, already, its a neat interface with a lot of intelligence. Deeper 
> integration with TW *will require understanding .rive scripts*, I think.
>
> Best wishes
> TT
>
> On Sunday, 19 July 2020 04:16:22 UTC+2, TW Tones wrote:
>>
>> Folks,
>>
>> On the chatbot, my thinking is how can we make the chatbot rely on 
>> content in a tiddlywiki, such as a knowledge base built with tiddlers 
>> fields and tags, perhaps TOC's or for example a genealogical tree such that 
>> the chat bot can be asked questions who's answers are sourced from the 
>> content of the wiki. eg; Does tony have an uncle, who are tony's aunts and 
>> uncles? Does fred have any living siblings? A bit like a Structured Query 
>> language in a chatbot.
>>
>> It would allow for another level of abstraction, that is given a 
>> knowledge base provide the user with a way to ask questions of it. I could 
>> imagine later even using this code, to code solutions at the higher 
>> abstraction level so rather than a list widget you use a query or question 
>> to list a set.
>>
>> To do this we need to find away to get the content to map to a data model 
>> that the bot can make use of and visa versa. The expert systems of old and 
>> the decision trees of big data and machine learning of today can easily be 
>> represented on top of tiddlywiki. It would be dreamy to allow these to be 
>> developed freely on tiddlywiki but then have a chatbot able to interpret 
>> plain language and respond with the knowledge. The 4th generation 
>> programming languages of the past which tiddlywiki, especially the list and 
>> set handling features is more than adequate for emulating, could be 
>> personified through a chat bot.
>>
>> Perhaps we first start with allowing the chat bot to respond to questions 
>> in tiddlywiki terms eg; have you any tasks due today, where "tasks" and 
>> "today" are defined, tasks defined by the wiki by the wiki designer, today 
>> as part of the tool set. So ideally we need to give the chatbot a way to 
>> look into the content, rather than put the content into the chatbot.
>>
>> Food for thought
>> TW Tones
>>
>>
>> On Thursday, July 16, 2020 at 3:19:55 PM UTC+10, ChristianB wrote:
>>>
>>> Hi All,
>>>
>>> I've created a chatbot plugin that would like to share with this group.  
>>>
>>> Its available here:  
>>> http://ceebeetree.tiddlyspot.com/#:%24%3A%2Fplugins%2Fceebee%2Fchatbot%2Fui%2Fchat
>>>  
>>>
>>> I'm interested to see what uses people can apply this to in their own 
>>> wiki's... at the moment the chatbot is using a very simplistic set of 
>>> responses that were available as a sample for the underlying AI library 
>>> (RiveScript) so it would be interesting what useful responses people can 
>>> program their own bot to provide...
>>>
>>> Also any review on the code is welcome - this is my first plugin I've 
>>> loaded to GitHub so happy to take on some push suggestions etc 
>>>
>>> Cheers
>>> CB
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/bafd2e59-8499-4c0e-88fc-9daf2f5333d4o%40googlegroups.com.

Reply via email to