Adding a .github folder to contain all the GitHub community files will help declutter the root of the project.

Files that can be added to the .github folder:

CODE_OF_CONDUCT
CONTRIBUTING
LICENCE
PR_TEMPLETE
ISSUE_TEMPLATE

Incoming PR for this as well 👍

Do you want to request a 🚀 feature or report a 🐛 bug?

(Write your answer here.)
minor bug

🤔 Expected Behaviour

(Write what you thought would happen.)
I thought i would go to the place i need to generate an api key but it leads to a 404 page.

😕 Current Behaviour

(Write what happened. Please add screenshots.)
I got a 404 page when i clicked on the 2nd ul in the contributing sections setup section of the readme. The ul that states "Generate your Sentiment API key here."

🌍 Your Environment

💻 Steps to Reproduce

(Write your steps here.)
click on the link in the setup section of the readme that states "Generate your Sentiment API key here."

💡 Possible Solution

(Write your solution here.)
fix the link to the proper url to generate a api key, i dont know which link that should be linked to but i suspect you do.

Thanks to @miljan-fsd from parcel-react-app for the template 👌

If the bot was to not use local storage via LevelDB then it could be turned into an immutable deployment with zeti's now.

On @kallaway request, will change the Slack Invitation Link back to the original link for 100DaysofCode Slack Channel since it is never expiring link.

@spences10 what do you think? A collection of emoticons with random tweets or one emoji for an individual tweet? 😀😁

I would like to add #301DaysOfCode to tweets so people following that track can join part of the larger FCC community.

Add Prettier badge

Add in the Prettier badge in the readme:

Add this line below the license badge>

