Simple, elegant. If elinks or w3m has support for websockets the deal is just showing the board in an elegant way, which "terminology" (enlightenment terminal) does great.
I volunteer to write any relevant code necessary, preferably c or one of python, ruby. Anyone interested?
Simple, elegant. If elinks or w3m has support for websockets the deal is just showing the board in an elegant way, which "terminology" (enlightenment terminal) does great.
I volunteer to write any relevant code necessary, preferably c or one of python, ruby. Anyone interested?
yes, what are you talking about..?
yes, what are you talking about..?
I started something simple once https://www.youtube.com/watch?v=flEFJYqVcnE
Exited to continue on it, but I have other priorities at the moment.
I wouldn't expect those browsers to have websockets, and I'm not interested in that path either.
I started something simple once https://www.youtube.com/watch?v=flEFJYqVcnE
Exited to continue on it, but I have other priorities at the moment.
I wouldn't expect those browsers to have websockets, and I'm not interested in that path either.
Concern: Makes it even easier to cheat.
Otherwise it's a great hook that makes it (so much more) easier to use Lichess programmatically in the absence of a robust API. If you are indeed to implement it, I'm all ears.
Concern: Makes it even easier to cheat.
Otherwise it's a great hook that makes it (so much more) easier to use Lichess programmatically in the absence of a robust API. If you are indeed to implement it, I'm all ears.
flugsio: I can give a hand if you want. Is the code available?
Unihedron: I find your concern logical however decreasing the difficulty of cheating should not be the reason to deny such a useful feature imo.
flugsio: I can give a hand if you want. Is the code available?
Unihedron: I find your concern logical however decreasing the difficulty of cheating should not be the reason to deny such a useful feature imo.