{"ops":[{"insert":"Is there a way to disable or turn off this feature? I generally use both of my monitors when deck editing and use one to check other sources for card lookup. Currently it feels like every time I tab away from Archidekt, I come back to an idle screen that just eats up time as I wait for it to \"load\" my deck again. I feel like the page is just refreshing every time I stop working on the deck, it's not a feature that I enjoy. It's clunky and I'm not sure what the purpose of adding it in the first place was, not to be too harsh. I just don't get ay benefit from it that I can perceive, and it's just made my deck editing sessions clunky and slower. Any advice to manage it or any insight on it's creation?\n"}]}
2
{"ops":[{"insert":"Just chiming in to say I greatly dislike the new idle screen. It keeps coming up repeatedly even if I have made no changes. (I have done a full refresh)\n"}]}
3
{"ops":[{"insert":"(I apologize in advance if this response feels somewhat generic -- I'm trying to cover as much ground as possible for anyone who's commented recently on the idle screen and/or save issues)\n\nToday (11-14-22) we pushed out an update to the idle screen. Instead of a full page overlay, it's now just a popup notification at the bottom of your screen after 15 minutes of idling. You can either reload the page directly from it (which we would recommend if you're working on it from multiple tabs/devices to make sure you're still on track), or just close the popout out. We're hoping this feels much less disruptive to folks, but would certainly appreciate feedback. \n\nImportantly, we also made a change that we believe could fix the issue that some users were experiencing with unexpected card losses while editing. At the absolute least, you should now receive a notification if cards aren't saving properly so we don't waste your time working on a deck that's gotten into a bad state. If you see this error regularly, please do let us know because it means that the problem we resolved today wasn't the whole story.\n\nWe appreciate everyone's patience as we work to dial this in. We believe we're getting close, but continue welcome feedback as we make our tweaks. \n"}]}
1
{"ops":[{"insert":"I understand that you don't care for it, to be honest I don't love it either. But it solves a few fairly complex problems that we can't seem to think ways around otherwise. \n\nSome users lose data when bouncing between devices due to them not refreshing the page before continuing to edit between devices. This gets multiple devices into separate states which makes making changes fairly dangerous if you're not aware of the differences. The idle screen forces a refresh which prevents this issue. \n\nThat alone wouldn't be enough to justify the idle screen since that problem likely affects fairly few individuals. But with the advent of collaborative real-time deck editing users have a constant connection to our server now, and eventually that connection will break after a certain amount of time. The idle screen forces a refresh once dismissed to make sure you have the most up to date changes after having been disconnected. \n\nThe idle screen also only pops after a minimum of 10 minutes of not making any changes to the deck and you're no longer focused on the browser tab (if you're focused on the tab it's 90 minutes). While we do feel is a reasonable amount of time to keep an unused connection open, we too aren't the largest fans of the idle screens implementation. It can be kind of obnoxious if/when you don't really understand why it's happening. We did spitball alternatives, like just not showing an idle screen and refreshing without telling the user what's going on, but that seemed a bit more disorienting. \n\nEither way, we'll continue to think of ways to better solve the \"keeping your data matching what's on the server\" issue and hopefully we'll be able to smooth out the idle screen over time. \n\nThanks for your feedback btw! I hope I don't come across as being dismissive of your thoughts. Just figured you might care for our thought process. \n"}]}
0
{"ops":[{"insert":"So the idle screen is related to a change made to how we're saving decks-- the tl;dr is that when changes to a deck are made, they'll "},{"attributes":{"italic":true},"insert":"immediately"},{"insert":" appear to someone (you or another user) looking at that deck in another window. This is in preparation for real-time collaborative deckbuilding.\n\nUnfortunately, the update (which went out last night) wasn't playing nice with some users' cookie settings, so we rolled it back a bit over an hour ago. It sounds like you might be operating on an old version of the client, so try refreshing your page with Ctrl-Shift-R and you should be good to go.\n\nThat all said, we do plan to reimplement this update as soon as we figure out what was going wrong. The idle screen will be necessary to make sure you're still connected to the current version of the deck, but we should be able to tweak it to be less annoying. I apologize for the inconvenience, but appreciate the feedback! \n"}]}
1
{"ops":[{"insert":"This is the first time I'm seeing the Idle Screen. It sounds like, when the OP posted, that this might have been even more intrusive, but it's pretty frustrating to deal with as it is now. I like working on decks over a period of time -- have a few ideas, insert a few cards, then take a brief break and come back. I really dislike having to reload when nothing has changed. \n\nI can understand that a forced refresh/Idle Screen is useful for collaborative deck development, but I'd also imagine collaborative deck development is something that very few of your users will actually do. If possible, I'd like to see this as an opt-in feature, so that the workflow for the vast majority of your userbase doesn't become worse.\n"}]}
2
{"ops":[{"insert":"Thank you for the quick response! Glad to hear things are being actively iterated on (as always)! I appreciate the insight on why the feature is being implemented, and the opportunity to give feedback for the platform, love your product! I look forward to seeing the continued work :)\n"}]}
0