---- Referring to another thread http://lists.wikimedia.org/pipermail/wikitech-l/2012-January/057720.html but i don't want to even more hijack jidanni.... and continuing http://lists.wikimedia.org/pipermail/wikitech-l/2012-January/057695.html under a new header -----
Ryan Lane wrote on Wed Jan 18 23:59:41
So, this will be my last comment on this.
In the time frame we had to implement this, it wasn't possible to do a 100% blackout that would have been completely impenetrable. There were a number of suggestions that could have blacked everything out completely, but very, very likely would have broken things in a way that would have lasted more than the blackout period.
Ryan, when i criticized the javascript implementation, i did not intend to be rude. I see now there might be a lot more considerations besides shocking visitors and editors, and there seem to have been not so much time too. Maybe i underestimated the task.
I am impressed that you tried to process input from 1700 participants. This effort should not go to waste.... I wonder, if this first step towards self-defense will be the last. You also mentioned lack of time and i believe that's always the situation. So, will there be any further evaluation of all this effort so far, of the decision process and its supervision, and the technical options for actual taking action, and then maybe deriving a first provisional guidelines ?
I do not imagine a catalog of predefined actions as that could turn out to be too predictable, but rather a catalog of possible goals and methods to achieve them, and possible technical implementations. But first before all, a guidance about the decision process, a supervision HowTo. I think that's the most difficult part.
Please understand me right. I don't want to urge. It is only a question, from a random outsider, and if you think it was useless, just skip it.
Ryan, when i criticized the javascript implementation, i did not intend to be rude. I see now there might be a lot more considerations besides shocking visitors and editors, and there seem to have been not so much time too. Maybe i underestimated the task.
I am impressed that you tried to process input from 1700 participants. This effort should not go to waste.... I wonder, if this first step towards self-defense will be the last. You also mentioned lack of time and i believe that's always the situation. So, will there be any further evaluation of all this effort so far, of the decision process and its supervision, and the technical options for actual taking action, and then maybe deriving a first provisional guidelines ?
Yep, that's a good idea. We have a log of what we've been doing, and we have a good amount of code written now as well. It's a good first step in documenting how to do something like this in the future.
I do not imagine a catalog of predefined actions as that could turn out to be too predictable, but rather a catalog of possible goals and methods to achieve them, and possible technical implementations. But first before all, a guidance about the decision process, a supervision HowTo. I think that's the most difficult part.
I think quite of bit of this can be predefined.
Please understand me right. I don't want to urge. It is only a question, from a random outsider, and if you think it was useless, just skip it.
It isn't useless. I'm hoping we don't have to black the site out again, but we should be more prepared for this kind of situation in the future.
- Ryan
Ryan,
Ryan, when i criticized the javascript implementation, i did not intend to be rude. I see now there might be a lot more considerations besides shocking visitors and editors, and there seem to have been not so much time too. Maybe i underestimated the task.
I am impressed that you tried to process input from 1700 participants. This effort should not go to waste.... I wonder, if this first step towards self-defense will be the last. You also mentioned lack of time and i believe that's always the situation. So, will there be any further evaluation of all this effort so far, of the decision process and its supervision, and the technical options for actual taking action, and then maybe deriving a first provisional guidelines ?
Yep, that's a good idea. We have a log of what we've been doing, and we have a good amount of code written now as well. It's a good first step in documenting how to do something like this in the future.
I think it could be collaborative work, but need a maintainer. A question of time i guess. Is there anyone in the position of doing it ?
I do not imagine a catalog of predefined actions as that could turn out to be too predictable, but rather a catalog of possible goals and methods to achieve them, and possible technical implementations. But first before all, a guidance about the decision process, a supervision HowTo. I think that's the most difficult part.
I think quite of bit of this can be predefined.
But what else should that be, besides take-down and alert banners ? I believe you first need to define the goals, for example, is it ok even to 'hurt' search engines and why (not). More generally, what's at risk and how much damage might self-defense cause. It is more like philosophy, not rules.
Please understand me right. I don't want to urge. It is only a question, from a random outsider, and if you think it was useless, just skip it.
It isn't useless. I'm hoping we don't have to black the site out again, but we should be more prepared for this kind of situation in the future.
Yes that was my idea too. Thanks for the answer.
wikitech-l@lists.wikimedia.org