You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 20, 2018. It is now read-only.
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:
Define what you want to say
Camperbot echos it back in the current channel for review
!bigtext confirm to broadcast or !bigtext cancel or just do a new bigtext to update the message.
The text was updated successfully, but these errors were encountered:
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:
!bigtext confirm
to broadcast or!bigtext cancel
or just do a newbigtext
to update the message.The text was updated successfully, but these errors were encountered: