@amit If you're on a WordPress you need this plugin to manually insert links of tweets into those posts that don't explicitly get a link back from Twitter. Bridgy uses it to pair you posts with your tweets.
@amit You have to add u-syndication links to your blog, thats what that plugin does for WordPress. It tells Bridgy where to look for your tweets, then it can send webmentions to you from Twitter.
@zsbenke Yes, exactly. Need to work out a custom solution to get this enabled on the posts. Haven't found the right thread to do this yet though. I do not want this to be manual, syndication is done by micro.blog -- not sure when/how to fetch the links to syndicated copies.
@amit This manual process was my problem too. I've just stopped doing it after a while even with a plugin. If Twitter refuses to support webmentions, well, that's their problems.
@manton That totally makes sense. Just thinking out load though, won't posting first and sending u-syndication link to micropub-endpoint work too? Or is there any technical/design challenge or limitation in doing so?
@amit That will work, but only for people who have a Micropub server with syndication, which I expect is a small percentage of Micro.blog users. Hopefully won't always be like that, but for now want to make sure everyone is supported.
@amit I know you're using Netlify (of which I have no knowledge) but a media endpoint is 'just' a specialised variant of a micropub endpoint that deals with uploading files. I used @aaronpk's Media Endpoint Gist as a starting point.
@manton Thank you, Manton - makes sense. I think, though, those others aren't affected anyway -- for them things stay the same.
Btw I hope I am not butting in too much here, that's not the intention. Just trying to stratch my own itch, hope the syndication is sorted out too.
@amit Always happy to hear the feedback. It's just a matter of prioritizing what will help the most people right now.
@dgold Yes, have that gist tried and tested. But the micropub endpoint I am using does not expose the media endpoint yet, as far as I know.
Which micropub endpoint are you using?
@dgold yes, of course - nanopub. Still on my list of things to embrace. I guess need to start exploring this sooner 👍🏽
@dgold If I’m reading correctly, your build of nanopub doesn’t (yet) kick off the Hugo site build itself. Does that mean you’re doing that manually, or via a scheduled job? I’m really interested in getting this working for my Hugo site, too.
@alans Hi alan! Yes, I never did find a robust or secure way to cause the Hugo rebuild from within nanopub. So, solutions: I tried a webhook that I called with a 'ping'. That was fragile, so I ended up using incron to watch the content folders & trigger rebuilds that way.
@dgold Thanks! Do you also have a “local” content store that you have to sync with the server side, or is everything effectively on the server for you?
@alans I store everything server side. The content store is outside the public directory of the website.
@dgold Understood, thanks again. I’ll tinker with this in the next few days. The big shift for me will be moving the content store to my server and adjusting to working with it there (or syncing local and remote).
@dgold I tinkered with this last night. Auth appeared to work, then throws internal server error out at posting. I’m testing with micropublish.net. Aside from the content paths, are there any obvious places to troubleshoot? Ill try not to lean on you too hard for tech support!
@dgold Thanks, I’ll give quill a try. The error isn’t descriptive at all so it’s hard to track down. I mostly wanted to check if there was a something obvious to you that’s easy to overlook. I’ll keep at it! Thanks for sharing your work.
@dgold Played more with this today and realized I need to use php7 for it. I'm up and running! One issue: when using the 'article' type request (w/Quill) it doesn't load the auth token into $headers['authorization'] so I get a blank response to indieAuth check and a 401 Unauthorized, but only for that type. Other actions, like posting a note, work great. I think they have the same flow, so I'm puzzled again.
@alans I can't understand that at all... As @jeremycherfas mentions elsewhere, the worst form of Feedback is "It works for me".
Perhaps play around with the quill settings, or try sending an article from micropublish.net? Or try PHP debugging with iniset('displayerrors', 'On');
@dgold Thanks for confirming my suspicion that This is Weird. I get the same behavior from micropublish.net; but even weirder, I can hit the endpoint with curl from my shell and the same auth token, and successfully create a post of that type. ¯\_(ツ)_/¯ I'll bang on it some more.
@alans aaaaagh! This is so frustrating. I’ve tried against my test server and I cannot reproduce your error 🤨 it might be worth toggling some settings in quill and see if that improves anything?
@dgold Thanks for experimenting. Could it have to do with the json-based request for the article format? When I send a request like "curl -d "@article.json" -X POST [myendpoint](http://myendpoint/) I get the auth error. The same request as curl -F 'h=entry' -F 'access_token=...' [...] works.
@dgold Aahhh. Tinkering with quill settings is interesting. I turned off the "send HTML content" setting, and it posted!
@alans aha! Now we’re coooking with diesel. I’ll be at a computer again this evening, and will try to see what’s going on at that stage. Glad it’s (mostly) working for you
@dgold Hey! I think I got this figured out. My host somehow suppresses the httpauthorization header, and clients send that header instead of the accesstoken parameter in certain situations. So it breaks. But I can rewrite that header with .htaccess and then use that new auth header, if present, in my code. I have functioning media endpoint and nanopub now! I'll clean up and share back my fork if you're interested. I'm super pleased!