IRC/LiberaChat suggestions #70

Open
opened 2021-05-22 19:57:31 +02:00 by Mikaela · 0 comments
  • @muppeth should setup automatic login to NickServ, because nicknames expire in ten weeks and at that points can either be requested to be dropped or get dropped during database cleanup which happened on freenode.
  • LiberaChat/freenode policies hide op status. I consider this as a difficulty to new IRC users and additionally it's incompatible with Matrix bridges. I have a short writeup on how to fix this here: https://mikaela.info/blog/english/2015/04/01/keep-the-ops-opped.html#fixing-freenode
    • this may already be fixed other than cs template as @muppeth appears to have +O
  • Currently only muppeth is an op on the channel, I think in the best case there would be several ops from different timezones. If my above instructions are followed, this can be fixed by /msg chanserv flags #disroot USERNAME AOP (if the templates aren't set, this will be missing auto-op).
    • while I have been an op on freenode since Oct 13 10:21:10 2017 according to freenode's ChanServ, I am not offended if you don't wish me to continue in the role.
    • to help avoiding freenode situation even more, some trusted users should be given additional flags of +sf to be able to use ChanServ SET command (+s) and grant others flags they have (+f) which when done at freenode would have helped me not be the only op.
      • see also /msg chanserv help flags
  • there is no topic set. I recommend /msg chanserv set #disroot keeptopic on which prevents it from disappearing even if the channel gets empty and /msg chanserv set #disroot guard on so ChanServ joins and stays on the channel.
  • tank[bridge] should be registered.
  • /msg ChanServ flags #disroot tank[bridge] +V in hopes to tell antispam to leave it alone should it flood, or at least give it a higher limits.
* [ ] @muppeth should setup automatic login to NickServ, because nicknames expire in ten weeks and at that points can either be requested to be dropped or get dropped during database cleanup which happened on freenode. * https://libera.chat/policies#nicknames * `Information on muppeth (account muppeth):` \n `Last seen : (less than two weeks ago)` this should always be `Last seen : now` * [ ] LiberaChat/freenode policies hide op status. I consider this as a difficulty to new IRC users and additionally it's incompatible with Matrix bridges. I have a short writeup on how to fix this here: https://mikaela.info/blog/english/2015/04/01/keep-the-ops-opped.html#fixing-freenode * this may already be fixed other than `cs template` as @muppeth appears to have +O * [ ] Currently only muppeth is an op on the channel, I think in the best case there would be several ops from different timezones. If my above instructions are followed, this can be fixed by `/msg chanserv flags #disroot USERNAME AOP` (if the templates aren't set, this will be missing auto-op). * while I have been an op on freenode since Oct 13 10:21:10 2017 according to freenode's ChanServ, I am not offended if you don't wish me to continue in the role. * to help avoiding freenode situation even more, some trusted users should be given additional flags of `+sf` to be able to use ChanServ SET command (`+s)` and grant others flags they have (`+f)` which when done at freenode would have helped me not be the only op. * see also `/msg chanserv help flags` * [ ] there is no topic set. I recommend `/msg chanserv set #disroot keeptopic on` which prevents it from disappearing even if the channel gets empty and `/msg chanserv set #disroot guard on` so ChanServ joins and stays on the channel. * [ ] `tank[bridge]` should be registered. * [ ] `/msg ChanServ flags #disroot tank[bridge] +V` in hopes to tell antispam to leave it alone should it flood, or at least give it a higher limits.
muppeth self-assigned this 2021-05-23 10:50:28 +02:00
muppeth added the
enhancement
xmpp
spam-protection
labels 2021-05-23 10:50:54 +02:00
fede added this to the (deleted) project 2022-01-07 22:44:54 +01:00
muppeth added the
refined
label 2023-11-08 22:35:40 +01:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Disroot/Disroot-Project#70
No description provided.