@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.
Por cierto, #AndStatus sí que muestra las notificaciones.
Otro tema es que en mis notificaciones no me aparecen algunas como las de @enjey e incluso la de @aab, que sí aparecen en la línea de tiempo. Pero vamos, que las notificaciones que veo en la web las veo en AndStatus también.
El problema principal es que no he conseguido actualizar en condiciones a la rama nueva y no consigo que se ejecute el script de upgrade.php por lo que unas cosas funcionan y otras no.
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...
@roka Looks like some deeper hardcoded limit in #AndStatus. Than you for reporting - will fix this also. However I cannot test this 65535 characters anywhere: tried and failed to register at your instance...
@rmbl Oh, I see that I was confused a bit about terminology. The "Group" notion in #ActivityPub is about a group of Actors (people etc.), but we are talking here about a named "Collection" of notes/activities. But actually GNU Social calls such collections "Groups" :-) I'm creating descriptions and comparisons of Groups/Lists notions in different types of social networks, supported by #AndStatus, here: https://github.com/andstatus/andstatus/issues/248#issuecomment-219826572
No, I don't use IRC. That way of communication is in another Universe for me :-)
@rmbl Sometimes I need the same, and I also feel that it is inconvenient to keep "unread" all notifications in order not to forget one of them. Recently I started implementation of Group/Lists support in #AndStatus. And I see that creation of some personal "ToDo" group and adding any note/ activity to that group could help in such cases. Unfortunately AFAIK only #ActivityPub supports such actions, meaning that such custom groups of notes could be automatically synced between User's devices or even shared... Moreover, each "Social network" in #AndStatus logically should have its own group... So it seems that I will start from some device-local groups (like tags...) that can be easily viewed... @fedilab
@moonman There are two dimentions in the support of different protocols of Social networks, which I'm facing during development : 1. Implementation of different API calls and parsing responses of every API of every supported protocol. I cope with this problem simply by implementing only some of available APIs (features)... 2. Trying to adapt internal data/actions model so that it could fit into conceptual differencies of different systems. This is a lot more time consuming and difficult to do right. In #AndStatus we started ten years ago with Twitter-like model. For the last two years I'm gradually converting it into #ActivityPub based model...
@roka As I remember, #AndStatus gets the limit from Mastodon's configuration... Please try to go to AndStatus Settings -> Accounts -> Manage Accounts -> Select your account and then Reverify credentials. Do you see updated toot length limit?
@andstatus > I need logged JSON responses of your server to the #AndStatus requests of the Home timeline...
Do you mean from my server's log or from AndStatus debug files?
> Tip: In order to fix a Timeline's syncing problem, try to go to "Manage Timelines" and select "Forget sync events and dates" in the Timeline's context menu.
@colegota "Sync 10 minutes ago. Sync since June 22" means that although the Timeline was successfully (without errors) synced some minutes ago, the latest activity/note ever downloaded via this server API, was sent on June 22. More recent activities that you see could be downloaded via other Server APIs (endpoints, URLs...) and this is why you see some more recent posts. In order to understand the problem better, I need logged JSON responses of your server to the #AndStatus requests of the Home timeline...
Tip: In order to fix a Timeline's syncing problem, try to go to "Manage Timelines" and select "Forget sync events and dates" in the Timeline's context menu. https://loadaverage.org/attachment/5477161
@colegota In short: Notifications section in #AndStatus settings lists some other things; not timelines. Longer answer: "Unread notifications" timeline includes activities: "create(post) note", "announce (retweet/repost/reblog) note", etc. which were recognized by AndStatus app as belonging to at least one of checked "Notification event types". No matter how the activity was received for some of them (e.g. for mentions) but one-to-one for others: "Home timeline" notification corresponds to the Home API timeline for all Twitter-like APIs (i.e. Twitter, GNU Social and Mastodon) and Inbox API timeline for #ActivityPub client to server API. Meaning of some AndStatus Timelines are changing over time. E.g. even for me it's unclear yet, if "Unread notifications" timeline notifies "the account" (as it was implemented quite long ago) or it should rather notify My Actor who happens to be linked to an account on some server... I clarify this for myself also, and make corresponding changes in the app...