clacke@libranet.de ❌

clacke@libranet.de ❌ at

I realized I'm not following Sumana Harihareswara so I tried to remedy that.

Logging into identi.ca with my datamost ID crashes identi.ca. So I tried sharing posts using my old identi.ca ID, which I am following. The shared posts don't show up on datamost. I tried using "Act as:" on AndStatus to find posts using my identi.ca ID and try to follow or repost as my datamost ID. Nope nope.

followUser userId=2688, oid'acct:brainwane@identi.ca', webFingerId:'brainwane@identi.ca',
Status code=INTERNAL_SERVER_ERROR; hard;
; statusCode:INTERNAL_SERVER_ERROR (500); url:'https://datamost.com/api/user/clacke/feed'; authenticated; posted:'{"objectType":"activity","verb":"follow","generator":{"id":"http:\/\/andstatus.org\/andstatus","displayName":"AndStatus","objectType":"application"},"actor":{"id":"acct:clacke@datamost.com","objectType":"person"},"object":{"id":"acct:brainwane@identi.ca","objectType":"person"}}'; response:'TypeError: upstreamDuplicates is not an…'; error='?';
Caused by org.json.JSONException: Value TypeError of type java.lang.String cannot be converted to JSONObject,

Show all 6 replies

You probably won't be able to follow her from datamost.com at this time. I certainly can't.


The dreaded "upstreamDuplicates" bug.

JanKusanagi at 2017-03-28T12:14:42Z

clacke@libranet.de ❌ likes this.

Oh. That's old.

https://github.com/pump-io/pump.io/issues/801

And yeah, the statement about the data is true: ...
,"upstreamDuplicates":{"0":"http://identi.ca/user/75508"} ...

I'm guessing identi.ca won't get this fixed any time soon, so maybe the parser should be more tolerant.

clacke@libranet.de ❌ at 2017-03-28T14:36:51Z

From what I've gathered during all this time, when this happens (to certain identi.ca users from some other servers**), it's because the server unable to follow that user has old/corrupt/incorrect data about that user. I've seen that go away after that identi.ca user updates their profile, follows someone on the affected server, etc (probably a combination of several of those things).


Maybe it would help if she tried to follow you, and then posted something with "you" in the "To" field.


I wish I was in control of one of those affected accounts xD


** The issue can affect user1@identi.ca as seen by users @datamost.com, but have no issues for users @microca.st for instance. Then users of datamost.com might be able to follow happily user2@identi.ca, while users of microca.st are unable to follow this one. It's a matter of what """version""" of that identi.ca user's profile your server has. It happens _only_ with identi.ca users, AFAIK, and once a user at your server can follow the affected user, all users on your server can.

JanKusanagi @identi.ca at 2017-03-28T18:22:47Z

clacke@libranet.de ❌ likes this.

Oh! So that data is not necessarily on the identi.ca side, which is what I assumed after reading that issue.

clacke@libranet.de ❌ at 2017-03-29T19:25:21Z