#37 New bridge request: @fedora / #fedora-telegram
Closed: complete by jflory7. Opened by michalrud.

Team/sub-project: Don't know what to put in here, it's the general @fedora group
IRC Channel: #fedora-telegram
IRC Nicks to ignore: none

Warning: @fedora on Telegram now has a public screening group and an "private" group to which everyone who has proven that they are not a bot are invited. The "private" group needs to be bridged. Group chat ID sent through the e-mail is - as far as I understand - the one corresponding to the private group.


Team/sub-project: Don't know what to put in here, it's the general @fedora group
IRC Channel: #fedora-telegram
IRC Nicks to ignore: none

Warning: @fedora on Telegram now has a public screening group and an "private" group to which everyone who has proven that they are not a bot are invited. The "private" group needs to be bridged. Group chat ID sent through the e-mail is - as far as I understand - the one corresponding to the private group.

Small correction: Everyone who has proven to be human AND has an interest in Open Source.

Hello, is this still desired? If so, I am going to assume:

Telegram: @fedora

IRC: #fedora-telegram on irc.libera.chat


Please let me know if this issue is still relevant and the above information is correct.

Metadata Update from @jflory7:
- Issue assigned to jflory7
- Issue priority set to: waiting on assignee (was: awaiting triage)
- Issue tagged with: type - existing bot

Merged via #48

Metadata Update from @jflory7:
- Issue close_status updated to: complete
- Issue status updated to: Closed (was: Open)

Telegram: @fedora

Keep in mind that this is just the screening group, which should not be bridged. Actual private group ID is different - it's not a supergroup - and was PM'ed to @jflory7 .

Metadata
Related Pull Requests