@jln Thank you for noticing. Actually, I overlooked #Mastodon ability to show Favorites. Added this in several minutes :-) In addition to syncing of the User's favorites #AndStatus v.33.05 will add syncing of: * Search by a hashtag (Mastodon doesn't support full text search though) * Messages by any selected User
@thefaico Actually v.33.03 is promoted to Release for Google Play users. I hope F-Droid build will appear soon. Regarding Mentions timeline. It's not syncable, because Mastodon doesn't provide such a feature, but you will see Mentions it this timeline as soon as they will be downloaded via Home timeline/feed.
@kaimi I don't create special "beta" version names in the code, so "beta" is indistinguishable from the "release" version. Moreover, at the time of publishing I usually don't know, if the "beta" will become "a release" or not. In Google Play professional promotion procedure exists, which allows to move/promote the same package from testing phases to production/release...
@allanviega Interesting observation. Yes, I added a lot of logging and diagnostic features to #AndStatus in order to help Users (and me) to solve problems quickly. Lots of federated servers, supported by volunteers, may have different problems, related to software and to infrastructure stability/configuration... Regarding the first application screen I would agree that maybe this is really "too much information" for an ordinary User... @yzakius @omarlibre
@wakest Most important features of Mastodon support are implemented in AndStatus, but I need some more checks and additions before Beta release. Especially regarding image attachment... Current state is reflected at the bottom of this ticket: https://github.com/andstatus/andstatus/issues/419
I implemented basic support of the "Mastodon" type Social network in AndStatus application. Currently a User can create an account and read Home and Public timelines. Unfortunately, posting doesn't work due to a problem with authorization. For some reason, authorization works for OAUTH "read" scope only. @gargron or maybe somebody else, Could you look, why e.g. uncommenting the line 61 with OAUTH_SCOPES in https://loadaverage.org/url/3561999 leads to authorization error. additionalParams.put(OAuthConstants.SCOPE, OAUTH_SCOPES); ?! With this line commented out read-only authorization is provided. Please note that during client application registration I do use the three OAUTH_SCOPES "read write follow" (in https://loadaverage.org/url/3562000 ) See https://github.com/andstatus/andstatus/issues/419#issuecomment-296375793