1. For Android 9+ only: Animations of animated images are shown by default. Both in attachments and in avatars. GIF and WebP are supported. Settings -> Appearance -> "Show image animations" option allows to turn this behavior off. It appears that currently only ActivityPub and Pump.io networks (i.e. server parts of them) support WebP and keep GIFs as is. Other servers simply reject WebP and convert GIFs to video... https://github.com/andstatus/andstatus/issues/330
2. Animated images and video on Twitter are shown as preview image with a "Play" button on it. This is the same behavior as for other social networks.
3. "Play" button on a video preview image is moved to the bottom corner to allow better view of the image.
4. Screen orientation is not "unspecified", as before, but is set to "The user's current preferred orientation", set by a User for the whole Android device. In particular, this allows to use landscape mode on smartphones (and not on tablets only, as before). https://loadaverage.org/attachment/5948838
I haven't seen anything else for iOS that supports GS, but it might be worth going to the big blue discount store (aka #Walmart ) and buying their $80 #Android device, so you can use #AndStatus instead. AndStatus is not known for being fast, but it can run circles around Shoyu, even running backwards, with its eyes closed and its ankles bound.
#AndStatus v.56.09 (326) released. "Show numbers of likes, replies and reblogs for a Note 1. Show numbers of likes, replies and reblogs for Mastodon; likes and retweets for Twitter. Added similar to #ActivityPub #C2S, hope the same counters will be supported there also. 2. Added Actors's name ("Real name") as a separate field to Actor's profile. Created landscape layout for Actor's profile. https://loadaverage.org/attachment/5933715
1. Simplified nterface to add new account in #Mastodon. You don't need to add "Social network" separately. Just type (host of) instance and proceed to Log in.
2. Fixed "App language" switch. Many translation updates.
Since its creation years ago AndStatus used only one background process (thread) to post and to download information from the Internet. Images downloads were considered low priority tasks, so avatars and attachments appeared noticeably later than text of a timeline, especially when multiple timelines and accounts were synced one after one. With this release a separate process is responsible for images downloading, so overall syncing performance improvement should be visible.
#Mustard is old and unmaintained, but it works with GS #OAuth and I have it on my phone. For a few years now, posting has not worked (error message said “unauthorized”), so I’ve used #AndStatus to post (despite its own issues). I don’t know if the server migration or the version bump fixed things, but I’m glad that I can now use Mustard for posting again.
@diogo Thank you for your explanation. Now I really see a page on the loadaverage site that tells its server version. And #AndStatus still successfully connects to the server (I'm writing to you using it). This means that the authentication problem that I reported is caused by a configuration of a concrete server, and not by the latest version of #GnuSocial :-)
Using a chance to talk with you, I hope that you will find time for Client-to-Server #ActivityPub API also. I'm extending support of that API in AndStatus, and already see that not only #Pleroma, but even some #Mastodon sites begin to implement some parts of the API, allowing a Client app to request information directly from its sources, without a need to duplicate it. E.g. Notes by an Actor may be requested from the Actor's profile (from the Actor's outbox) at his site, and not from the server, at which the User of the Client app has an account...
@xrevan86 @diogo One of users reported that #AndStatus app doesn't work with the new #GnuSocial server "v.2.0..x dev". I started investigation and see that /api/statusnet/config.json API point now returns 404. Looking in current Source code of the server I see that the API is documented now as /api/gnusocial/config.json - but that returns 404 also...
So the question is did Client API change radically or the server is simply broken, or... ? And where can we see any info on Client to Server API changes / current docs? @colegota
@coolboymew I heard recently that #AndStatus doesn't work properly with Pleroma as with "Mastodon type" social network. Didn't investigate this... But since last year #Pleroma is adding #ActivityPub #C2S (Client to Server) interface, and AndStatus has basic support for this type, checked and tested with Pleroma team! See https://github.com/andstatus/andstatus/issues/499 @dielan @thefaico@quitter.se
@coolboymew Thank you for the feedback. As I see you mentions not "outdated things" but features/settings that didn't meet your expectations or were unusual for you :-) Most of what you mentioned can be configured in #AndStatus settings. Including a list of timelines to be shown, whether or not request all notes/tweets or recent only... Notifications were improved a year or two ago and now you can see "Unread notifications" timeline (yes, another timeline :-) ) and explicitly mark all notifications as read.
Moreover, looking into the source code I found the first-hand info about the system's API . And although the code, related to Groups support, didn't change for the last six years :-) https://notabug.org/diogo/gnu-social/src/nightly/actions/apitimelinegroup.php , it works and I could actually retrieve the group's timeline at loadaverage.org
The unusual "!groupname" syntax to address a group is not a big problem...
@rozzin After today's thinking about our discussion and re-reading of the thread, I seem like understand, what needs to be done, see updated comment: https://github.com/andstatus/andstatus/issues/248#issuecomment-219826572 And what's interesting: GNU Social's groups look like the first to be worth implementing. Simply because they work and at least somebody is using them, I hope.
Or it is too late to implement something for #GNUSocial ?! I mean, too few people use it..?!