There is that side of things, but there is also the issue of community stuff too. The site is years old and doesn't even have a way of transferring subs, for example. If I combined the time, I probably spend more time waiting to receive/give subs than not. If you're working on other stuff, or don't have anyone who can build it for you, appoint someone to handle it for you. Even when moe was in charge of doing it, it still took weeks.
There is that side of things, but there is also the issue of community stuff too. The site is years old and doesn't even have a way of transferring subs, for example. If I combined the time, I probably spend more time waiting to receive/give subs than not. If you're working on other stuff, or don't have anyone who can build it for you, appoint someone to handle it for you. Even when moe was in charge of doing it, it still took weeks.
Voat lost motivated contributors because of the sub transfer problem. People can only wait so long before they need to move on to a different project.
I was having a whinge with some people waiting on transfers at the same time as me. Most gave up after 3 or 4 weeks and quit contributing.
Voat lost motivated contributors because of the sub transfer problem. People can only wait so long before they need to move on to a different project.
I was having a whinge with some people waiting on transfers at the same time as me. Most gave up after 3 or 4 weeks and quit contributing.
the api would have allowed some neat functionality and saved some bandwidth. The stats site i made had a bunch of the features built for a user hosted UI. Unfotuantely i dont know much about ASP.NET stuff.