Uses mastadon rather than others (eg github) but gives reasons why. Currently, it's a multi step process it seems;
> I do have to create the mastodon post, right now I just edit the file again and push the changes with the proper id.
> I could create the posts first with the soon-to-be link for the blogpost, but it would be confusing.
> Right now I am thinking about doing some hook with the cli tool `toot` to post the link and do some stuff with sed, echo and then another git push. But meh, manual works too
So, create the blog post, then mastadon post, grab it's id and put it back into jeykll and resubmit.
Hey, this is the original author of the blog, it really sounds easy to automate, I am just lazy.
I already have a script to setup Jekyll's metadata.
I could use toot, a terminal utility to post the blog, using the description as the toot content and since the command returns the toot's url I could echo that and do some sed magic.
I havent had the time to set it up but I will write about it once I have the time...
You can also use https://utteranc.es/, which uses GitHub issues for blog comments. This works well for a lot of Jekyll blogs that are already hosted on GitHub Pages.
I feel like this is just a service that github/lab could provide officially for blogs. Then they could do it in a nice and performant way and it would add a lot of value to their product.
8 comments
[ 2.9 ms ] story [ 18.0 ms ] thread> I do have to create the mastodon post, right now I just edit the file again and push the changes with the proper id.
> I could create the posts first with the soon-to-be link for the blogpost, but it would be confusing.
> Right now I am thinking about doing some hook with the cli tool `toot` to post the link and do some stuff with sed, echo and then another git push. But meh, manual works too
So, create the blog post, then mastadon post, grab it's id and put it back into jeykll and resubmit.
I havent had the time to set it up but I will write about it once I have the time...