As for the second point, I have a working setup on my local machine. I have not tested it on the server, so your mileage may vary. Simple solution: I made the * .ipynb file read-only. A quick test showed me that I can access it through an online notepad, make changes, run the code, try to save ("save the laptop"), upload the modified file to the * .ipynb file, since the save did not work, and continue with another local laptop. I hope this matches your case.
Edit: I feel that I need to clarify the behavior a bit. In principle, each user has his own temporary session, which is saved to a large extent until they move from the page. If it's in the university lecture hall, I'm sure you'll hear the random "Oh &% $ #!" when someone closes their browser by mistake, but the laptop makes a request before allowing you to move around, so I feel it should be pretty rare. As soon as they move far from the page, all of their work disappeared. I think this meets the criteria for a fickle copy of the session.
source share