@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.
@ben @theinstantwin There’s no doubt the Mastodon onboarding process is harder than Meta made it. But if the main goal is engagement and distribution, we already know how this story ends.
And in 2016 i could blame Facebook. But now? I’d squarely blame the pub if I saw even one layoff as a result of “The algorithm is reducing our reach.”
Agree. The algorithms bootstrap people into a community in other places... The only value. Instead perhaps mastodon instance Admins should nominate welcome committees alongside mods as a role to ensure joiners get plugged in.
@ben @charlesroper @theinstantwin
Just to add my small opinion to all of this.
I think, in a few ways, the "rake" here was many presuming, rather lazily, that Mastodon is a Twitter replacement. It's a substitute at best, with its own distinct motivations that are notably anti-viral or engagement.
The fediverse or AP protocol at large however is rich with potential, which has been missed in all of this. Beyond masto we can have algorithms, search, etc. Someone needs to build it though.
@jdp23 @ben @charlesroper @theinstantwin
Not sure we're disagreeing here ... ?
What I'm saying is that the broader "rake" was expecting or demanding a platform that wasn't here, and then, depending on how much you expect of news media, bailing wholsesale on the fediverse rather than building within it.
@jdp23 @ben @charlesroper @theinstantwin
Maybe. I think I was not so interested in blaming anyone but pointing out that there was/is a cultural moment with deficiencies/misunderstandings.
I'm personally happy to criticise mastodon for things you'd know much more about. But they're also doing well and I'm seeing other platforms struggle with basic things like scaling to moderate sizes. So I'm also inclined to think we expect too much of masto and not enough of the ecosystem.
@jdp23 @ben @charlesroper @theinstantwin
A little like the Stroustrup line about programming languages: there are only two kinds, those which people complain about and those which nobody uses.
At some point someone just needs to show what mastodon could do differently, successfully and at scale.
And, getting back to news media, it would have been interesting if they tried something.
@laurenshof @ben @theinstantwin @charlesroper @jdp23
Yea, there are some interesting factors there too, as you say. No established culture. Two separate platforms with a degree of symbiosis that are also kinda the underdogs against masto.
In lemmy's case, the core devs didn't want to have the flagship instance, and so there appears to be a flatter organisation amongst admins and contributors.
And they've both survived scaling to a moderate size with decent performance.
@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.
@charlesroper @ben Developing reach and sourcing content are the most expensive parts of #journalism.
The second one seems to be such an easy solve for #mastodon . That's a miss.
@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.
@ben @theinstantwin Precisely.
Ideally, the way Mastodon is designed, a newsroom “onboards” their journalists by hosting a node and setting up their journalists on it.
… I’m building a node now and, lemme tell ya, this is not something I expect just any random newsroom to have the in-house competency to do. It’s getting better, but I think it’s easy for tech folk in particular to underestimate how much “just one sysadmin” costs, or how overworked they are the minute they sign up to the average not-tech-focused firm. So with no additional information, I would assume that “Meta sets it up, all you have to do is have your team sign up for it” is a huge value-add for newsrooms and journalists by itself.
This problem will continue until we stop building tools for regular folks to use that are monuments to all our sins (seriously… four package managers? And curl-to-bash? And pulling github repos? Or you could “just use Docker” which is a whole other can of worms? And that’s just setup; God knows I’m about to throw myself to the lions when I turn this thing on and have to self-admin it).
@mtomczak @ben I don't disagree about the node, especially since the entire point of federation from the news side would be going vertical and owning your instance/distribution.
I think they aren't estimating the true cost of the project though. Investing in a hidden algorithm you don't own and then praying it doesn't change is demonstrably not working.
I suspect it's more $ long term to over-invest in someone else's distribution/platform then pay a sysadmin.