I know about piston, and you wrote it. I have been reviewing the code base recently. Why isn't it? Seems pretty trivial.
Would it not also be much more secure if software with this function could be run locally? Seems there is a big trust issue with a service like this.
If you want someone else to vote/post on your behalf, then you need to trust then entity. THere is no way around it.
Running to locally doesn't help you either, because you can't grow the numbers.
I can think of a distributed discovery process for agents and operators, but that still requires that others have posting/voting authority for your account.
Could individuals not run a piece of software that watches the vote stream and then votes when a specific person on a defined list votes?
Cross posting seems to be a similar issue, I actually already sketched out a program to do this.
Maybe I'm misunderstanding but it appears pretty straight forward. I only see unnecessary danger of centralizing this.
Also why are you allowing registration and sign up on a site without SSL? That is just simply reckless.
Also the SSL on https://panel.xeroc.org:4089/ is not setup properly.
And you probably should turn off tokens: Apache/2.2.22 (Debian)
Here is an exploit that works on that Apache version:
Thanks for your replies and I understand your concerns. Let me address them.
Sure, that can be done, but it requires additional efforts to be taken or an application to be run by the user. He also losses some time advantage.
As for xposting and upvoting, I think you missed a few essential points:
Apologise for that, I am working on this already!
The other issues, we have discussed on slack
looks like you have quite a few curators there for now.