Complete this sentence:
"I experience #fediverse as a .."
Complete this sentence:
"I experience #fediverse as a .."
What no one has remarked thus far, is that this #poll has a serious flaw. Sure, if you're in a village or city you can find roads and highways that lead you to answer the question above.
But if you are in a Ghost Town out in the wilderness, the poll likely won't pass by your timeline. And warp the outcome of this little #fediverse survey.
Boosts are appreciated so the poll has more chance to find the outer reaches of our fedi universe.
Even more remarkable is the near complete absence of the #ActivityPub developer community in mingling in the social side of the discussion.
To learn how #fedizens actually *experience* this here fediverse. A #fediverse which results from them tying their apps together, to hopefully get more than the sum of individual parts. By means of facilitating #interoperability, technically speaking. But it involves more than getting that feature across the wire to the next app.
There's exists a clear gap between #sociosphere and #technosphere, where the latter must serve the former to bring real solutions. Otherwise it is all apps and not much seamless social fabric to navigate. No peopleverse anywhere in sight. Just apps and users of them.
The apps see great success, and I enjoy their use a lot. But I don't see a future for the app-centric fediverse where it comes to providing mankind the future of #SocialNetworking.
This is just me note-taking and cross-referencing.. weaving in public :)

Adding a marker to this poll on how people experience the fediverse, with absolutely delightful outcome and responses, but also showing the huge gap to the developer community who seem to be lost in tech and their own app domains. Where the foundational technology base languishes and deteriorates, ever more incapable of addressing the needs of the broader public and bringing the future of social networking, a peopleverse.
Don't worry it is more a note-to-self on the forum which serves as note-taking tool. The link it includes is to the poll at the top of this thread. Other than that I have tooted all over the place on the subject matter, which is unfortunately now all dispersed and sinking in timeline history (though I kept a bunch of bookmarks).
Within this multitude different folks have different needs and desires, some are testing the waters, some are regulars.
Even the impulse for networked sociality ebbs and flows.
@smallcircles
In a technical sense constituting a shift towards a fediverse of apps and services.
In a social sense as inter-connected spaces that are open for people to explore, collaborate, cocreate, and do all the things we do offline to the extent we can do them online too, plus all the extra's that remote connection by technological means have to offer.
But that is an exploratory design area. A vast space hardly explored. This is where Social experience design focuses. See the diagram at https://coding.social where SX broadens horizons by taking a more holistic approach (actually utterly holistic and boundless in scope, as SX scales from personal to societal levels).
What #SX envisions is a peopleverse. A hypothetical place-to-be in the future where our online and offline worlds are seamlessly intertwined and in services of our day to day activities and human needs.
@smallcircles "Even more remarkable is the near complete absence of the #ActivityPub developer community in mingling in the social side of the discussion."
Once you've been here for a little longer you'll realise this statement isn't the case.
You are certainly not wrong. And I apologize, as it is not immediately clear that my post above is against the backdrop of 2 weeks of microblogging addressing a whole range of paint points and inhibitors to a fedi that evolves to be the future of social networking. Microblogging is too fragmentary and 'context-lossy', but unfortunately the primary comms channel for the dev community.
The gist and big issue is that the current fediverse is app-centric in nature, and accepted a work method that will further that app-centricness by introducing ever more protocol decay and tech debt. The examples you gave above are app talk, turn to features, howto federate feature, tech talk, get mired in impl details. And importantly: do not catch up with standards. That is up to some poor volunteers, who see that things are going side-ways.
There are 2 fediverse forks: the promised one in the AP specs, and the one we have. There's no shared vision, and tons of misconception to deal with.