| Latest revision |
Your text |
| Line 35: |
Line 35: |
| | | | |
| | Re. "the next vote would occur sooner or later respectively": This doesn't make sense - by definition, the vote takes place at no fixed time. Everybody votes at different times, depending on when they feel like it's 9am. They could, if they wished, do this capriciously, with no relation at all to the previous day's vote. One possible outcome of this is that the consensus view could drift so far from that of some individual views that it becomes impossible to determine which 'day' they're voting in respect of, and therefore which vote they should be counted in.[[Special:Contributions/162.158.34.239|162.158.34.239]] 11:25, 17 March 2022 (UTC) | | Re. "the next vote would occur sooner or later respectively": This doesn't make sense - by definition, the vote takes place at no fixed time. Everybody votes at different times, depending on when they feel like it's 9am. They could, if they wished, do this capriciously, with no relation at all to the previous day's vote. One possible outcome of this is that the consensus view could drift so far from that of some individual views that it becomes impossible to determine which 'day' they're voting in respect of, and therefore which vote they should be counted in.[[Special:Contributions/162.158.34.239|162.158.34.239]] 11:25, 17 March 2022 (UTC) |
| − | :I see your point. If I was writing it, I'd suggest one of three alternatives.
| |
| − | :*The time that an otherwise consistent (possibly even 'accurate') voter votes is at variable times according to the Consensus Clock.
| |
| − | :*What it really means is that the votes are ''actioned'' (or processed, but see below) at Consensus Midnight (close-of-votes) which is going to usually be earlier/later than 24-hours after the prior C.M. point.
| |
| − | :*During the period of longer (or shorter) hours, for the Consensus adjustment, the vote that comes in three Consensus Hours before that day's Consensus 9AM will not actually be three 'real' hours before that point, and there is no indication that it will be back-adjusted, in case the Consensus Median Vote asked for 15 minutes earlier but might appear to be (say) 10 minutes earlier. (A vote that is deemed Consensus Median and 15 minutes later will ''always'' be intrinsically 15 minutes later.)
| |
| − | :But I don't think there'll ever be a problem deciding which day a vote is effective for (though it might be different from intention, for the more inattentive voters). My proposed implementation would be to assume a cut-off at (or maybe slightly before, depending upon overheads) C.M., with all votes now either held off or handed straight over to the next day's vote as very-early votes for the next 9AM rather than very-(very-very-)late votes for the one now being acted upon.
| |
| − | :A simple method that saves end-of-day time to process involves a chronological-queue of incoming votes. For every odd-numbered vote added to the tail of the queue, from the 3rd one onwards, a single recorded vote (the current earliest) is shifted off the head of the queue (to be recorded/archived, maybe, but no longer relevent to the result we will calculate).
| |
| − | :At the moment of tallying, the head of the queue has your median-vote. The next one waiting to be shifted, if it's an odd-length, the mid-point of that with the next one on if the queue is even-length. (If I've described/imagined it correctly!)
| |
| − | :This immediately sets the time-factor used to expand/contract the hours from 00:00 to 09:00 in the Consensus Clock to get 9AM to match the Consensus Median Plus 24 Hours.
| |
| − | :Problems with lag/latency of incoming votes (chronologically confirmed, at source, but late to be processed centrally) would be most important with those immediately around the precisely defined Median, when sheer weight of opinion suggests that it'll be the most busy, but there should be enough idle-capacity to insert or shuffle items into the right bit of queue before the Midnight point. Or maintain sub-lists (5 minute slots?) that are maintained and finalised seperately and then their number of entries reported as a simple digest so that the system knows that "the ''n''th point of the ''m''th array", and maybe the n+1th, or the first in the m+1th (if needed), is/are to be plucked out at Midnight and looked at.
| |
| − | :It really won't matter if a million votes come in at 23:59, so long as they are counted and have been at least balanced by a million earlier-votes from 00:00 onwards. But if valid and acceptable but ''very late'' votes filter through after a preliminary decision has already been made based upon a now pre-Median time-vote timing, the new (true) Median can be established within the first few minutes (or probably seconds, or even microseconds!) of the adjusted-hours and the adjustment-Rate simply re-adjusted accordingly to meet whatever the revised Consensus is (seconds later? minutes later, at a push?).
| |
| − | :It could not push the next 9AM beyond 24 hours from the vote-period's closing Midnight, and likely won't push it beyond the prior idea of what the Midnight the upcoming day would originally have, without serious mass-action to break the system.
| |
| − | :An example of deliberate breaking could be by coordinating ''everyone'' to seed a few heavily premature votes (so the next Midnight is sent close to 15 real-hours after the vote-close one, very compressed 0:00->09:00 upon the clocks) then virtually nothing until everyone else quite deliberately votes at a confirmable moment of 23:59:59 (or as close as feasible, without being next-day votes, whilst jamming the queue-mechanism and forcing delayed evaluation) to force the rapidly-compressed clocks to switch over to a snail-paced rate to compensate...
| |
| − | :...But that kind of coordinated civil-disruption wouldn't be suddenly conjoured out of nowhere. I would expect that there'd be plenty of forewarning that any particular disruptive strategy is being considered (or experimented with), and it also needs (almost) everyone to be striving to force the exact same scenario with easily detected coordination of instructions. Heavily outnumbering both honest-voters and those dishonest-voters contrarily inclined. Otherwise the effect is minimal, or even practically ineffective. [[Special:Contributions/172.68.229.27|172.68.229.27]] 21:39, 17 March 2022 (UTC)
| |
| − |
| |
| | | | |
| | Of course, before mechanical clocks, hours varied across the year. With 12 short hours each day, and long ones over night in winter and 12 long ones in summer, with shorter hours overnight. [[User:Arachrah|Arachrah]] ([[User talk:Arachrah|talk]]) 21:31, 17 March 2022 (UTC) | | Of course, before mechanical clocks, hours varied across the year. With 12 short hours each day, and long ones over night in winter and 12 long ones in summer, with shorter hours overnight. [[User:Arachrah|Arachrah]] ([[User talk:Arachrah|talk]]) 21:31, 17 March 2022 (UTC) |
