Implemented Autosave post drafts

Rob

Well-known member
Autosave does not equal 'save as draft'....

Time to analyse things...
10% of posts are above average in size (high estimate) and 10% of those posts (high estimate) *may* get lost and need rewritten... as I said, very high estimates and real world will be much much lower... but lets use the above anyway to explain...

Lets say you have 100 posts to make...
10 posts are above average size
1 post (10% of above) could potentially get lost

So, out of 100 posts you could potentially get very annoyed about having to rewrite ONE long post.

Do those figures warrant an autosave feature that will add overhead to the server and slow the experience for EVERYONE? Does it warrant the extra storage requirement on the server? I actually say no, I dont think so. (localstorage is not supported on all devices so a true solution will involve the server)

I think the option to 'save as draft' SHOULD be offered, but not autosave. Admins and staff will use this especially but also many users. If limits were set then this is not only practical but a feature you would expect of any modern forum (I believe IPB is/will be doing this, wordpress and even vBulletin blogs allows this). I feel xenForo needs to lead the field and if not at least keep up.

One other feature I would like to see along side this...
When writing a new thread or reply I would like to see xenForo do an Ajax 'call home' every minute or two... this will trigger notifications. If you are writing a long reply then chances are someone has replied to the thread in that time. If the 'call home' was going on in the background then it could trigger an alert that someone has replied to x thread. This may prompt the user to 'save as draft' and go check the reply before continuing with their response.

Ok, this is just an opinion but I think it would be the best implementation, most useful and leave the smallest server footprint. Autosave would be sucky imo but at least the mod in the post above can autosave on some browsers at client level :)
 

CoreIssue

Member
As I said before, Save as Draft makes sense.

But, with that said, it isn't only long posts that get lost. Something happens during a shorter post, you are called away too long, it is lost.

But, ah! Just recreate the shorter. Hang on there, a shorter post can require research that would have to be redone.

Point here is that length is not the only metric to consider, but time as well. Time for research, time for composition, time for interruption.

Something is needed.
 

Rob

Well-known member
the localstorage clientside solution should suffice for your needs Corelssue but it doesnt take away the need for a safe as draft requirement - that really is needed imo.
 

CoreIssue

Member
Doesn't always work, Rob. Been there, done that. Not worth the risk. I would really appreciate the Save as Draft.
 

Rob

Well-known member
Doesn't always work, Rob. Been there, done that. Not worth the risk. I would really appreciate the Save as Draft.
I think this feature will come in time natively and a mod for it will come shortly Im sure. The autosave feature.... I dont think that will ever come tbh except via the localstorage client side method.
 

Green Cat

Active member
I would also appreciate this feature. Not sure if LS or database would be the way. LS seems more appropriate for posts and database for threads. But doing two separate ways is subideal. Probably LS with a fallback to db for browsers not supporting LS is a good way.
 
Top