#55 Clear todo instructions in case of spams on fedora channels
Closed: Moved 6 years ago Opened 6 years ago by amsharma.

We need to have a set of actions we can take in order to kickout spammers from fedora channels. It is happening more often now a days and not many people know what can be done. PFA
Screenshot_from_2018-02-01_12-52-50.png

We can have a page for these instructions and put the link in IRC topic space.


This should probably be addressed with the IRC SIG

Todo instructions should be
do /msg chanserv access #fedora-channelname list
then contact one of those ops
If there is an insufficient number of ops, ask an existing op that has +f flag to add more
If it is #fedora #fedora-social #fedora-unregistered #fedora-ops, there is a process to vote on adding more. The other channels, it is up to that particular team in Fedora to manage the list of their ops.

Thanks @nb for your inputs. I would like to know where I should put all this information which can be easily accessible by everyone. @bex any suggestion?
Should we share them on all MLs , wiki page or somewhere else?

Hi,

this will be part of an objective I'm working on. I will let you know when I have something more solid.

@amsharma +1 for wiki page note and then sending the link to mailing lists (diversity and possibly Irc Sig) to boost the visibility. Other mailing lists could potentially consider it as spamming.

@rhea how is it coming along? Can you elaborate a bit more?

Who are the ops for fedora-diversity and fedora-women? We should probably include those contacts on wiki page info too.

Metadata Update from @bee2502:
- Issue tagged with: easyfix, internal operations, meeting

6 years ago

Metadata Update from @bee2502:
- Issue tagged with: Open for voting

6 years ago

I believe the instructions link can also be included in diversity pages. I will take the task to create a wiki page for the instructions here and I will post the link here.

Metadata Update from @amsharma:
- Issue untagged with: Open for voting

6 years ago

Metadata Update from @amsharma:
- Issue assigned to amsharma

6 years ago

Metadata Update from @jflory7:
- Issue untagged with: meeting

6 years ago

Is this something the Diversity Team should lead?

When this ticket was filed, Freenode was being attacked by spam bots and malicious users. From what I've seen, this activity has subsided, so the urgency this ticket had is no longer true.

However, explaining how to respond with IRC commands is a helpful thing to do. I think this ticket makes more sense for the Mindshare Committee to work on, to help standardize best practices for managing Fedora IRC channels. If we implement this work in our group, there are surely other groups in Fedora that would find this useful.

Therefore, I recommend filing a new ticket to request standardized IRC moderation guidelines (i.e. how to ban, how to quiet, how to react to spam) with the Mindshare Committee and close this ticket as moved.

@jflory7 I think this might be better addressed with the IRC Support Sig instead of Mindshare, they could probably provide advice, although the IRC Support Sig by definition only controls #fedora, #fedora-social, #fedora-ops, #fedora-unregistered.

-ChanServ- Entry Nickname/Host Flags
-ChanServ- ----- ---------------------- -----
-ChanServ- 1 TaTiCa +AFRefiorstv (FOUNDER) (#fedora-diversity) [modified 2y 7w 5d ago, on Jan 22 12:06:28 2016]
-ChanServ- 2 nb +ARefiorstv (#fedora-diversity) [modified 2y 0w 6d ago, on Mar 09 20:12:46 2016]
-ChanServ- 3 nirik +Aiortv (#fedora-diversity) [modified 1y 43w 6d ago, on May 12 17:46:19 2016]
-ChanServ- 4 zodbot +Oo (#fedora-diversity) [modified 1y 43w 2d ago, on May 16 20:17:24 2016]
-ChanServ- 5 jflory7 +AFOfiortv (#fedora-diversity) [modified 17w 6d 19h ago, on Nov 10 19:30:08 2017]
-ChanServ- 6 !@irc-lug.rit.edu +Vv (#fedora-diversity) [modified 48w 0d 21h ago, on Apr 13 18:09:47 2017]
-ChanServ- 7 spot +AFRefiorstv (FOUNDER) (#fedora-diversity) [modified 17w 6d 23h ago, on Nov 10 15:49:43 2017]
-ChanServ- 8 meskarune +AORfiorstv (#fedora-diversity) [modified 17w 6d 19h ago, on Nov 10 19:29:55 2017]
-ChanServ- 9 jonatoni +AORfiorstv (#fedora-diversity) [modified 17w 6d 19h ago, on Nov 10 19:30:01 2017]
-ChanServ- 10 bee2502 +AORfiorstv (#fedora-diversity) [modified 17w 6d 19h ago, on Nov 10 19:29:59 2017]
-ChanServ- 11 puiterwijk +Aiortv (#fedora-diversity) [modified 8w 4d 18h ago, on Jan 14 20:38:45 2018]
-ChanServ- ----- ---------------------- -----
-ChanServ- End of #fedora-diversity FLAGS listing.

-ChanServ- Entry Nickname/Host Flags
-ChanServ- ----- ---------------------- -----
-ChanServ- 1 mizmo +ARefiorstv (#fedora-women) [modified 24w 6d 22h ago, on Sep 22 17:10:52 2017]
-ChanServ- 2 freenode-staff +ARefiorstv (#fedora-women) [modified 24w 6d 22h ago, on Sep 22 17:07:02 2017]
-ChanServ- 3 spot +AFORfiorstv (#fedora-women) [modified 24w 6d 22h ago, on Sep 22 17:07:02 2017]
-ChanServ- 4 Southern_Gentlem +ARefiorstv (#fedora-women) [modified 24w 6d 22h ago, on Sep 22 17:10:47 2017]
-ChanServ- 5 jflory7 +ARefiorstv (#fedora-women) [modified 24w 6d 22h ago, on Sep 22 17:10:57 2017]
-ChanServ- 6 nb +ARefiorstv (#fedora-women) [modified 24w 6d 22h ago, on Sep 22 17:11:01 2017]
-ChanServ- 7 nirik +ARefiorstv (#fedora-women) [modified 24w 6d 22h ago, on Sep 22 17:11:17 2017]
-ChanServ- 8 meskarune +ARefiorstv (#fedora-women) [modified 24w 1d 20h ago, on Sep 27 19:08:54 2017]
-ChanServ- 9 puiterwijk +Aiortv (#fedora-women) [modified 8w 4d 18h ago, on Jan 14 20:40:01 2018]
-ChanServ- ----- ---------------------- -----
-ChanServ- End of #fedora-women FLAGS listing.

@nb I'm trying to think of who can standardize and publish a list of best practices for managing channel bans, quiets, and moderation activities. Where should we direct this kind of request?

@nb so we should move this ticket from here to https://pagure.io/irc-support-sig ?
If that is the case then I will open new ticket there and close this one.
Please suggest .

Metadata Update from @bee2502:
- Issue tagged with: meeting

6 years ago

I filed a new ticket in irc-support-sig#197. Closing this ticket as moved.

Metadata Update from @jflory7:
- Issue close_status updated to: Moved
- Issue priority set to: happening now
- Issue set to the milestone: Fedora 28 (to May 2018)
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata Update from @jflory7:
- Issue untagged with: meeting

6 years ago

Login to comment on this ticket.

Metadata
Attachments 1