So about 30 minutes after I posted it I'm on the L and there's a train to Lorimer at in 8 minutes, train to Manhattan in 19 minutes. That's on the countdown clo

So about 30 minutes after I posted it I'm on the L and there's a train to Lorimer at in 8 minutes, train to Manhattan in 19 minutes. That's on the countdown clock. This will put the Manhattan train above the Broadway Junction. There's an announcement on the loud speaker that there's no service between Broadway Junction and Canarsie in both directions because of police activity. Two minutes later, according to the count down clock there's a train to Lorimer in 6 minutes and to Manhattan in 17 minutes. Followed by 5 - 16 and 3 - 13. There's still an announcement that there's no service between Broadway Junction and Canarsie in both directions. But there are magical countdown clock connected trains that will be now here in 3 minutes and 10 minutes. Oh wait, the magical clock is saying there's a train entering a platform! It is going to Lorimer and it is followed by a train to Manhattan! The clock is at zero and it is blinking! All aboard the subway track! This went on for about 40 minutes. Twitter says there's no service. Countdown clock says there's a train coming! Google transit says there's no train. Countdown clock says there's one! And when the service was restored the countdown clock said the next train was going to Lorimer and it was finally 6 minutes away. Except that a train to Manhattan was pulling into the station. The countdown clocks are garbage because the only time that they matter is when there are sick passengers, police activity, mechanical failures and cascading delays -- otherwise we know the train will be here in about ~4-5 minutes and that's exactly the time when the countdown clocks cannot provide reliable information. MTA should finish that project and make it work. After that they can pick their next "digital initiative"