-
Notifications
You must be signed in to change notification settings - Fork 170
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
Saving drafts #356
Comments
Agree, but I probably won't be able to get to it anytime soon. |
Any way to prioritize this? Several times now (more than 3), I've written out long responses or posts and had a failure. When this happens, I've lost the entire post, which is especially painful when it's been typed out on a mobile phone. The failures come in three types, not all are Jerboa, but they could all be alleviated if Jerboa autosaved drafts like Fedilab does.
Having a draft autosave would be a godsend for these cases. OP asked for saving drafts; I'm suggesting that it should be specifically autosave. |
+1 on this. With Lemmy getting so overloaded I've lost posts three times in the last hour from timeouts. I've resorted to writing my posts in a separate note application and then copy/pasting it into jerboa so if the request times out I don't lose what I wrote. |
I'm interested in working on this. I'm a bit stuck on getting spoilers working, so I'd like a diversion. |
Looking forward to this, few things are more dissatisfying than having whatever you just wrote lost because of technical issues out of your control. With Lemmy instances overloaded I'm unfortunately seeing this all the time lately. |
Personally, all that I need is autosave as it would solve navigating to home or another app only to lose your response when navigating back to Jerboa. Imo, having functionality for multiple drafts could be considered an enhancement to the autosave feature. |
I don't have time atm, but anyone else is free to work on it. |
It'd be nice to save drafts so you can finish writing you post afterwards.
The text was updated successfully, but these errors were encountered: