Discourse is necroing my posts
-
Just came back to a thread I hadn't visited in (literally) months. Many weeks ago, I had written a reply to one of the posts in this thread. Apparently, Discourse saved a draft of that post at some point, because it immediately opened an editor window with that old post of mine.
Since I'm on mobile, that editor covered the whole screen and I would've almost accidentally re-posted a reply I posted months ago.
How on earth is it helpful to remember drafts for months? And how can you not remember I actually posted this draft before?
-
WONTFIX
WORKAROUND
Just don't post it again!*jeffing*
-
I only changed this yesterday:
(Default is 180 days.)
-
Default is 180 days.
OK, that's "only" a stupid default then.
But, this happened today, not yesterday.
-
Today is really Discoyesterday, and yesterday is really Discotoday. Obviously.
-
But, this happened today, not yesterday.
Probably only affects new drafts. Because DB updates are hard.
-
Or whatever mystery Discotime the "clean up" job runs at hadn't happened. Or... fuck it, it's Discourse, it's difficult to predict what shit it's up to.
-
I only changed this yesterday:
But I was keeping important documents in a draft in t/1000!
-
Maybe deleting the old drafts is done client-side and the setting only propagates on refresh.
That way we don't have to tie up the database with daily purge jobs. Brillant!
-
But I was keeping important documents in a draft in t/1000!
you should use the recycle bin/trash for that!
-
right-clicks /t/1000 and chooses Empty Drafts
-
For a moment, I was afraid that Discourse has right-click menus. That would be discoverable!
-
afraid
That would be cool though! We should totally build an interface to manage personal data on the fly like that!
Maybe even a Windowing system!
And each of the plugins could be controlled in a user-configured panel!
And things and features and vaporware!