0
0

[–] where_is_my_vagina 0 points 0 points (+0|-0) ago 

Why not contribute to voat source directly instead of making a plug-in layer? Have I missed a discussion about it?

0
0

[–] travis [S, M] 0 points 0 points (+0|-0) ago 

You haven't missed an official discussion, but Voat is written primarily in a server-side language that I'm not familiar with yet. I'd love to contribute to Voat's source, but primarily I'm interested in churning out features that people are requesting over in /v/ideasforvoat and /v/voatdev that the devs don't have the time to add right now.

From the downtime recently I'm assuming the devs are focused on scaling Voat's infrastructure to cope with the site's sudden popularity. The way VES is licensed, anyone could copy-paste VES's code into Voat to add these features later or use VES as a springboard. There's also some stuff that wouldn't make sense to implement server-side, but that may be more opinion than fact.

I'd love it if I knew Voat's source, and I'd love it if the features of VES made it into the main codebase, but I'm going to wait and see how the site's development pans out first.

0
0

[–] where_is_my_vagina 0 points 0 points (+0|-0) ago 

FYI: source is here. I skimmed through a little, here's where CSS is located, and here's JS. Not whole source is server oriented, plenty of places to improve front end as well.