Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Post mortem May 25 2021 #520

Merged
merged 1 commit into from May 27, 2021
Merged
Changes from all commits
Commits
File filter
Filter file types
Beta Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.

Always

Just for now

Post mortem May 25 2021
  • Loading branch information
Andrew Lee Andrew Lee
Andrew Lee authored and Andrew Lee committed May 27, 2021
commit eae127f52505d0b5d06af646582133ccaac47069
@@ -0,0 +1,29 @@
---
author: rasengan
date: 2021-05-26T21:00:00
slug: post-mortem-may21
title: Letter to freenode - Post Mortem of May 25, 2021
category: announcements
---


Greetings freenode users,

As you are aware, over the last few weeks, we’ve been seeing an increasing amount of spam from other networks intending to mislead and influence long term running projects, namespaces and channels into moving to another new network which was formed parallel to freenode. While group contacts from the channels did not contact freenode staff directly, we were rather surprised when we received reports of unpleasant elements operating in the background and influencing these projects, namespaces and channels with false information in order to harm freenode’s administration and staff members’ images and paint a false narrative altogether.

In conjunction with yesterday’s events, in retrospect, we should have handled the action of closing down channels slightly differently. Originally, we posted a draft policy revision and solicited feedback in #freenode-policy-feedback. After several days, we discussed various feedback internally that was given.

The intent of doing this was not an attempt of a hostile takeover nor hijack like many people are saying. Since certain projects were disrupting their users' ability to chat on freenode via mass kicks, force closures, spam, we decided to enact this policy in those places which were deemed in violation and could cause an issue later.

This comment has been minimized.

@alyx

alyx May 27, 2021

Perhaps it would be more clear if you updated this to "Since many projects did not want to deal with freenode under my regime and chose to leave, we decided to enact this policy to try as hard as possible to obscure this from our users."?

It may be beneficial in your goal to be open and transparent with your userbase.


We believe we should have done this in a much more communicative way to circulate the right message and keep things transparent which of course did not happen. As we move forward I’d like to fully assure you that we will be working in complete commitment to restore projects, namespaces and channels that were closed on accident as a part of this event and we welcome them to use freenode as before as their very own homebase.

Lastly, there are no excuses for this, and I’m willing to admit that I was wrong with yesterday’s move and apologize for the inconvenience that may have caused.

The freenode team is working in zeal to support everyone as much as we can and we sincerely request your support and cooperation to jointly move ahead positively.

Thank you for your support,

Andrew Lee (rasengan)

On behalf of freenode’s Administration & Volunteer Staff

ProTip! Use n and p to navigate between commits in a pull request.