As I understand it, the vote is given by "lottery". If you contribute 5 DCR you have 5 chances to "win" the vote. If you contribute 50 DRC you get 50 chances.So it's possible for everyone to vote, but more likely the higher contributors will "win".Averaged out over many tickets, even a 5 DCR contributor will eventually get to vote.
Because Pi reads how many tickets you had locked 2 days prior to beginning of vote (this of course launched recently and so was not part of initial ticket splitting) the lottery the ticket-splitter uses is irrelevant. This means there exists currently a potential to "game" the system by being the majority contributor on multiple splits. Due to the extreme low volume of splits (less than 0.1%) this is not a "threat" that is high concern now, however MatheusD already wrote the "hack" version of a solution which could be implemented but requires changes to both the ticket splitter and the Pi system (allowing fractions of votes to be applied to Pi). I think that's a solid solution and for the purpose of budgetary governance superior to lottery in some ways.
Anyone know how the https://mainnet-split-tickets.matheusd.com/ site looks up the sessions? Is there an API you can access if you want to setup another monitoring system (thinking a telegram bot would be cool)