Conversation

Notices

1. AndStatus (andstatus@loadaverage.org)'s status on Thursday, 28-Mar-2019 05:49:17 UTC AndStatus

   • Juanjo Faico
   @dwaltiz Funny proposal :-)
   I think it's much easier to fix the problem that you encountered (I suspect it's about UI/#UX) yet even _you_ didn't find time to file the issue properly, trying to reproduce it, describing steps to reproduce the issue and attaching screenshots. Just this post that doesn't help to make the app better, unfortunately :-(
   Yes, there may be "steps back" (developers call them "regressions") but they occur exactly because I'm rewriting #AndStatus and rely on community members, who take their time to explain, what went wrong...
   So, when you are ready to help, please file the bug here and we will substantially discuss it: https://github.com/andstatus/andstatus/issues?q=is%3Aissue+sort%3Aupdated-desc
   Maybe at that stage somebody will join us with concrete help...
   • AndStatus (andstatus@loadaverage.org)'s status on Friday, 12-Apr-2019 06:24:25 UTC AndStatus

     • Juanjo Faico
     @dwaltiz I fixed probable cause of the "lost draft" problem, that you encountered, in #AndStatus v.47.11 (released yesterday). A draft could be lost (unsent and invisible in a timeline) in a case there was another draft saved earlier by the same account.
     Now different drafts don't interfere with each other.