New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Temporary Move Storage #11304
Comments
a large population like lichess user base, and a large feature set like lichess site, might provide for diversity of usage and use-case. It is possible that even a majority of users feel like you as they would also be using the same features as you. I comment here, not to deny your experience, but to propose a rewording of your issue that would not assume uniform needs and feature subset usage. lichess has forum where to first vent initial reactions. Perhaps just take out the first sentence, and all would be fine with me. not a dev, another fellow lichess user who actually need that feature, but not in the context you have shared. in that context I would actually agree that this feature might not be useful. I would also take out the last sentence. I am like you though. These vents do sustain the motivation to keep efficient at stating what a problem might be. but luckily, here, markdown and editable. once the dust settles. Conclusion: edit suggestion. trim first and last sentences and your issue is helpful feedabck i would say. |
feedback forum 2 threads related to this |
RE: user reload signal. |
Rephrasing without the criminal intent attribution: (I can do that too :) ) |
@Dboingue |
My suggestions:
If we want to leave this feature enabled everywhere, I think there's a strong argument that this feature should be controlled by an option.
If /analysis does not store moves locally, I think having an option is less important. |
I think We already have studies. What value does this add to the analysis board? It seems to me that it just blurs the lines between the two, when they were already great as separate entities. It's fair enough that some people like it, I can only speak for myself. But I'd like to respectfully request that Lichess at least includes a way to turn this off in settings. It is significantly degrading the UX for me. It also seems to be causing a raft of bugs for various existing features in Lichess e.g. importing FEN via URL. For me, the move numbers which are inset into the move list are rendering weirdly in correspondence games. After I click the 'play X and save premove line' button, the analysis board gets stuck in a repetitive loop of making the same move over and over again, to the point where even clicking the 'back to game' button does nothing and I have to close the tab! I think @370417's suggestion is a good stop-gap for now, but I'd rather not have to contend with this feature in Correspondence either. Also, this would do nothing to address the bugs. As I said, this is only my own opinion, but as an aside - so far I've only really seen one or two people speaking out in favour of the feature. |
I like it in correspondence.
That's interesting. Will fix. |
Well I thought so too for the suggestions. the user variations in correspondance is where some people also complain. that is also a place for the opening explorer.
that is why i think each user annoyance report should be precise about the context.. so that we don't assume anything, as we may not all have same feature usage experience, and the analysis mode is the work horse of many lichess pages (or objects).
There is no use for persistence in correspondance if not in analysis mode.... is what wanted to make more precise.. the complaints might not be coming from same places.. the few words tendencies is not always a precision garantee and might rely too much on common sense being the same in a big population of users....
I do agree with the logic of everywhere meaning option. but the following bullet points seem an added concern. i may have missed a few post here or there. or it might be about studies, where such issues about collaboration and permissions matter. but in games, each user tree is private already.
Also not understanding why storing locally is linked to the option importance. is this about using a public machine? did not think of that. I guess firefox containers might come in handy then, no? (I am trying to understand with the little I know).
@schlawg As to the editing question. i decided to make my posts modular in order to possibly delete moot ones without affecting things that i wanted to stay. also, easier for the replies, to be precise without asking the replier to be precise about which unrelated part. thanks for the help it may help also others. I have worked with issues in the past, my problem is not about its features (which i actually find very good) but about content expectations given a repository. I also fear making messes.
Le 01/08/2022 à 14:27, Albert Ford a écrit :
…
My suggestions:
* Leave the feature on in game replays and in correspondence.
* Turn it off in /analysis, since that is where users go if they
want a blank slate (and where they go for the opening explorer)
* Less important: avoid displaying the message panel until there is
locally stored data; this way we only require attention from the
user when the feature is having an effect
If we want to leave this feature enabled everywhere, I think there's a
strong argument that this feature should be controlled by an option.
* Privacy: let users control what is stored about them, like how a
browser lets you control cache/cookie/history settings.
* Ownership: let users control what their computation and their
screen real estate is used for.
* Automation: some people might want to click "clear moves" after
every move. Computers are good at automating, and they should be
able to automate this too.
If /analysis does not store moves locally, I think having an option is
less important.
—
Reply to this email directly, view it on GitHub
<#11304 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADNEZIANH5RZU5UZTB35CUDVXAJK7ANCNFSM55HYCM5Q>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I made a reply to that suggestion in lichess feedback... not doing the job that in game correspondance analysis mode does... it is good for sharing not for own games. one would have to give up all the game features... or painfully keep a mirror of the game at each user variation creation session in a study. I tried that, and I should ask you to try it too for a whole game... and let me know how much a nail hit it was.... I did it for a while. then gave up about it. i like chess not repetitive motions. for other reasons about specific of variations handling see my reply: first paragraphs are about study. then i recap what I do in correspondance that would make little sense in studies (unless above tedious work around). |
I liked Albert's comment but I think the privacy argument weakens the rest of his points. There may yet come a day when amazon can recommend an electric string trimmer based on adware scans of the analysis moves in your browser cache. But that day is not now. I don't think. |
https://lichess.org/forum/lichess-feedback/analysis-boards-persisting-between-uses?page=2#16 |
it makes me curious about the interaction between premove storage and local user variation tree storage.. |
Adding this as an account/board option button would be a simple fix. The change is obnoxious for my use case. I liked it the way it was before. |
* master: (56 commits) yarn run format only log non-mod forum post deletion (team) in a server file lpv support for local lichess upgrade ui deps don't log deletion of automated lichess posts disable persistence on /analysis - closes lichess-org#11304 opening refactoring and tree struggle New Crowdin updates (lichess-org#11310) tweak daily puzzle selection Ignore msg security when Lichess sends DMs more percent decimal precision lazy load opening variation boards with IntersectionObserver cache and improve opening page variations always show variations on opening pages opening abstract family page WIP don't log the entire request query string oauth tweaks fix game embed CSP fix analysis CSP for the embed dialog fix opening CSP ...
This is an obnoxious feature that should be disabled. When the user chooses to close the opening explorer or refresh the browser tab that is an unambiguous signal that the user does NOT want to save a study.Studies are great, but that is not how people use the Opening Explorer.
It is difficult and annoying to use the "clear moves" button because it requires switching away from the opening explorer database, whichis the feature I'm trying to use. Forcing moves to be stored in browser cache without user consent is malicious behavior.
The text was updated successfully, but these errors were encountered: