jk.nipponalba.scot website https://jk.nipponalba.scot
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
This repo is archived. You can view files and clone it, but cannot push or open issues/pull-requests.
 
 
 

1.2 KiB

slug date posttype mastodonlink
1606003755 2020-11-22T00:09:15+00:00 note https://social.nipponalba.scot/notice/A1RHb7rlQLigdNpeOO

Hello #indieweb folks..

Could any of you advise on syndication of media to the mastodon api from your sites?

I've moved from skpy/micropub-endpoint to dg01d/nanopub and so am directly syndicating rather than posting everything via bridgy.. however, I'm struggling with media posts - I've amended nanopub to do what I think it should do in this regard, which is to post the media to /api/v1/media (or v2) endpoint and collate an array of returned ids which can then be used in the subsequent /api/v1/statuses post..

Despite my amendments the status posts (sans media) still work, but despite the fact I can successfully, manually curl a post request which should match that which is being constructed in nanopub, I am receiving a 400 response when I do so.. and hence no json response containing the id keys that I need for the status post which is also returning a 400 response as a result..

If any of you have a php-ish way to handle this, can you offer any guidance? I'd happily opt for another micropub endpoint but I have limited time for hacking and I'm not overly familiar with go, rust etc.