@ben I remember this same statement being made in 2014. “We have to get on Facebook.” Then “We have to pivot to video.”
You know the rest. There is no one more of a glutton for punishment than news media. There is no rake they won’t step on.
@charlesroper @ben I actually see the challenge in a bit more (admittedly cynical) way. Not to paint a broad brush, but journalism in 2023 is deeply and destructively lazy. (See: Any and all pubs who covered Amazon Prime Day as a news story.)
One of the best ways to boost reach for journalists is - and this is basic - making embedding Toots in WordPress dead simple.
@charlesroper @ben Then quoting a source directly and rewarming whatever the source said (This is what passed for "#journalism" in the #Twitter era) would be as simple as it was before.
That's the biggest mystery to me. Why not work with the #WordPress core team to embed toots right now?
Reach would explode.
@theinstantwin @ben This was announced a couple of days ago:
https://jetpack.com/blog/automatically-share-content-to-instagram-mastodon-with-jetpack-social/
So they're actively working on it. This looks like a way to make it easier to publish stuff. But it's progress.
@theinstantwin @charlesroper @ben You can in fact. in the block editor, create an embed block, and paste your URL to the post on mastodon in, and it will embed it.
While WordPress has various blocks for embedding from social networks and such, the general embed block uses oEmbed, and it can embed anything that supports the oEmbed protocol. Of which, mastodon is one.
@otto42 @charlesroper @ben Not sure if it's my theme, a plugin, etc... but this is what happens
With Twitter, Spotify, etc. -- the embed looks beautiful and works well out of the box and is theme agnostic.
@theinstantwin @charlesroper @ben Yeah, unfortunately, that's a mastodon problem. Basically, it's falling afoul of the same origin problem. And the mastodon server needs to return a Access-Control-Allow-Origin: * header for embedded resources to allow other sites to properly embed stuff like CSS, JS, etc..
If you look in the browser console, you'll find a whole slew of different things it's trying to load, but can't because CORS/Same-Origin policy.