@manton Would love to be able to import posts from Substack. It’s the only major blogging platform missing from your otherwise exhaustive list.

P.S. I’m moving my personal blog from Substack to micro.blog! 🙌🏼 But that also means I’m having to manually import every post. :/

@uncertainquark I’ll look into the Substack export format and see what it would take to support it. Thanks!

@uncertainquark you can definitely export substack and reimport somewhere else - looking at possibility of buttondown .. and did it there … the biggest issue around images .. substack handles image sizing on the fly … buttondown currently requires you to size images correctly.

// @manton

@uncertainquark and podcasts

@uncertainquark Nice. The interesting thing about our WordPress import is that it’s actually RSS with some custom WordPress-y tags in it… It might partially work with other RSS feeds.

@manton Interesting. BTW I’m not seeing this reply in my Mentions. Has happened with multiple replies since the last week despite people directly tagging me. I just happened to stumble on this and the others when viewing the original post(s).

@uncertainquark Thanks, I do think there is an issue with Mentions… Looking into it.

@manton Glad you’re on top of this. I think I wrote a few days ago that this wasn’t working. Was starting to think it was me.

@manton Are you able to go back through unsent ones?

@cdevroe Probably. Need to figure out exactly what is happening first.

@manton Re-reading this thread I see @uncertainquark is saying Mentions. I meant webmentions. Haven’t seen one sent to my blog in a few weeks from M.b.

@manton I miss webmentions.

@cdevroe I’ve been looking into this, and I don’t think it’s a Micro.blog bug. I noticed that a Webmention sent to your site is getting a 500 error back… “cURL error 60: SSL certificate problem: certificate has expired”

@manton hmmm. Is that for cdevroe.com? Will look into it. Does M.b ever try non-HTTPS?

@cdevroe https for that site doesn’t load for me on Safari (High Sierra).

@cdevroe Yes, it’s using what you have set for your endpoint, which is non-HTTPS. The “curl” error is something triggered on your side… Micro.blog’s connection to your endpoint is working fine and I get a JSON response with the error.

@manton I’m using @pfefferle‘s WordPress plugins for webmentions. I’ll see if they have a setting for allowing non-HTTPS requests.

As an aside, I really do need to figure out HTTPS again for my site. I’m on Digital Ocean. If someone wants to offer a hand.