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
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! :)
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 :-(
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 :)
It's hard to know exactly which commit you are running but; Currently, the nightly branch is only for devs. The latest stable release of GNU social is available on 1.20.x. A more updated version but not as tested is available in the master branch.
@ziggys We do not recommend upgrading to nightly and even master branch requires attention by the sysadmin. Every production instance should stay in the 1.20.x branch.
I'm in love with loadaverage.org Site Notice: "A race condition is when GNU social has scheduled ActivityPub support in autumn and mastodon.social removed OStatus in August."