words:

help me

trigger adding environment variables [wiki]
which is obvious error. please fix that, it's annoying how much time we have to see this window

This is not currently used by FCC and I also don't think it's completely working. I propose removing this.

https://gitter.im/FreeCodeCamp/FreeCodeCamp?at=57edcc09d56b91170dfc75cd

When there are known issues on FCC, we sometimes need to make "Big Text" announcements across channels. It would be nice if we could use the Camperbot to simplify this.

Command

!bigtext <Message>
We want it to be impossible to accidentally use. The output formatting might be pre-defined, or allow for the user to enter arbitrary text and formatting.

Broadcast Scope

We probably don't need it across every possible channel, more like just the "Core" help channels and main channel. We're need a list built in to the system.

Important Security

It would be critical that this command could only be used by designated admins. I'm thinking these would be hard-coded in to the codebase to prevent hijacking.

This could potentially also be limited to only being executed from a single room.

It might make sense to have a two stage process:

1. Define what you want to say
2. Camperbot echos it back in the current channel for review
3. !bigtext confirm to broadcast or !bigtext cancel or just do a new bigtext to update the message.

Right now it only responds with the command eightball. It be really cool to be able to
Oh magic eightball, Should I go to sleep?

I think we can scope it to lines starting with Oh magic Eightball. Thoughts?

