Conversation
Notices
-
clacke (clacke)'s status on Friday, 16-Jan-2015 17:38:22 CET clacke @mmn I disagree with that observation. :-) -
Skratterciseterapeutens Leende (hannes2peer)'s status on Friday, 16-Jan-2015 00:40:14 CET Skratterciseterapeutens Leende quitter.se seems to be running fast again :) i opened registrations again just now. -
mmn (mmn)'s status on Friday, 16-Jan-2015 17:39:55 CET mmn ^- @hannes2peer (did you reply to my like activity, @clacke? :)) clacke repeated this. -
clacke (clacke)'s status on Friday, 16-Jan-2015 17:49:12 CET clacke @mmn Old web UI and AndStatus both think that like activity is just a post. :-/ -
Temporary Marjolein (mk)'s status on Friday, 16-Jan-2015 18:19:48 CET Temporary Marjolein @clacke that's because a post is just an activity really ;-) -
lnxw37 (lnxw37)'s status on Friday, 16-Jan-2015 18:23:01 CET lnxw37 @clacke Yeah, something changed in the way likes are recorded. Applications need to be updatedfor the change. -
AndStatus@quitter.se (andstatus)'s status on Friday, 16-Jan-2015 18:38:11 CET AndStatus@quitter.se @clacke Please see this report https://github.com/andstatus/andstatus/issues/200 clacke repeated this. -
clacke (clacke)'s status on Friday, 16-Jan-2015 19:34:33 CET clacke @mmn Oh! So that's what that was. I was confused there were two "identical" posts and just picked one. -
clacke (clacke)'s status on Friday, 16-Jan-2015 19:38:45 CET clacke @andstatus Oh. So it seems there is no way for AndStatus to see the difference? Or is it visible in AS API (if that exists) or something? -
AndStatus@quitter.se (andstatus)'s status on Saturday, 17-Jan-2015 14:26:40 CET AndStatus@quitter.se @clacke This is a simple bug to be fixed in GNU social. I don't think it's right to workaround it using some "intelligent recognition"... clacke repeated this. -
AndStatus@quitter.se (andstatus)'s status on Saturday, 17-Jan-2015 14:26:47 CET AndStatus@quitter.se @clacke There is no special "AS API". AndStatus reuses existing "Twitter compatible API" in GNU social clacke repeated this. -
clacke (clacke)'s status on Saturday, 17-Jan-2015 15:40:14 CET clacke @andstatus Yes, Twitter API should probably filter out such activities. I was thinking of the way forward using richer activities. -
clacke (clacke)'s status on Saturday, 17-Jan-2015 15:41:43 CET clacke @andstatus AS as in ActivityStreams, not as in AndStatus. Sorry for being unclear. I wonder e.g. what API the #qvitter frontend is using. -
clacke (clacke)'s status on Saturday, 17-Jan-2015 15:44:15 CET clacke @lnxw37 I agree with @andstatus that existing Twitter API clients should not have to change. New semantics should be in a new API. Roland Häder likes this.Temporary Marjolein repeated this. -
Roland Häder (roland)'s status on Saturday, 17-Jan-2015 16:00:36 CET Roland Häder Well, in one hand you have the benefit of letting #twitter applications connect to your !gnusocial instance but on other hand, the twitter API is #propritary and the GNUSocial is #free-libre. clacke repeated this. -
clacke (clacke)'s status on Saturday, 17-Jan-2015 16:14:22 CET clacke @roland There is no contradiction in having a legacy Twitter API and a new API with richer semantics. Roland Häder likes this. -
AndStatus@quitter.se (andstatus)'s status on Monday, 19-Jan-2015 08:43:14 CET AndStatus@quitter.se @clacke @lnxw37@quitter.se Actually I think that _extending_ what was originally the "Twitter compatible API" is a good approach clacke repeated this. -
clacke (clacke)'s status on Tuesday, 20-Jan-2015 23:07:51 CET clacke @andstatus But not if it means making non-backwards-compatible changed to semantics.
-