Notices by AndStatus (andstatus@loadaverage.org), page 27
-
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 27-Nov-2016 07:29:42 UTC
AndStatus
#AndStatus v.30.04 (198) published to the Open Beta testing channel https://play.google.com/apps/testing/org.andstatus.app
Translations updated thanks to volunteer translators! (see https://crowdin.com/project/andstatus )
All known crashes fixed. Thank you for your crash reports!
In particular, we found a cause of intermittent application freezes for a second or two: loading and saving of the commands queue. Now this is done asynchronously. -
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 26-Nov-2016 17:32:35 UTC
AndStatus
@dtluna @lnxw48 For those, who don't like Github for some reason, I imported #AndStatus repository to Gitlab. URL differs from Github in two letters only: https://gitlab.com/andstatus/andstatus/
Is this ok?
@d0e @lambadalambda @dt -
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 26-Nov-2016 15:15:11 UTC
AndStatus
@dtluna Would you help the project, if I create alternative AndStatus repository at a git hosting of your choice?
@d0e @lambadalambda @lnxw48 @dt -
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 26-Nov-2016 15:00:16 UTC
AndStatus
@dtluna I don't believe hosting at Github is a stopper for anyone, who really wants to contribute a source code :-)
@d0e @lambadalambda @lnxw48 @dt -
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 26-Nov-2016 14:34:06 UTC
AndStatus
@lnxw48 Anyway, if anybody wants to improve AndStatus to have OAuth for !gnusocial, you are welcome at https://github.com/andstatus/andstatus/
@d0e @lambadalambda @dtluna -
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 26-Nov-2016 14:26:42 UTC
AndStatus
@lnxw48 Maybe that time I didn't figure out how to get Client keys... -
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 26-Nov-2016 12:30:27 UTC
AndStatus
@lambadalambda When I tried to implement OAuth for GNU Social some years ago... I couldn't and I didn't find any working implementation example.
BTW recently we implemented OAuth2 for Mastodon in AndStatus. Didn't agree on the other API though yet...
@d0e @dtluna -
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 26-Nov-2016 12:14:35 UTC
AndStatus
@d0e For GNU social please set basic authentication in AndStatus. OAuth works for Pump.io and Twitter -
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 23-Nov-2016 10:19:32 UTC
AndStatus
@takeshitakenji Regarding AndStatus, you can lookup errors in the "Commands in a queue" menu item / view -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 20-Nov-2016 16:16:51 UTC
AndStatus
@archaeme I will add the simplest check for the ”favorited something by”, but unfortunately there are other variations of the "favoriting activity”, sent by GNU Social server to a client application...
@theru @vinzv @takeshitakenji -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 20-Nov-2016 16:07:27 UTC
AndStatus
@maiyannah Because you took part in this conversation,and we are Replying to all :-)
@theru @vinzv @archaeme @takeshitakenji https://loadaverage.org/attachment/3315107 -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 20-Nov-2016 15:25:16 UTC
AndStatus
@takeshitakenji Agree, so one existing "Reply to all” action will be replaced with two, to avoid confusion: ”Reply to all participants" (what we actually have now) and "Reply to all mentioned users” ?!
@maiyannah @theru @vinzv @archaeme -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 20-Nov-2016 15:15:24 UTC
AndStatus
@takeshitakenji Do you mean an option to include into "Reply to all” all users, mentioned in all messages of the conversation?
I think a separate action "Reply to all including mentioned” would be more flexible?! (but longer context menu...)
@maiyannah @theru @vinzv @archaeme -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 20-Nov-2016 15:04:06 UTC
AndStatus
@archaeme Yes, AndStatus includes in ”Reply all” only users, who actually took part in the conversation (i.e. ignoring mentioned users). This is not a limitation: I think this is proper behavior.
@theru @vinzv @takeshitakenji -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 20-Nov-2016 08:33:14 UTC
AndStatus
@takeshitakenji Please point me to an example and describe, what you are doing and and what you expect to see.
The best way way to show me that message is to reply to it and mention me in that reply. -
AndStatus (andstatus@loadaverage.org)'s status on Monday, 14-Nov-2016 11:59:33 UTC
AndStatus
@maiyannah If you really want to discuss this issue, please do it in https://github.com/andstatus/andstatus/issues/83
Otherwise we are going in circles :-( -
AndStatus (andstatus@loadaverage.org)'s status on Monday, 14-Nov-2016 06:24:54 UTC
AndStatus
@maiyannah I see. I am talking not about personal preferences, but about proper system's design... -
AndStatus (andstatus@loadaverage.org)'s status on Monday, 14-Nov-2016 06:20:14 UTC
AndStatus
@maiyannah I evidently couldn't explain to you, why current behavior is correct :-(
Instead of pointing to inexistent bugs, please read our discussion on this topic and take part in it here: https://github.com/andstatus/andstatus/issues/83 -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 13-Nov-2016 08:03:52 UTC
AndStatus
@takeshitakenji We have AndStatus Settings -> Syncing -> Don't synchronize old messages... See https://github.com/andstatus/andstatus/issues/354 @lnxw48 @tknjshiftbot -
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 09-Nov-2016 10:48:54 UTC
AndStatus
@maiyannah I think that relying on a client application to check for duplication is conceptually wrong, because this solution won't guarantee absence of duplicated posts at a server side. E.g. a client application reposts intentionally, or has a bug...
@gargron