Skip to content
This repository has been archived by the owner on Oct 9, 2019. It is now read-only.

chatid can be left unstored without warning with forward slashes in group name #208

Closed
Mikaela opened this issue Sep 3, 2017 · 2 comments · Fixed by #228
Closed

chatid can be left unstored without warning with forward slashes in group name #208

Mikaela opened this issue Sep 3, 2017 · 2 comments · Fixed by #228
Labels

Comments

@Mikaela
Copy link
Collaborator

Mikaela commented Sep 3, 2017

     {
         ircChan: '#mer-meeting',
         tgGroup: 'Mer-meeting :: One-way connection, if you want to participate join on IRC at http://webchat.freenode.net/?channels=mer-meeting',
         tgGroupReadOnly: true
     }

This resulted to a lot of spam at IRC and SSHing in and trying to investigate the issue, I see that a chatid file hasn't been stored.

  • A lot of spam at IRC

I think the bot should possibly warn about chatid not being stored very loudly in the Telegram group or something so this wouldn't happen. The group in question has now been renamed.

@Mikaela Mikaela added the bug label Sep 3, 2017
@adedomin
Copy link
Contributor

adedomin commented Nov 4, 2017

it's not the length but the forward slashes, specifically the url scheme part in your telegram group name. I had planned on reworking the chatid storage but i never got around to it.

@Mikaela Mikaela changed the title chatid can be left unstored without warning with a long group name chatid can be left unstored without warning with forward slashes in group name Nov 6, 2017
@Mikaela
Copy link
Collaborator Author

Mikaela commented Nov 6, 2017

Issue renamed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants