1st world problems...
Buhu ma precious bullet icon... Buhu...
LeL
Buhu ma precious bullet icon... Buhu...
LeL
You're acting like lichess had no reason to make changes, which isn't true.
For example, bots cannot play ultrabullet because they get rate-limited.
Tor browser is not one of the recommended supported browsers.
Rating range: Stop peaksitting (high rated players making seeks for 1300 and below to remain on leaderboard without fear of losing points), make people to play people near their rating to keep it fair.
I could go on, but I haven't the time. At least think a little bit.
For example, bots cannot play ultrabullet because they get rate-limited.
Tor browser is not one of the recommended supported browsers.
Rating range: Stop peaksitting (high rated players making seeks for 1300 and below to remain on leaderboard without fear of losing points), make people to play people near their rating to keep it fair.
I could go on, but I haven't the time. At least think a little bit.
What about casual ultra bullet against bots? It was possible before.
Well, peaksitting works only if the game is rated, not casual. Fairness isn't really an argument, because 500 rating difference means already "no chance" and so there is no reason to forbid higher differences of rating. And anyway, people can also agree on unfair matches if they want.
Well, peaksitting works only if the game is rated, not casual. Fairness isn't really an argument, because 500 rating difference means already "no chance" and so there is no reason to forbid higher differences of rating. And anyway, people can also agree on unfair matches if they want.
Rate limiting:
Rate limiting is used to control the amount of incoming and outgoing traffic to or from a network. For example, let's say you are using a particular service's API that is configured to allow 100 requests/minute. If the number of requests you make exceeds that limit, then an error will be triggered.
Making it casual doesn't change anything.
Rate limiting is used to control the amount of incoming and outgoing traffic to or from a network. For example, let's say you are using a particular service's API that is configured to allow 100 requests/minute. If the number of requests you make exceeds that limit, then an error will be triggered.
Making it casual doesn't change anything.
here are more suggestions for various features - lichess.org/forum/lichess-feedback/quality-of-life-features
#1
4) Ultrabullet with bots was breaking bots by overloading the spam filter.
4) Ultrabullet with bots was breaking bots by overloading the spam filter.
Well, of course there's reasons for all these changes. I don't doubt that. But why the lack of official communication? Lichess has a blog and a message system, not to mention Twitter, Reddit, Facebook etc. Why not copy some of these answers to an official lichess medium, and fill in some of the gaps (like why the rating range control was changed).
9 bots posting in forums
#17 Honestly, I'm not sure. I personally don't handle PR promotional stuff, so I guess I refer you to lichess.org/contact#help-other-bug for more information.
@Toadofsky
I know that you have many occupations on Lichess and probably far more outside (IRL). I would be grateful if you found time to tell us what is (was?) the result of the discussion which you mentioned in lichess.org/forum/lichess-feedback/please-rollback-the-rating-range-change?page=7#69. Thank you, at the very least, for trying to achieve something!
#AbC
I know that you have many occupations on Lichess and probably far more outside (IRL). I would be grateful if you found time to tell us what is (was?) the result of the discussion which you mentioned in lichess.org/forum/lichess-feedback/please-rollback-the-rating-range-change?page=7#69. Thank you, at the very least, for trying to achieve something!
#AbC
This topic has been archived and can no longer be replied to.