@mangeurdenuage Yeah, I agree. I looked at the Qvitter interface for #GNUsocial and decided that I did not want a #JavaScrippled instance. I wish the #Pleroma folks would make a minimal JS interface.
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.
@licho #Mastodon 3.x and #Pleroma 2x no longer speak the #OStatus federation protocol. !GNUsocial 2.0 will add the #ActivityPub federation protocol, so ask your admin to be ready to upgrade soon.
@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
@strypey @clacke #ActivityPub support is already in the #GNU_Social (2.0.0-dev) codebase that many instances currently use, it just isn't working so well (from what I can tell, Mastodon signatures don't verify). They're working on fixing that
@xrevan86 I suspect that non-local groups aren't shown via API simply because you cannot do anything with via API with non-local groups: join, leave, list members... In a case of GNU Social seeing local groups only is mostly useless: main power comes with using the same group across different instances. E.g. naturally I would like to join !gnusocial But as I cannot even find this group via API from loadaverage.org, it looks like implementation of "list local groups" won't worth its efforts :-(
@xrevan86 As I see you are an active #GnuSocial developer now :-), congratulations! Could you help to boost Group support in client apps?
I see that web site has the global Group Directory https://loadaverage.org/groups but API, as I see, shows local groups only. Could you extend API to list All accessible groups?!
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..?!
@guizzy It's the way all these things work. I've seen loads of resurrected threads on #Pleroma and #Mastodon as well as #GNUSocial when someone deletes their account. Their home instance sends out deletes for every individual post they ever made, which modifies the conversations those posts were part of.