The following happens when two campers call up the code formatting wiki article at the same time (a common occurrence when someone doesn't format their code with markdown).

console.logs are not being written on the prod server. Need to look into this.

https://gitter.im/FreeCodeCamp/Casual

I was given points in this chat room for hangouts and camperbot gave me points... please fix

thanks,
Tommy

As suggested by @SaintPeter. Could also lead to confusion about what features are available where, so this is a feature we may want to approach with caution, but it's worth putting up for discussion.

Recently, we have made a switch to relative links in the FCC wiki. The links to other wiki articles, or fragmented links within same articles - are now relative.

However, the content in the chatroom would require absolute links. We need to have camperbot parse the links before posting, and add a constant URL string ahead of all hyperlinks.

If certain key words like "thanks" "thank you" appear in your code quoted between ``` ````, the camperbot still send brownies to people mentioned.

Too many times do users come into a channel and type 'help me' or something similar that generates a wall of text or any english word that happens to be a camperbot command.

Example:
!explain format
!help where art thou

Tests are passing and linting is good right now, so this should be a cinch to get set up. I'll play around with it tomorrow.

When the chat channel has high traffic Camperbot should be silenced from spamming mass body of texts to commit a CoC violation of spamming either on purpose, accidental or informational.

This could be also resolved with a prefix but combining both will keep the chat from being overloaded by a rogue Camperbot command.

Ex: If the chat is moving at a high rate, do not allow camperbot to spam more than 3 lines of text, no images, no gifs.

Trying to explain items in the staticReplies array fails with tried to linkify an empty item because there is no dashedName property, so the bot sends this:

Regular wiki item explain js closures

topicData {
  displayName: 'js closures',
  fileName: 'js-closures.md',
  data: 'example',
  dashedName: 'js-closures' }
Utils.linkify> link [js closures  [wiki]](https://github.com/freecodecamp/freecodecamp/wiki/js-closures)
Utils.linkify> link [read more about js closures on the FCC Wiki](https://github.com/freecodecamp/freecodecamp/wiki/js-closures)
GBot> out|  ## :point_right: [js closures  [wiki]](https://github.com/freecodecamp/freecodecamp/wiki/js-closures)
Closures are functions that refer to independent (free) variables. In other words, the function defined in the closure 'remembers' the environment in which it was created.
> tags: closure, javascript, js
:pencil: [read more about js closures on the FCC Wiki](https://github.com/freecodecamp/freecodecamp/wiki/js-closures)

staticReplies wiki item explain link

topicData try this [guide](http://www.freecodecamp.com/field-guide/all-articles).

I can try to take this one, but need feedback on how to handle. Link to the wiki home page for these, change how these are handled and not link to anything, something else?

When i type wiki no repeat.

somehow it got missed bottom ```.

When you know someone bring up the subject of my worst enemy (java) and I "cleverly" think "hmmm if I type explain java surely I will get a page telling this nice person about the horridness of java" but instead I got a page on javascript!

This makes me very upset for two reasons:

1. It made me look dumb (very bad time in my life).
2. java != JavaScript

It would be nice if we could do something about this atrocity.

Love,
CEREBR4L

https://github.com/FreeCodeCamp/camperbot/blob/master/nap/lib/bot/cmds/thanks.js#L139

Camperbot's wiki invocation (via such commands as explain, help, etc.,) results in, potentially, large wiki pages that can contain: multiple lines, static (or dynamic gif) images and other media that disrupts the chat window (both on desktop/ and mobile platforms). Would it be possible to limit summary to 2-4 lines and provide the actual link to the wiki?

Right now if you search for something using the wiki command and it's not found you get a message like this:

The URL is no longer valid because we turned off the main Wiki commits. Now you need to go through the PR process on the main Wiki.

Maybe we need an article on how to add articles? Anyway, we need to remove this message for now.

In the Gitter application, when I tried to paste a code, CamperBot's help link is this -
https://github.com/freecodecamp/freecodecamp/wiki/code-formatting

This should be changed to this - https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/code-format

I have noticed some time ago that there were changes in "Falsy bouncer" bonfire, it was named "Falsey bouncer" before.
Now people can't find these bonfire using command: bf falsy bouncer.
Changes in @camperbot code have to be made.

Project Ban Hammer

In order to facilitate troll extermination we need a system to promote campers to admins in Gitter without giving them write access on Free Code Camp org. We can do this. We have the power.

This will come in three parts.

• Promote CamperBot's github user to an owner on FCC org.
• Create a command where camperbot will enter the text /ban @<someUser> in all our main chat rooms.
• Checks if the user giving the command is a FCC admin (This will be a list on the server that will not be tracked here on the Repo)

When camperbot hit the cloudflare DDoS protection it stopped accepting thanks and would not recover without a restart. camperbot should be able to recover from an error like that.

This makes some of the tests incredibly brittle. Our build is broken again because the wiki changed. Tests that rely on wiki type data should have data mocked for them.

Was trying to give some kudos happy brownie points and camperbot isn't working.. So I tried some camperbot commands and nothing.

However, I'm not sure camperbot is expected to be in every room? I am just assuming he is..
if not, please ignore.

https://gitter.im/FreeCodeCamp/LetsPair

No more than X Thanks Yous per minute/hour/etc. Also, maybe no more than ?10? per thank you. Don't award any points at all if there are more than a certain number of @mentions in a message?

We had an issue where someone came into the main channel and spammed thank yous A LOT. It took a long time for Camperbot to process them all and could have acted like a DOS to the API and Camperbot.

Livecoding has officially been delisted

Camperbot is down across all the chat rooms since today (09/20), that I know of. Just FYI.

I've got an idea: camperbot will use 🌟 :star2: for 1000 brownies and above.

Currently:

⭐ 2468 | @abhisekp | http://www.freecodecamp.com/abhisekp

Improved:

🌟 2468 | @abhisekp | http://www.freecodecamp.com/abhisekp

Add this whenever you want, this feature isn't necassary. But I still want it to be added.

This happened in chat:

@rphares wrote:

tax @darrylpargeter @darrylpargeter @darrylpargeter

@camperbot responded:

⭐ 714 | @darrylpargeter | http://www.freecodecamp.com/darrylpargeter
⭐ 714 | @darrylpargeter | http://www.freecodecamp.com/darrylpargeter
⭐ 714 | @darrylpargeter | http://www.freecodecamp.com/darrylpargeter

Bug? I don't know. But yeah, That is an easier way to spam in chat.
Please fix.

As discussed earlier with @Rafase282 in the chat:

Camperbot will no longer be able to suggest any of the wiki articles including:

1. Solution hints
2. Rooms
3. Articles
4. Any other help topic

Hence the course of action is now to:

• Close all the open issues are pull requests with after a thorough audit.
• Fix any issues relevant to chat and clean up this repository of the wiki related logic.
• If it receives any command for wiki, respond with a migration message.
• Deploy the bot.

Note : Its functionality to thank people will remain as such.
But any relevant help links should be removed or changed to forum links if available

/cc @FreeCodeCamp/issue-moderators
Refer freeCodeCamp/freeCodeCamp#9731

This functionality will give superpowers to our dear @camperbot

The code in this repository should conform to the FCC style guide.

https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/Free-Code-Camp-JavaScript-Style-Guide
https://github.com/FreeCodeCamp/FreeCodeCamp/blob/staging/.eslintrc

Refer: ☝️ July 5, 2016 3:49 PM

The bot currently says "could not find receiver for user". It should provide a better worded error message when it can't find a user for brownie points.

Because this is just silly:

when you explain entries the footer edit link

goes here ->

https://github.com/freecodecamp/freecodecamp/wiki

eg
https://github.com/freecodecamp/freecodecamp/wiki/waypoint-bring-your-javascript-slot-machine-to-life

but maybe should go here?

https://github.com/freecodecamp/wiki

Add testing suite using Tape

We created a Room on GITTER and three of us colleagues have been added to it. In the "Activity" section, we would like to be notified of each other's completion of FCC challenges automatically. Can a "/notifyCompletion" command be created for this requirement?

It looks like copying example.config.json to config.json is breaking Travis CI tests. See PR from @abhisekp here (scroll down)

It's an easy fix. Move the example to config.json and update the readme. The code itself relies on config.json which is why the test fails.

It makes sense for users who don't need a custom bot user not to need to alter a config.json anyway.