From 91e3ec1a502e721bef19eec1d839c10a5edad1c5 Mon Sep 17 00:00:00 2001 From: jk Date: Sun, 22 Nov 2020 00:09:19 +0000 Subject: [PATCH] Scripted auto-commit on change (2020-11-22 00:09:19) by gitwatch.sh --- content/note/1606003755/index.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 content/note/1606003755/index.md diff --git a/content/note/1606003755/index.md b/content/note/1606003755/index.md new file mode 100644 index 00000000..5933ee74 --- /dev/null +++ b/content/note/1606003755/index.md @@ -0,0 +1,16 @@ +--- +slug: '1606003755' +date: '2020-11-22T00:09:15+00:00' +posttype: note +mastodonlink: '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. \ No newline at end of file