Threads API is the big news of the week. Credit to the Threads team for pulling it off.
But what if Mastodon's fedi:creator footnote tells a bigger story? While the Threads API takes us down a well worn path, re-centring the #Fediverse on blogs, podcasts, forums and curation takes us somewhere new. See you there! We can meet around @johnonolan 's campfire.
I don't know how to conceptualize the story, though.
It sounds to me like (bear with me) the proposal is to recenter microblogging around long-form content, by which they mean linking out to longform content elsewhere
That is full of contradictions, though, both in the conflict between micro- and long- and in longform being on the outside, not the center.
I WISH there would be a recentering around long-form content, but this doesn't sound like that.
@johnonolan sure, although I think it needs to be appreciated that there are a lot of people who flat out reject long-form content here, so they would oppose any such move.
Personally, obviously that's not my position🙂
But to be clear, my feedback was to say that I wasn't really sure what was being said, personally I would love more long-form content on the platform and I wish there would be more, but I couldn't tell if the composition was actually promoting that or not.
@johnonolan I agree, though I would phrase it as each interface tailoring itself for presenting the content coming to it as its users need it to.
I think that when talking about Fediverse engineering all too often the needs of users, the wants of users, doesn't get enough attention in the conversation.
Just a slight nitpick 🙂
I hear a lot of Mastodon users, for example, flat out saying they don't want long-form content, and so I would phrase it as, Mastodon uis will display or not display long form posts in response to users who don't want to see it that way.
Anyway, again, not disagreeing, just blabbering :)