Conversation

Notices

1. MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 30-Apr-2016 09:16:08 UTC MMN-o ✅⃠

   • Verius
   @verius that url is the unique global identifier for the user (or alternatively a profile url that when running discovery, say using webfinger or microformats2, gives you the user info). It should be safe to cache it for a relatively long time as an identifier for a specific profile.
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Friday, 29-Apr-2016 15:31:37 UTC MMN-o ✅⃠

     • AndStatus
     @andstatus The full mentioned id should never be trusted from HTML in the first place, that is metadata accompanied with the post. More specifically <link rel="mentioned" ... />
     AndStatus repeated this.
   • AndStatus (andstatus@loadaverage.org)'s status on Friday, 29-Apr-2016 16:05:03 UTC AndStatus

     in reply to

     • thefaico
     @mmn I don't see anything like <link rel="mentioned" ... /> in the JSON file from a server.
     Maybe this is problem of the "Twitter compatible API" only?
     BTW about two months ago we already started discussion on ActivityStreams protocol in JSON format. Let's make another step forward! :-)
     
     My latest posts to you on that subject (unanswered) are below:
     
     @mmn Thank you for encouragement.
     Do you know any implementation of this API that I could lookup in order to move from a zero point?!
     I need at least two pieces: authentication (client registration...) and making a request something like "statusnet/config"
     --
     andstatus@loadaverage.org
     URL: https://loadaverage.org/notice/7762601
     
     
     @mmn AndStatus already supports ActivityStreams protocol in JSON format. Do you mean that I can switch to that protocol accessing GNU Social and forget about Twitter API problems? If yes, do you have any links with a list of API calls... ? Maybe any reference client implementation?!
     --
     andstatus@loadaverage.org
     URL: https://loadaverage.org/notice/7705136
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Friday, 29-Apr-2016 16:08:11 UTC MMN-o ✅⃠

     in reply to

     • AndStatus
     @andstatus Yeah. The Twitter compatible API is compatible with Twitter's extremely limited, non-federating design and all its flaws.
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Friday, 29-Apr-2016 16:14:29 UTC MMN-o ✅⃠

     in reply to

     • AndStatus
     @andstatus I thought I answered that you should use AS but few use it so if I accidenyally sneak in a bug then it'll take longer to discover it probably.
   • AndStatus (andstatus@loadaverage.org)'s status on Friday, 29-Apr-2016 16:29:40 UTC AndStatus

     in reply to

     • thefaico
     • Verius
     @mmn The problem is that I cannot start having nether API documentation nor reference implementation / examples. Anothet time:
     
     Do you know any implementation of this API that I could lookup in order to move from a zero point?!
     I need at least two pieces: authentication (client registration...) and making a request something like "statusnet/config".
     
     @verius
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 30-Apr-2016 09:21:43 UTC MMN-o ✅⃠

     in reply to

     • Verius
     @verius the rel="mentioned" are always URIs btw (as apart from perhaps bring URLs which aren't _the_ specific identifier).