Yes I can see what in the implementation stopped the voting, but just because the voting mechanism is implemented wrong, does not make it right.

Quote from the answer you linked to "and for being an active participant on E2E"

How can the inability to vote on slightly old posts match being active participants?

When you go look at very successful forums like stackoverflow, you will find that one of the things that makes it easy to find the answer you are looking for is the vote count, those votes grow over time making the common problems we all face stand out.

Example: This is the first time I am using a dual processor MCU from TI, and I will likely face some problems. And it is very likely that Joe was facing the same problem 5 years ago, asked a question on the forum and got a good answer.

During those 5 years 50 other people faces the same problem and managed to find Joe's question, and may 30 of them voted the answer up. So when I now turn up facing that same answer I see that one questions/answer stands out becuse of the many votes, I start my search by looking there, and would you know it, in 90% of the cases, I just saved hours of searching because the is my answer.

And as a bonus to allow voting over time, is the feedback to TI. Today you cannot see that a customer did spend a lot of time looking for how to properly start a debug session wilh dual processors, unless she actually post yest another question that yo have to spend time answering.And even if a lot of customers ask about the same thing, it will be with different wording, may different but related MCU's and so on. So if you want to find common problems for a device or for a device family it requires quite some effort from you to collect all those questions and pool them as the same problem.

With a well functioning voting setup, that includes the ability to vote as well as the ability to utilize the vote count in a search. You get all this data collection for free. You can now just go to the most voted Q/A's and see where you may have a problem in the documentation or design. And use this as a strong indicator as to where you can impact user value the most.

Example: You find that a Joes question get a lot of votes, looking into this you find that maybe you should add a description on how to do to this in the document list of those processors, and you can even then go back and see if this result in a decrease of new votes to that question.

So all in all, I can't figure out how this implementation can be right.

Hello Martin, 

 Again, thank you for detailing and expressing the reasons for allowing "votes" and I will pass this request on to the E2E managers.  

Thank you, 

~Leonard