Skip to content
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

Open
suoko opened this issue Apr 1, 2023 · 7 comments
Open

Saving drafts #356

suoko opened this issue Apr 1, 2023 · 7 comments
Labels
4 - medium/high priority Issue needs to be fixed soon, does not break core functionality enhancement New feature or request

Comments

@suoko
Copy link

suoko commented Apr 1, 2023

It'd be nice to save drafts so you can finish writing you post afterwards.

@dessalines
Copy link
Member

Agree, but I probably won't be able to get to it anytime soon.

@twizmwazin twizmwazin added the enhancement New feature or request label Jun 7, 2023
@xxxserxxx
Copy link

xxxserxxx commented Jun 11, 2023

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.

  1. I navigate away to look something up for the post; when I return, Jerboa shows a white screen and no widgets, and I've lost my post.
  2. Crash. This is quite rare, but I've had it happen while posting
  3. There's some error while posting. Maybe this is on the server side, or just a network error, or whatever. In any case, the post is lost.

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.

@peake100
Copy link

+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.

@twizmwazin twizmwazin added the 4 - medium/high priority Issue needs to be fixed soon, does not break core functionality label Jun 14, 2023
@beatgammit
Copy link
Contributor

I'm interested in working on this. I'm a bit stuck on getting spoilers working, so I'd like a diversion.

@lucaspar
Copy link

lucaspar commented Jul 1, 2023

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.

@Coehill
Copy link

Coehill commented Dec 14, 2023

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.

1. I navigate away to look something up for the post; when I return, Jerboa shows a white screen and no widgets, and I've lost my post.

2. Crash. This is quite rare, but I've had it happen while posting

3. There's some error while posting. Maybe this is on the server side, or just a network error, or whatever. In any case, the post is lost.

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.

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.

@dessalines
Copy link
Member

I don't have time atm, but anyone else is free to work on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4 - medium/high priority Issue needs to be fixed soon, does not break core functionality enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

8 participants