Didn’t realize this was missing but now that I’ve implemented it, I love it. Post to your blog, someone replies in Bluesky. The reply appears on your blog. If you reply back on Bluesky, that reply is included in the conversation on your blog too.
Didn’t realize this was missing but now that I’ve implemented it, I love it. Post to your blog, someone replies in Bluesky. The reply appears on your blog. If you reply back on Bluesky, that reply is included in the conversation on your blog too.
@manton That’s great. No more conscious effort of seeing a reply in Bluesky and having to switch apps to reply within Micro.blog
@manton Very handy for when Bluesky's notifications pull me in to reply there “by mistake”. Thank you!
@manton where does someone have to reply in Bluesky for the reply to appear on your blog post?
@eatyourglory They can reply to the cross-posted version of the post on Bluesky. Micro.blog automatically sends a copy to Bluesky, then people can reply to that.
@manton Unsure if this is related, but replies made on Micro.blog that are sent to Bluesky appear to miss out on some Markdown conversion. bsky.app/profile/h...
thank you for the free Bluesky cross-posting integration!
Any chance the links to cross-posted Bluesky entries are made available in the Micro.blog API? These seem to only be available in the Hugo front matter.
@kandr3s You're right, the cross-posted metadata isn't available in the API. I'll add it today. I think in API calls such as /posts/your-username it can include those links in the _microblog
namespace. Or were you thinking something different?
@kandr3s Thanks! Just in case it's not clear, Micro.blog iOS and Epilogue should be able to post to Micropub servers now, but more needs to happen to decouple the other features from Micro.blog.