Conversation
Notices
-
@roland AndStatus does have follow/unfollow feature. Unfortunately, following a remote user is not currently supported at a server side, so this is a request to GNU Social developers?!
Do you know of any subscription API, which works at GNU social servers, but is not supported by #AndStatus yet? If yes, please send me links with documentation/examples...
- @mcscx@quitter.se and Stephen Sekula repeated this.
-
@roland Of course I know :-) But I cannot do this at a client's side only. This is why I'm asking for help from the server side :-)
-
@andstatus so you're suggesting the the 'remote follow' process as implemented in the web interface is not actually supported by the API but (instead) inplemented "directly" in the web GUI? If so, yuk! Then that should definitely be amended. /cc @mmn
-
@mk Oops, I could follow you from AndStatus at LoadAverage. Maybe this depends on some server/user setting
@mmn
-
@andstatus well, the instance I'm on has far fewer than 10 users - but I'm following 141, and have 171 followers - see sidebar here: http://oracle.skilledtests.com/mk . So that proves 'remote follow' is indeed possible. I don't know how that relates to server configuration though.
-
@mk Yeah, this is something I want to fix and I just have to understand some parts of the API better to know if I should fix it, extend it or simply hack in some support that @andstatus can use and others can adapt to :)
-
@mmn probably extend it - doing a hack would just mean more headaches down the line ;-)
-
@mk See e.g. this discussion, starting from September 12, 2014 https://github.com/andstatus/andstatus/issues/93
- attachments are not properly crossing GNU social instances for some instances, not for all... so the problem there is in configuration/version of components
-
@andstatus yes, it's quite possible that some things that can be configured are not robust in the context of federation - simply because federation was added later. But in the case of remote subscription my point is that it cannot have been implemented as a single API call, because it is *always* a process with several steps. There may be a configuration factor here, too because normally there are two ways to do this process: 1) starting from the local node and 2) starting from the remote node - both work nearly everywhere except in a very few cases; these rare exceptions _may_ be due to configuration, or to incompatibility between http and https in the steps of the remote subscription process. But afaik one of teh two methods always works.
-
@mk I am confused about whether remote following via API already works or not. I thought that it doesn't work but yesterday I successfully followed _you_ using AndStatus at LoadAverage.
Please test at your side: can you follow anybody using AndStatus at your instance. If not please send me error report from "Commands in a Queue"
@mmn
-
@andstatus Not remote users are impossible to subscribe to via Twitter-compatible API but remote users without any presence on local instance.
-
@andstatus : @mk has already an entry in loadaverage's db b/c she has already subscribers there. It wouldn't have worked for an unknown acct
-
@andstatus Hm, is the /api/friendships/{show,exists,create,destroy}.format what you're looking for?
create/destroy take the locally stored ID of a profile as argument 'id' and creates or destroys a "friendship" (i.e. subscription, which sounds less brutal).
exists takes 'user_a' and 'user_b' as "subscriber" and "subscribed" respectively.
The locally stored ID should be available in the notices and updates, so for the home_timeline for example, it's the user->id property of a status.
-
@mmn AndStatus already uses the "friendships" API to follow/stop following a user.
Does anything similar exist for subscription to a group?
Any other API related to a group?
BTW, earlier I used the link as a reference of API: https://e14n.com/wiki/API - Now that link doesn't work, but is anywhere GNU Social API page?
@roland @mk @lnxw48
-
http://www.skilledtests.com/wiki/Twitter-compatible_API#Group_resources should be sufficient thanks to @erkan (there's a copy on web.archive.org #WaybackMachine too)
Should be the same thing as with profile subscriptions, provide the local ID and it should work. Won't currently work with _remote_ group nicknames, aliases or (unfortunately) URIs.
-
@roland Thanks I will look at it...
-
you mean: SELECT * FROM `user` WHERE `nickname`="andstatus"; Empty set (0,00 sec)