[![styled with prettier](https://img.shields.io/badge/styled_with-prettier-ff69b4.svg)](https://github.com/prettier/prettier)

For the badge to look like this:

Label it as a good first issue and help wanted @amandeepmittal please

Also add in the Twitter follow intent button:

Adding the following HTML into the README.me

<p>
  <a href="https://twitter.com/intent/follow?screen_name=_100DaysOfCode">
    <img src="https://img.shields.io/twitter/follow/shields_io.svg?style=social"
      alt="follow on Twitter"></a>
</p>

You will have a follow on Twitter badge:

For replies from the bit suggest using in_reply_to_status_id: in the reply, this will give the user a bit of context as to why the bot is tweeting them with an inspirational quote. Example here:

bot.post('statuses/update', {
  status: '@ScottDevTweets I reply to you yes!',
  in_reply_to_status_id: '860900406381211649'
}, (err, data, response) => {
  if (err) {
    console.log(err)
  } else {
    console.log(`${data.text} tweeted!`)
  }
})

A modification on this will need o be added to the sentiment.js module

README pattern

Optimal README layout from Kent Dodds source:

1. Title + tagline + logo?
2. Badges
3. The problem
4. The solution
5. TOC
6. Installation
7. Usage
8. FAQ
9. Inspiration
10. Alternatives
11. Contributors
12. License

Check the condition if it's Day 1 or Day 100 to decide whether its first day or last day.
Also check the condition and exclude Day 10, no tweet should be sent on Day 10.

Looks like the Mashape API for sentiment has been down for the last few days now.

Not sure wen it's going to be back up 🤷‍♂️

Give #100DaysOfCode community members the option to opt out of receiving tweets from the bot.

They could just block the bot or mute it if they prefer but I think this will be a nice way to let users know that we're thinking of them and they can still follow the bot and see its posts in their stream so then be able to encourage other community members without getting tweeted at by the bot.

opt out reply 'something' to stop the bot

Something to that effect, this will have to go into a persistent datastore LevelDB is probably the best option.

Add Code of COnduct for the community profile of the project

Consider adding SuperCoderBot @heroes_bot to the user blacklist

Maybe add blacklisted usernames to the config.js files like in the example done for the twitter bot bootstrap

The current slack channel url has expired

This is a good first issue

Change it to 100xcode.slack.com

I got this to deploy, however it's acting strange,
it's starting to build okay, but gives me an error

(node:116) UnhandledPromiseRejectionWarning: OpenError: IO error: /home/nowuser/src/src/helpers/blacklistUsersDb/LOCK: No such file or directory
    at /home/nowuser/src/node_modules/levelup/lib/levelup.js:91:23
    at /home/nowuser/src/node_modules/abstract-leveldown/abstract-leveldown.js:41:14
    at /home/nowuser/src/node_modules/deferred-leveldown/deferred-leveldown.js:20:21
    at /home/nowuser/src/node_modules/abstract-leveldown/abstract-leveldown.js:41:14
    at /home/nowuser/src/node_modules/abstract-leveldown/abstract-leveldown.js:41:14
(node:116) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:116) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
No open port found. Make sure 'npm start' creates an HTTP server on a port (any).
More details: https://err.sh/now-cli/no-open-port-found
====================
TWEET COUNTER=100
====================
...

it seems to just loop with the tweet counter...

Any help would be appreciated!

Thanks!

Is there a way to promote use of the Slack channel via the bot?

Maybe have it as one of the automated tweets?

Here is the signup link: https://t.co/yEbhWEtFsv

I re-tweeted one user:
https://twitter.com/heyamberwilkie/status/818507978697506818

And the bot replied to me think that I am on my first day of streak
https://twitter.com/_100DaysOfCode/status/818512348080115713

And it kept up the conversation:
https://twitter.com/_100DaysOfCode/status/818512644994985984

I noticed that the Bot is twiting two time for the same person.

Maybe this could be pulled from an API

Maybe the quotes.json file could be made into an npm package?

Would be good for a first timer with reference to @amandeepmittal's stoic-api for reference?

Tweet in form of "#100DaysOfCode ......" is not retweeted
example, https://twitter.com/realslimshanky/status/816352899257102336

Please consider adding a development branch and possibly a branch for adding patches to

Also please consider adding the following protection on branches master, development and patch so they are protected:

Thanks

Node is defaulted to 8 in now so maybe do away with this if deploying to now with next release?

"engines": {
    "node": "~6.1.0",
    "npm": "~.3.8.6"
  },

Licence it's MIT, right?

Request for Comments

I'm thinking that we could have this added to a Travis CI workflow but I'm not sure on how it works with Heroku
https://docs.travis-ci.com/user/deployment/heroku/

Anyone have other suggestions, like deploying as an immutable deployment to now or surge??

What if we had something to where the bot would encourage someone to continue their 100DaysofCode? Maybe if they haven't posted in 7+ days and haven't posted Day 100 they would get a tweet mention that encouraged them to keep on going??

API keys in config.js again, I have submitted PR to use .env require('dotenv') so API keys can be ignored in future 😄

Added #53 for this

to keep consistent use of npm over all development modes and the introduction of package-lock.json since npm@5.

The contributing.md needs to have some work done.

Can I suggest adding in how to make a PR

Maybe take details from one of @QuincyLarson's Medium articles from the guides app?

Or point to the fCC Guides app locations??

Add CONTRIBUTING for the community profile of the project

This is a great one and fitting for freeCodeCamp imo

Thoughts on using bot.stream('statuses/filter' in place of search?

So, in place of having:

setInterval(retweet, retweetFrequency) 

Then the search function in the retweet module and the parameter passed in with the search terms. Why not have all the search terms in a search parameter?

const trackStream = bot.stream('statuses/filter', {
  track: trackWords
})
trackStream.on('tweet', retweet)

There would possibly need to be some form of filter so as not to RT absolutely everything that is tweeted, but with this method, we can track more than just 100DaysOfCode tag

Upgrade Node.js version to 6.11.1 to avoid vulnerabilities.
More information regarding this issue here.

It serves no purpose in the src folder as it's the images for the README.md would it not make more sense o have this in teh root directory @amandeepmittal?

In the current release First/Last Day check APIs are abandoned due to some issues. For more info on this, see issue #15, #24 & #50.

It is a suggestion of a project that one can develop on that day. It can be a simple things of a skill to develop through that 1 hour.

Issue

Basically had 24 notifications in less than 30 seconds and they were all from the bot mentioning me.

Possible Solution

Maybe we can teach it to only encourage once per day?

I am opening this issue to block Twitter accounts who spam #100DaysOfCode and are retweeted by the bot. Please list Twitter handlers here and will update the list in production either weekly or bi-weekly basis.

Check relationship and if user has already been thanked for following the account

This should probably go into one of the database enhancements as the info needs to be persisted.

Just a thought that the Twitter keys for this are regenerated and kept private so that someone with not the best intentions could post what they like?

As it stands anyone can take this code and post what they like to the @_100DaysOfCode account on Twitter

Maybe consider pushing some tags to make a release for this?

https://github.com/zeit/release#usage

I'm not sure if I make a release on my branch if it will be reflected on the fCC one

In the Medium article there's a call to arms where the user will tweet their commitment to the challenge:

I'm publicly committing to the 100DaysOfCode Challenge

The bot can reply with a welcome message, this is sort of an extension to the abandoned API:

#15
#66

This could be a quick win however by using stream.on('tweet' and match the specific (or exact) phrase

to avoid this:

==================== 
TWEET COUNTER=100 
==================== 
==================== 
TWEET COUNTER=100 
==================== 
==================== 
TWEET COUNTER=100 
==================== 
==================== 
TWEET COUNTER=100 
==================== 
==================== 
TWEET COUNTER=100 
====================

These parameters need to be tested 🙃

So as I understand it, 100DoC bot is calling functions in two differing ways which seem the samey

setImmediate(checkIfFirstOrLastDay, 720000);

bot.js#L148

And

setInterval(favoriteTweet, 960000);

bot.js#L93

and I'm asking for clarification here just as much as agreement but, is there not one way we could agree to use just one for consistency?

and also I have no idea what 960000 and 720000 milliseconds are and have to go convert them

can we agree on the

setInterval(favoriteTweet, 1000 * 60 * howeverManayMinutes);

So anyone reading can quickly see how long the interval is?

Thanks.

Using GraphCool to store the data the bot uses for things like:

• The Project of the Day, items could be tweeted sequentially and not repeated
• Inspirational quote items could be tweeted sequentially and not repeated
• Encouragement via the sentiment API could be better handled and use more than a key value pair
• Retweets can be checked so the bot is not retweeting a popular tweet

The idea is to use giphy translate endpoint to tweet relevant gifs.