Pushed v0.12.1 of Share on Mastodon yesterday. It can now be “tricked” into cross-posting video and audio (from WordPress’ media library to Mastodon) as well. Quick example: https://gist.github.com/janboddez/5c6a69ca603d42b53904f7af6b2ad030 Disclaimer: File type and size limitations apply.
Modified my “Share on Mastodon” mu-plugin, i.e., where I keep my PHP filters/tweaks, to correctly “thread” cross-posted replies to not only notes, but articles as well. https://indieweb.social/@janboddez/109884956066372057
Should probably share the exact code, but it looks something like https://jan.boddez.net/wordpress/share-on-mastodon#threaded_toots, i.e., I’m using a regex to look up the note or article I’m replying to and then fetch its syndication URL, which I use to derive and set an in_reply_to_id parameter.
Spent the evening experimenting with Gutenberg’s PluginPrePublishPanel. Thought it’d be nice if I could move Share on Mastodon’s “meta box” there. Think Jetpack does something similar.
Now I’m not so sure anymore. On the one hand, it may help prevent sharing when updating old posts. On the other, it’s almost too easy to simply disable the panel, so I’d probably still need a regular PluginDocumentSettingPanel.
Also, the way I currently process the old-style meta box interferes with Gutenberg’s setMeta(). No biggie, we can turn that off. Except … there’s still that “Custom Fields” panel (which I have open often): https://github.com/WordPress/gutenberg/issues/23078.
Conclusion, at least for now: I’m sticking with a regular meta box. (Which within Gutenberg looks somewhat out of place, but not horribly so.)
Added some major improvements to Share on Pixelfed just now. Planning to release before the end of the week.
Added to Share on Mastodon’s “latest nightly,” so to speak: (1) the ability to upload not just featured and attached images, but also images in the post; (2) more robust alt text; (3) (server) error messages; and (4) (optional) admin notices.
Posting two random images through Micropub.
Ha, Chris Coyier linking to Terence Eden’s article (on extending one of my tiny WordPress plugins) linking back to my site is kinda cool!
(There’s yet another filter hook, by the way; lets you add a CW, adjust post visibility, and more.)
When I exclusively used WordPress’s classic editor and Jetpack’s Markdown module (or Easy Markdown), syndicating Markdown to, e.g., Mastodon, was easy. (Both plugins store unparsed Markdown in post_content_filtered, so I’d cross-post that.)
Now that I spend more and more time in the block editor, I have this issue where blockquotes, once syndicated, are no longer recognizable as (block)quotes—I strip away HTML before POSSEing, and there’s no > or nothing in the original post.
Might eventually solve this by converting (all) HTML to Markdown first.
In reply to https://jan.boddez.net/notes/11d0756b16.
Which is, of course, exactly what has happened with my crossposting plugins. :-)