4 ms·
> Why pay for a service, and have the little mental overhead of it existing, when I’ve duplicated it on my own site? For me, because Pinboard has IFTTT integra
by zimpenfish 2y ago
> Why pay for a service, and have the little mental overhead of it existing, when I’ve duplicated it on my own site?
For me, because Pinboard has IFTTT integration where I can feed a whole bunch of things[0] into it automagically. None of the self-hosted services has IFTTT integration or, as far as I've seen thus far, webhook functionality I could feed from IFTTT[1].
I've got a self-made feed from Pinboard to a self-hosted linkhut which works fine (absent the archiving capability but I've never really used that anyway.)
[0] Although sadly that list does keep shrinking as arseholes close off / commercialise their APIs.
[1] A REST API doesn't work because they rely on setting the 'Authorisation' header which, AFAIK, isn't supported in IFTTT's webhook.
- landhar 2y agoHi, linkhut dev here. Just wanted to call out that linkhut does have IFTTT integration [0]. Although you will need to pay for an IFTTT developer account if you want to enable that on your self hosted instance. If you need help setting that up let me know, I’ll be happy to walk you through the process (and that way I can write documentation on how to do it). Edit: I also was under the impression that one could use the webhooks integration [1] to make bespoke integrations (as the documentation says they support passing arbitrary request headers) but haven’t tried it myself, have you tried it and run into any issues? I’d also be happy to help improving support for that workflow. [0] https://ifttt.com/linkhut https://ifttt.com/linkhut [1] https://help.ifttt.com/hc/en-us/articles/115010230347-Webhooks-service-FAQ https://help.ifttt.com/hc/en-us/articles/115010230347-Webhoo...