Mikaela/mikaela.github.io
1
0
Fork 0
mirror of https://github.com/mikaela/mikaela.github.io/ synced 2025-02-16 13:31:00 +01:00
Code Issues Projects Releases Wiki Activity

blog: keep the ops opped

Browse Source 
closes #33
This commit is contained in:
Aminda Suomalainen 2015-04-01 00:59:03 +03:00
parent ec751a2482
commit 936ddf7bac
1 changed files with 28 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
_posts/2015-04-01-keep-the-ops-opped.md Normal file
View File

@ -0,0 +1,28 @@
---
layout: post
comments: true
title: "Keep the ops opped"
category: [english]
tags: [irc, english]
---
Why I think that you should keep the ops opped instead of following
freenode's recommendations.
*Tired blogging, this will probably have a need for lot of fixing after I
am more awake if I ever am...*
Is there issue with your channel? What will people do? They will go to
some other channel to say that there is spam on your channel forgetting
to ping you about it.
Yes, of course there is `/msg chanserv access #channel list`, but who
really uses that, especially from newer users? Probably no one and if
you have larger channel with multiple ops, it requires whoising the
whole lot of you to see who is not away and has lower idle time (even if
the idletime might not mean anything if the op uses OTR and other reasons).
And there is also the issue of having to trust services or your bots.
What if the services go down or netsplit and the same happens to your bot?
You are out of luck unless you had the ops opped in which case the outage
doesn't affect you that much at all.