search

Chaosthebot / Chaos

A social coding experiment that updates its own code democratically.
http://chaosthebot.com
MIT License
2.44k stars 210 forks source link

Re Reopen #443 according to #364 - Twitter Api Working #550

Closed eamanu closed 7 years ago

eamanu commented 7 years ago

Fix encryptation problems, regenerate twitter keys @PlasmaPower

kylerchin commented 7 years ago

:100: Looking good! Any account name yet?

kylerchin commented 7 years ago

I can give you "realChaosBot" on twitter if you would like. ;)

eamanu commented 7 years ago

@kylerschin https://twitter.com/ChaobotsC

dbpokorny commented 7 years ago

@eamanu "encryptation" isn't a word, you mean "encryption".

@PlasmaPower are there plans to make the bot generate the encryption keys when it needs to by itself, without your supervision? I was under the impression that the encryption work was supposed to lead to that point eventually.

PlasmaPower commented 7 years ago

@dbpokorny What do you mean? It already generates its own encryption keys.

dbpokorny commented 7 years ago

@PlasmaPower oh dear, I thought @eamanu was asking you to regenerate the twitter keys and somehow send them to the bot. My misunderstanding.

PlasmaPower commented 7 years ago

@dbpokorny No, it was the reverse - I asked @eamanu to regenerate the twitter keys. :smile:

eamanu commented 7 years ago

@dbpokorny I write 'encryptation' repeatedly... My fouls. Sorry for my spanglish :laughing:

chaosbot commented 7 years ago

:white_check_mark: PR passed with a vote of 6 for and 0 against, a weighted total of 6.0 and a threshold of 6.0, and a current meritocracy review.

See merge-commit 6b112d023e337a6ed296b42502a1928e2055ecbe for more details.

mdcfe commented 7 years ago

This breaks dev environments almost completely, as ChaosBot tries to decrypt the Twitter token with the locally-generated private key, throws an error because it's the wrong key and crashes.