That time when Voat was crippled and barely functional...
Posted: Tue Sep 28, 2021 3:25 pm
(Not quite a confession, but more to do with why Voat's set feature was disabled)
When Voat was having issue with listing submissions, where the subverse page failed to list its submissions, I was trying to recreate an alternative list view. It was done with good intention. But it ended up crippling (If I remember correctly, it crashed) Voat very badly. I had to send Putt a message to catch his attention
What happened? Voat had a set feature, where subverses could be included to form a set. When a user visited a set, such as default set, only submissions from those subverses included in the set would be shown. This set feature was open to regular users, which meant that anyone could create the set in private or public sharable mode. Because Voat was not displaying properly, I tried to add almost every subverse into a user-defined set in public mode. I think the number of subverses was more than 8,000(edit: will have to check on this number). If I remember correctly, it did not manage to add all subverses to the set. The effect was that this set had created a completely different virtual view of '/v/all' equivalence. The server resource was crippled as it was attempting to populate this new '/v/all' set, alongside Voat's regular /v/all
When Putt arrived to the rescue, he tried to disable Voat's set feature . And he said that half of the site would not work properly when he did it. That was hilarious as hell... I think he eventually removed that '/v/all' set, before re-enabling the set feature. The user-defined set feature was eventually disabled as well. This was why we could no longer create user-defined sets, all because one nigger decided to fuck with the set feature.
I apologized to him in the chat, for creating such a mess. But he was cool with it . He even joked about how fuzzywords created an empty set that also caused a problem.
Fond memories of Voat, where Freedom of Speech once existed and thrived... Sometimes I wish voat.co or preview.voat.co were still there.
Edit: wow, Voat had 8000+ subverses!!
When Voat was having issue with listing submissions, where the subverse page failed to list its submissions, I was trying to recreate an alternative list view. It was done with good intention. But it ended up crippling (If I remember correctly, it crashed) Voat very badly. I had to send Putt a message to catch his attention
What happened? Voat had a set feature, where subverses could be included to form a set. When a user visited a set, such as default set, only submissions from those subverses included in the set would be shown. This set feature was open to regular users, which meant that anyone could create the set in private or public sharable mode. Because Voat was not displaying properly, I tried to add almost every subverse into a user-defined set in public mode. I think the number of subverses was more than 8,000(edit: will have to check on this number). If I remember correctly, it did not manage to add all subverses to the set. The effect was that this set had created a completely different virtual view of '/v/all' equivalence. The server resource was crippled as it was attempting to populate this new '/v/all' set, alongside Voat's regular /v/all
When Putt arrived to the rescue, he tried to disable Voat's set feature
. And he said that half of the site would not work properly when he did it. That was hilarious as hell... I think he eventually removed that '/v/all' set, before re-enabling the set feature. The user-defined set feature was eventually disabled as well. This was why we could no longer create user-defined sets, all because one nigger decided to fuck with the set feature.I apologized to him in the chat, for creating such a mess. But he was cool with it
. He even joked about how fuzzywords created an empty set that also caused a problem.Fond memories of Voat, where Freedom of Speech once existed and thrived... Sometimes I wish voat.co or preview.voat.co were still there.
Edit: wow, Voat had 8000+ subverses!!
