Conversation

Notices

1. AndStatus (andstatus@loadaverage.org)'s status on Thursday, 23-Aug-2018 06:04:51 UTC AndStatus

   • thefaico
   @roka Does this work with any other Pleroma instance? I mean is the problem in compatibility with Pleroma in general or just with your site's setup? In order to figure out a problem from #AndStatus side you could:
   1. Lookup errors in Menu -> "Commands in a queue"
   2. Turn on verbose logging with saving logs to files, and later analyse logs of a Note with an attachment sending. More on logging in AndStatus is here: https://github.com/andstatus/andstatus/issues/225
   • DEATH TO GASTONS DESU~ (roka@pl.smuglo.li)'s status on Friday, 24-Aug-2018 02:43:33 UTC DEATH TO GASTONS DESU~

     in reply to

     • 仮面の告白
     • :bunny:
     • takao
     @andstatus I didn't have the chance to make an account on another Pleroma instance yet but I did gather some logs. Unfortunately I had to repeat this several times because queue requests leftover from previous attempts at testing (and cross-referencing behaviour with that of a real GNU Social server) kept polluting the log.
     
     I noticed two issues in those past runs, at least one repeats in this batch of logs:
     a) AndStatus on OStatus endpoint of Pleroma instance tried to query /api/account/rate_limit_status.json - this fails because https://pl.smuglo.li/api/account/rate_limit_status.json returns the Pleroma Fe UI with empty content part; meanwhile Shitposter.club, a real GS instance, returns a JSON document after auth - thus cc-ing @lain and @kaniini ; this problem pops up in „commands in a queue” view as well
     b) it did the same by accessing /api/statuses/show.json?id=X (where X is an ID) - again, Pleroma just serves a webpage
     
     Attached is a zipfile featuring logs of an attempt to send a post with a file attached on AndStatus with data purged beforehand via Apps screen in Android settings - it still seems to have references to my previously setup alt at @takao but it's much easier to read than it was before. Post composition starts in logs/2018-08-24-04-18-41_log.txt
     
     The result is a post with text but no attachments *shrugs*
     smugfreshest.zip
     AndStatus repeated this.
   • AndStatus (andstatus@loadaverage.org)'s status on Friday, 24-Aug-2018 06:21:37 UTC AndStatus

     in reply to

     • thefaico
     • DEATH TO GASTONS DESU~
     @roka Thanks for these logs, I will look at them closer today. Currently I see that for some reason a note, posted to Pleroma, doesn't have an attachment even in its metadata...
     Please clarify: do you see attached images in the downloaded posts that have images when looking via web interface? I mean, if only _posting_ images from #AndStatus to Pleroma doesn't work?
   • AndStatus (andstatus@loadaverage.org)'s status on Saturday, 25-Aug-2018 04:15:29 UTC AndStatus

     in reply to

     • thefaico
     • DEATH TO GASTONS DESU~
     @roka Thank you again for logs provided. This line in a log tells that a Note with an Attachment was sent to a server (in one HTTP post action) and a server responded with OK (200):
     08-24 04:19:03.008 V/HttpReadResult: ; statusCode:OK (200); url:'https://pl.smuglo.li/api/statuses/update.json'; authenticated; posted:'{"status":"Messed it up, again.","source":"AndStatus","media_part_name":"media","media_part_uri":"content:\/\/org.andstatus.app.data.FileProvider\/downloadfile\/at_19_0.jpg"}'; response:'{"activity_type":"post","attachments":[…'
     The note was sent as a Multipart entity (see https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html ). The entity is built in code here: org.andstatus.app.net.http.HttpConnectionApacheCommon#multiPartFormEntity
     The same code is used for GnuSocial, Mastodon and Twitter. And it works there. So I would say that that Pleroma implementation should process the same content correctly also.
     Could you get similar logs for a server side to know why the "media" part of the post was silently ignored or failed there?!