Yeah I am now feeling like he is a pretty selfish person to keep Voat limping along. Time to call it a good run and shut it down already. He is just not ready to admit defeat.
Also there is a lot of broken stuff on Voat that has never been fixed. Like try going through the history of a user or a domain. For users it errors at page 20. For domains at page 10.
That was to stop sanegoatiswear from going into his deep history past page 50 and using alternate accounts to upvote his main account. He was not the only one doing it, but it also cut down on server bandwidth and processing costs to limit it. several spam bots started using this method as well, which was one of voat's many crashes.
It was not an ideal solution, but it was one of many stop gap measures that have piles up over the past 4 years. If poal takes off, it may need to do something similar to address the automated bot problem.
Interesting. Had not thought of that. Thank you for your reply!
the sad part of this issue is that there are 2 sides to this coin. Those who looked for the reason for this change and were around at just the right time to find it, and those who either never bothered, or found restriction and never found out about why. An F.A.Q. page could have had this as an answer, but with only 1 staff member, there was never time to compile one. Putting an F.A.Q. together as issues like this pop up could help with transparency, and if anyone asks about it just point them to the F.A.Q.
Half the problem with voat is most changes like this are not written down anywhere unless you can dig through the announcements or the admin's comment history, which this issue compounds if it falls past page 19...
(post is archived)