My feature request is to include an option on a button made from choice skill, to redirect a link to an external url...

Here's a detailed explanation including screenshots

https://help.botpress.io/t/how-to-redirect-to-an-external-url-while-using-a-button-made-in-choice-skill/1791

This option will be really beneficial using choice skill buttons since at the moment, you can only add an ext

In https://github.com/botman/docs/blob/master/conversations.md all callbacks have no return statement (i.e. return null).
But in https://github.com/botman/botman/blob/75a2ed17b87f9ec286345972f8465342922ef074/src/BotMan.php#L491 we assume call was successfull if user function return true (and stop futher processing). Otherwise we go on matches process. It may lead to multi-match into one re

Following the documentation

https://botsharp.readthedocs.io/en/latest/installation.html

git clone https://github.com/Oceania2018/BotSharp
cd BotSharp
dotnet build -v m -o ../bin -c ARTICULATE

Fails:

PS C:\users\andre\BotSharp2\BotSharp> dotnet build -v m -o ../bin -c ARTICULATE
Microsoft (R) Build Engine version 16.4.0+e901037fe for .NET Core
Copyright (C) Microsoft Corpo

We've moved a command from one bundle to another, but you need to fully qualify the command still.

This shows up in two separate places, when trying to get help on the new command (https://github.com/operable/cog/blob/master/lib/cog/repository/commands.ex#L20 due to not checking for enabled I'd imagine) and when trying to run the new command (https://github.com/operable/cog/blob/master/lib/cog/

We can start with this
Charca/bootbot#67

Currently Program O uses MD5 as a hash function for passwords, but this function is outdated for a long time now and no longer secure. With the help of GPUs you can break MD5s easily in hours or days. That's why we should use newer and more secure hash functions like Argon2 or BCrypt which are available in newer version of PHP.

The documentation for deploying to Heroku here shows an out of date Procfile example. The correct Procfile should be:

web: bundle exec puma -C config/puma.rb
sidekiq: bundle exec sidekiq -C config/sidekiq.yml -q stealth_webhooks -q stealth_replies -r ./config/boot.rb

This is one of the breaking changes for version 1.1.0

Describe the bug
Cannot use 'cp' command while installing it on Windows.
It is needed to replace 'cp' with 'copy' in scripts written in package.json if an user wants to install botfront on Windows machine.

To Reproduce
Steps to reproduce the behavior:

1. Install choco
2. Install meteor
3. Install botfront using meteor npm install in Windows Powershell.

Expected behavior

Currently, the standard joe.ReceiveMessageEvent sent by all documented adapters does not specify whether the message is "private" (a one-on-one chat in Slack, a /msg in IRC, etc).

This can be useful in having handlers process commands differently (e.g. allow admin-level commands in direct chats) depending on the communication mode, without having to either parse the Channel or Data fiel

Expected Behavior

The backend development documentation exists and walks developers through concerns and tips.

Current Behavior

The document is an empty file with a header.

Instructions aren't sufficient to deploy as it misses a lot of steps. Actual deployment instructions are mostly the same as https://cloud.google.com/python/django/appengine

• A new botkit controller for Slack
• Updated HTML within ThirdParty/index.js
• At least boiler code for test suites.

Hi All,

First of would like to say that Ana Chat is an impressive project and I would very much like to contribute if there is a back-log you're willing to share.

I wanted to point out that there is extensive documentation missing on many aspects and hidden features in Ana Chat, for ex:

1. Usage of Nodes Variables
2. Using of API calls and usage of chat context
3. Querying and analyzing t

name: test
match: command
args:
  - var1

to

name: test
match: command
expose_args:
  - var1

This is consistent with expose_json_fields. So, any time we expose variable from within rules we would use the expose_ prefix.

As building it from sources it's right now the only way to run Xaktit, I'd move the Build Xatkit page out of the Developers resource menu and move it up to the beginning