in reply to Re^3: Chatterbot update
in thread Chatterbot update

The number of CB users is small. Those garnering up votes even smaller.

Just hardcoding those saints in a hash who where seen here in the last 2 years would certainly cover 99% of the cases.

I wouldn't fear a DOS attack here, probably cavac should rather be worried about PM's lag and downtimes.

Edit

Such a data structure holding "last here" might lead to another nice feature: 😃

A "Hello <MLX>! Long time no see" greeting 😉

Cheers Rolf
(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery

Replies are listed 'Best First'.
Re^5: Chatterbot update
by cavac (Prior) on Jun 21, 2024 at 08:13 UTC
      > Any ideas what threshold/timeframe would be appropriate?

      I think after parsing saints in our books you can just chart the "last time here" and visually come to one or various natural thresholds.

      Edit

      If I were you I'd put the whole table into an extra module which is imported by chatterbot and updated once per week.

      The threshold for greetings depends on frequency, at some point people might get annoyed by too many of them.

      I'd start with 6 or 12 month and would adjust those settings later.

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      see Wikisyntax for the Monastery

        I did some number crunching, to try to come up with something like $NORM for absence time. It turns out that there really isn't one. A human-factors approach is probably better. For you personally, after how long of an absence would you appreciate a "welcome back" message? I think for me it would be 12 months. Someone create a poll.

        12 months sounds good to me.

        BTW, the whole thing runs on a big PostgreSQL database, since it uses my PageCamel framework i also use to make other personal and commercial projects (created the whole thing from scratch since 2008; concepts and pre-projects go back to 2003 or so). There's no need to "create extra modules", this is something a little bit of re-used database magic and recycling of existing framework code can easily accomplish 😁. If, against all odds, the pagecamel framework doesn't have it, i can usually fish out something from the vast library(*) of my past and present projects.


        (*)
        $ du -hs src/private_mercurial 31G src/private_mercurial