Conversation
Notices
-
@colegota @andstatus @diogo !loadaverage is using nginx.
Writing this from AndStatus, so… works for me :-).
- AndStatus repeated this.
-
@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
-
@diogo @xrevan86 Oops, I see that 404 error was due to the wrong domain :-).
But my questions regarding API changes and their descriptions are still valid: now authentication fails with 401 error and I simply don't know, where to look at? Any reference client app/tool to lookup?!
@colegota@quitter.es
-
Hey @andstatus, thank you for reporting this!
There are no changes planned in V2 regarding existing APIs so, if it isn't working and it was in a prior version, that means we have either accidentally added a bug or some plugin in the faulty instance is somehow interfering :-(
I've just tried requesting: https://loadaverage.org/api/statuses/mentions.json and authenticated myself via HTTP Basic Authentication with no issues.
Every GNU social installation has a doc concerning its APIs at instance.tld/doc/twitterapi, as seen, e.g., in: https://loadaverage.org/doc/api
If this problem is present in LoadAverage, please open an issue with instructions to reproduce this, so that we can further debug and get this fixed asap!; Otherwise, please ask the affected instance's sysadmin to open an issue requesting for help, so that we can assist them getting their instance back to normal :)
Our repository is available at https://notabug.org/diogo/gnu-social
Keep up the great work and thank you for supporting us! ^^
-
@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...
@colegota @xrevan86
-
ActivityPub C2S is part of our roadmap.
Concerning federation and APIs, this is the current tasks sequence:
- TheFreeNetworkModule: a layer that will ensure data integrity and proper federation with more than one protocol enabled (OStatus and ActivityPub, for instance);
- ActivityPubPlugin S2S: It seems to be working properly with Pleroma already, yet some issues with Mastodon were reported. Furthermore, there's still a couple of things to implement, namely: Groups, attachment retrieval, proper deletion and some minor issues;
- ActivityPub C2S: unfortunately, this one wasn't even started yet, we've just done some planning about it, sorry, but we want it to be part of v2;
- Pleroma API: We want to release this one in v3.
I can advanced that TheFreeNetworkModule is having good results already and will soon be merged! :)
cc: @tenma
-
Hey!
I believe ldavg runs on nginx with the latest nightly and AP plugin disabled ( @xrevan86 will know this better than I do, obviously).
Nonetheless, I tested in social.hackersatporto.com (nginx based), which is running nightly with AP enabled and the APIs seemed to be working. I doubt ActivityPubPlugin to affect this.
nginx vs apache shouldn't make any difference (but may, although I would only expect some in serving attachments, and that was tested with both web servers).
If you're convinced that AndStatus stopped working with a code update, try rolling back some commits to see if it helps; try also to disable every plugin you've enabled to see if it is some plugin's fault. Also, check the PHP's error log, apache's and GNU social's to see if they have some helpful information.
Consider opening an issue concerning this in the repository if your findings suggest a bug somewhere!
See ya ^^
AH! Please specify a commit or branch when reporting issues because both master, nightly and experimental announce 2.0.0-dev :/
Kind reminder:
- 1.20.x is the latest release (v1.20.9)
- master is fairly stable and acceptable to be used in production
- nightly is force pushed somewhat frequently and is intended for devs (ActivityPub plugin isn't considered ready for production and will cause duplicated profiles when used together with OStatus - that's why ldavg has it disabled, TheFederationModule will solve this)
- experimental is for my own testing
-
It seems to fail only at my instances. Updated to January, 7 (and with apache).
Will try to upgrade on next days.
Sorokin Alexei
AndStatus
Diogo Cordeiro
Colegota El Villano
All senooken JP Social content and data are available under the