Andrew Gray wrote:
You might want to clarify what "new and anonymous" means - is this going to be a time-lapse job like sprotection, or a manually enabled flag? Because people may well assume the latter, and SFAIK that isn't being considered...
O rly? I understood it would indeed be a "tick each and every edit before it shows by default" thing. I guess the feature isn't finished yet then.
(I like the idea of it being queued for approval for a few days and passing through then if it hasn't already - but note me not working on the code.)
- d,
On 30/08/06, David Gerard dgerard@gmail.com wrote:
Andrew Gray wrote:
You might want to clarify what "new and anonymous" means - is this going to be a time-lapse job like sprotection, or a manually enabled flag? Because people may well assume the latter, and SFAIK that isn't being considered...
O rly? I understood it would indeed be a "tick each and every edit before it shows by default" thing. I guess the feature isn't finished yet then.
I dunno, this is just the gossip I picked up. I may have entirely grasped the wrong end of the stick...
(I like the idea of it being queued for approval for a few days and passing through then if it hasn't already - but note me not working on the code.)
It's such a lovely comfortable club to be in, this one.
David Gerard wrote:
Andrew Gray wrote:
You might want to clarify what "new and anonymous" means - is this going to be a time-lapse job like sprotection, or a manually enabled flag? Because people may well assume the latter, and SFAIK that isn't being considered...
O rly? I understood it would indeed be a "tick each and every edit before it shows by default" thing. I guess the feature isn't finished yet then.
(I like the idea of it being queued for approval for a few days and passing through then if it hasn't already - but note me not working on the code.)
The exact details will depend on the community's discussion and decisions. Which of course is why a FAQ at this point is very hard to answer. ;) The question is still pretty open-ended.
But most likely there will be a combination of automated time delays, vandalism-detection heuristics, and of course manual checking.
Most importantly, please remember that the latest versions on any reviewed/approved/time-delayed/whatever page will *ALWAYS* be available to everyone, at most one click away.
-- brion vibber (brion @ pobox.com)
On 31/08/06, Brion Vibber brion@pobox.com wrote:
The exact details will depend on the community's discussion and decisions. Which of course is why a FAQ at this point is very hard to answer. ;) The question is still pretty open-ended.
The current wording of the FAQ, as far as I can understand it, appears very much more definite than you (the person writing the feature) seem to think it will be. I kept mine fairly vague on purpose, and from what you're saying it should be made more vague rather than less. Is this accurate from your view?
- d.
David Gerard wrote:
On 31/08/06, Brion Vibber brion@pobox.com wrote:
The exact details will depend on the community's discussion and decisions. Which of course is why a FAQ at this point is very hard to answer. ;) The question is still pretty open-ended.
The current wording of the FAQ, as far as I can understand it, appears very much more definite than you (the person writing the feature) seem to think it will be. I kept mine fairly vague on purpose, and from what you're saying it should be made more vague rather than less. Is this accurate from your view?
Yes.
In particular, the FAQ as you posted it seems to imply that this will be applied equally to every page, but that is not certain.
-- brion vibber (brion @ pobox.com)
wikipedia-l@lists.wikimedia.org