[SUGGESTION] Pseudo-editing capability until true editing capability is implemented
Right now, we do not have edit functionality which is killing me, because I often find mistakes after I push things live.
I know that you plan to edit this function properly in the future, but until that comes, I have a framework which would give users some of the funtionality.
New option in digg settings for "Edit after posting (time delay) (disabled by default)
New option (nested under above if enabled): "Time allowed" [invoke OS time picker] (you know, the one you scroll through to set hours, minutes, and seconds).
Posting now simulates on device successful reply, back end doesn't actually post it until timer ends (defined as local timer ending - no need to keep track of it on digg servers)
What would this look like in practice? The user posts a submission or a comment and it looks like it immediately goes live, but it doesn't. Additionally, the three got menu would now contain two additional options such as "Edit* and "Push Live (stop editing)".
The timer would define how long they have to look at their post before it actually goes live. I know this seems silly but it seems way too common that you look a post over and everything looks to be in good order, but then when you finally post it to the website, you notice that there are mistakes. Too late now Using my strategy above, you get both the effect of posting it (to see problems) and then being able to truly go back and catch the mistake. The timer functionality is to be user set is so that people don't start posting things and having to wait an exceptionally long amount of time for everything to post or to always having to click push live. For example, set the timer to 1 minute and then it will give you 1 minute after you think you've posted it to go back and edit. And then at the end of 1 minute, it actually shows up on digg.
3 Comments