Share on Mastodon v0.19.1
Version 0.19.1—one day I’ll be ready, psychologically, for a 1.0 release—addresses 3 bugs. One had to do with image uploads failing on certain PHP installs. The other two changes should bring the block editor in line with the classic editor. That is: On publish (or update), the “Share on Mastodon” toggle should no longer temporarily […]
One of WordPress’ block editor’s “nastiest” quirks is how it deals with “classic” meta boxes, including the Custom Fields panel.
It’s why in my ActivityPub add-on plugin, I had to “delay” federation to a later hook (than transition_post_status [and use a static variable to temporarily store the new and old post statuses], but only when rather specific conditions are met).
Anyhoo, I literally wrote about this countless times, and still occasionally get it wrong.
One of WordPress’ block editor’s “nastiest” quirks is [how it deals with “classic” meta boxes](https://jan.boddez.net/articles/wordpress-block-editor-and-custom-post-meta), [including the Custom Fields panel](https://jan.boddez.net/articles/the-block-editor-custom-meta-and-activitypub).
It’s why in my ActivityPub add-on plugin, I had to [“delay” federation to a later hook](https://github.com/janboddez/addon-for-activit…
Wondering if anyone would ever be willing to pay for a “pro” version of #ShareOnMastodon, seeing how niche it is.
I was thinking multi-author support, which is something (independent) magazine-style sites might find useful. Or even sharing to more than one account.
Or (better) blocks (sporting a link preview or something), like to make it clear(er) that a post can be interacted with on Mastodon.
Or threading.
Or crossposting audio and video.
Excited to be "working" on #ShareOnMastodon (a silly #WordPress plugin) again, although I'm starting to wonder if any extra features shouldn't go into a "premium" add-on plugin, for instance.
Don't get me wrong, I'm not planning to drop #ActivityPub, although it comes with quite some quirks still. (Someone drops a reply, then changes their avatar: Yay, you've now got broken images [potentially] all over your blog. Also, you can't, e.g., not federate specific posts or categories.)
Playing with multiple account support for Share on Mastodon.
Right now, all posts (that are crossposted) get crossposted to one and the same account. (I.e., your WordPress install acts a Mastodon client, for a single account, and a single instance.)
Having different settings for each and every user is a whole lot trickier, though.
Like, you could have multiple users on one instance, and then more users on other instances. Ideally, you’d autoregister—this all happens in the background—as a client application only once per instance.
But how do you guarantee “old” instance details aren’t outdated, etc.? And do you then store them in a custom table? And so on.
(The current implementation isn’t necessarily great either, because if you were to somehow wipe your client details, WordPress would just re-register itself and be given a new client ID from the instance you entered.)
Playing with multiple account support for Share on Mastodon.
Right now, all posts (that *are* crossposted) get crossposted to *one and the same* account. (I.e., your WordPress install acts a Mastodon client, for a single account, and a single instance.)
Having different settings for each and every user is a whole lot trickier, though.
Like, you could have multiple users on one instance, and then more users on other instances. Ideally, you…
Thomas Schmidt 
mvanmartijn
Jan Boddez
Jan Boddez