Complete this sentence:
-
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.
🫧 socialcoding.. (@smallcircles@social.coop)
#ThoughtProvoker :blobhyperthink: The current fediverse is an evolutionary dead-end for 2 reasons: 1. It has painted itself in a small niche of decentralizing typical social media use cases, by means of post-facto interop and the introduction of protocol decay. 2. Lacking a proper grassroots standardization process, and with the primary mechanism for fediverse extension being only post-facto interoperability, there is no way out. Congratulations to the early adopters, who managed to "cross the chasm" with their own app platforms. It took true grit to become deep #ActivityPub experts, and plug holes needed for your app, but you have made it. Post-facto interop works in your favor now. You are unrestrained to productively add more features in your app, and put them on the fedi wire for others to deal with. To avoid fedi to become less and less attractive to newcomers, we must now consider: “Why do we want to grow the open social web, and for whom?” -- @ben@werd.social http://coding.social/blog/shared-ownership/
social.coop (social.coop)
-
@smallcircles @unattributed
My problem with using person vor journalist is as follows:
- The Organizations are the actual, paying customers (Sales domain, but also grouping element for authorization checks)
- We have journalists on both ends of our software. *our* journalists produce news which the customers journalists use to write their news
- people are everywhere in our system. So we need words to differentiate between themYou may look at domain driven design here, the 'strategic design' parts, that is.
The solutions are to either use more specific stakeholder names than "Journalist", and perhaps make Journalist a stakeholder group.
Or distinguish the bounded contexts that define and restrict the meaning of Journalist to a particular sub-domain. Bounded contexts form consistency boundaries in the software design, and when you communicate across boundaries you can take contextual or semantic differences into account.
That is the part where tactical patterns apply, like an anti-corruption layer between the different journalistic contexts.
ECommerce is the usual example, where an Order has a different meaning to the Sales domain than that it has to Billing or Shipping. And the data model of the Order has different fields in each of these sub-domains.
-
You may look at domain driven design here, the 'strategic design' parts, that is.
The solutions are to either use more specific stakeholder names than "Journalist", and perhaps make Journalist a stakeholder group.
Or distinguish the bounded contexts that define and restrict the meaning of Journalist to a particular sub-domain. Bounded contexts form consistency boundaries in the software design, and when you communicate across boundaries you can take contextual or semantic differences into account.
That is the part where tactical patterns apply, like an anti-corruption layer between the different journalistic contexts.
ECommerce is the usual example, where an Order has a different meaning to the Sales domain than that it has to Billing or Shipping. And the data model of the Order has different fields in each of these sub-domains.
@smallcircles @unattributed
I do know about bounded contexts and DDD. Our code is structured to make clear in which context we move. I guess its more of a "Ubiquitious Language" Problem when talking with people about what we need to do and what not.
Did I mention that not *all* our "users" are journalists? Some are just "consumers". So I still need a word to mean both at the same time as they are the ones to get authorized to different parts/services of our Software. -
Yes, a nice depiction. An intricate social networking landscape is shaping up, where our social graphs fan out to interact in many different social settings and contexts. Lovely, thank you.
@smallcircles Yes, something like that. Including its chances regarding diversity, but also its challenges related to community management, bridging gaps and keeping infrastructure both working and at a sane level. Maybe it's similar problems in general, no matter which kind of network one's talking about.
-
@smallcircles Yes, something like that. Including its chances regarding diversity, but also its challenges related to community management, bridging gaps and keeping infrastructure both working and at a sane level. Maybe it's similar problems in general, no matter which kind of network one's talking about.
@z428 yes, this is the focus area of Social experience experience design, which takes on the challenge of overcoming the wicked challenge of cocreation at scale in "herding of cats" grassroots environments, where regular top-down forms of organization and governance like community-building are doomed to fail.
Joyful creation for the Social web
We reimagine the social web and cocreate a peopleverse.
Social coding commons (coding.social)
-
Yes, ubiquitous language. I created an excalidraw copy of a diagram that you see quite often to explain the idea. I adapted it slightly for the purpose of https://coding.social
I can't say what are best name choices in your case, but at least I feel confident that it is possible to entirely avoid "user" and benefit from some extra clarity by doing so.
@smallcircles @unattributed
Hmm... Well.... I thought at least a good year about these questions and did not yet come up with better words.
I mean, yes, our journalists are creators, which clarifies that. But then our users would be consumers and thats not better. And I cant call them journalists as not every user is one. So client maybe? But that would be a better fit for the Organizations as they are the ones talking with sales and paying the money.
All in all: I really am at a loss for better words here.
Nonetheless, thank you for your time
-
Complete this sentence:
"I experience #fediverse as a .."
-
@smallcircles @unattributed
I do know about bounded contexts and DDD. Our code is structured to make clear in which context we move. I guess its more of a "Ubiquitious Language" Problem when talking with people about what we need to do and what not.
Did I mention that not *all* our "users" are journalists? Some are just "consumers". So I still need a word to mean both at the same time as they are the ones to get authorized to different parts/services of our Software.Yes, ubiquitous language. I created an excalidraw copy of a diagram that you see quite often to explain the idea. I adapted it slightly for the purpose of https://coding.social
I can't say what are best name choices in your case, but at least I feel confident that it is possible to entirely avoid "user" and benefit from some extra clarity by doing so.
-
@smallcircles I experience the fedi as network of cafés with shared seating, or a vast food court with characters and conversations galore.
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 -
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.
🫧 socialcoding.. (@smallcircles@social.coop)
#ThoughtProvoker :blobhyperthink: The current fediverse is an evolutionary dead-end for 2 reasons: 1. It has painted itself in a small niche of decentralizing typical social media use cases, by means of post-facto interop and the introduction of protocol decay. 2. Lacking a proper grassroots standardization process, and with the primary mechanism for fediverse extension being only post-facto interoperability, there is no way out. Congratulations to the early adopters, who managed to "cross the chasm" with their own app platforms. It took true grit to become deep #ActivityPub experts, and plug holes needed for your app, but you have made it. Post-facto interop works in your favor now. You are unrestrained to productively add more features in your app, and put them on the fedi wire for others to deal with. To avoid fedi to become less and less attractive to newcomers, we must now consider: “Why do we want to grow the open social web, and for whom?” -- @ben@werd.social http://coding.social/blog/shared-ownership/
social.coop (social.coop)
@smallcircles I experience the fedi as network of cafés with shared seating, or a vast food court with characters and conversations galore.
-
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.
🫧 socialcoding.. (@smallcircles@social.coop)
#ThoughtProvoker :blobhyperthink: The current fediverse is an evolutionary dead-end for 2 reasons: 1. It has painted itself in a small niche of decentralizing typical social media use cases, by means of post-facto interop and the introduction of protocol decay. 2. Lacking a proper grassroots standardization process, and with the primary mechanism for fediverse extension being only post-facto interoperability, there is no way out. Congratulations to the early adopters, who managed to "cross the chasm" with their own app platforms. It took true grit to become deep #ActivityPub experts, and plug holes needed for your app, but you have made it. Post-facto interop works in your favor now. You are unrestrained to productively add more features in your app, and put them on the fedi wire for others to deal with. To avoid fedi to become less and less attractive to newcomers, we must now consider: “Why do we want to grow the open social web, and for whom?” -- @ben@werd.social http://coding.social/blog/shared-ownership/
social.coop (social.coop)
@smallcircles an app as a doorway to something.
How do you see the the people verse, within ans beyond the app paradigm? -
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@django very much so. I particularly like your last observation, thank you.
-
@smallcircles an app as a doorway to something.
How do you see the the people verse, within ans beyond the app paradigm?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.
-
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.
🫧 socialcoding.. (@smallcircles@social.coop)
#ThoughtProvoker :blobhyperthink: The current fediverse is an evolutionary dead-end for 2 reasons: 1. It has painted itself in a small niche of decentralizing typical social media use cases, by means of post-facto interop and the introduction of protocol decay. 2. Lacking a proper grassroots standardization process, and with the primary mechanism for fediverse extension being only post-facto interoperability, there is no way out. Congratulations to the early adopters, who managed to "cross the chasm" with their own app platforms. It took true grit to become deep #ActivityPub experts, and plug holes needed for your app, but you have made it. Post-facto interop works in your favor now. You are unrestrained to productively add more features in your app, and put them on the fedi wire for others to deal with. To avoid fedi to become less and less attractive to newcomers, we must now consider: “Why do we want to grow the open social web, and for whom?” -- @ben@werd.social http://coding.social/blog/shared-ownership/
social.coop (social.coop)
This is just me note-taking and cross-referencing.. weaving in public
Gap between socio and technosphere
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 ap…
Discuss Social Coding (discuss.coding.social)
-
Complete this sentence:
"I experience #fediverse as a .."
@smallcircles I was going to answer a cozy village after seeing how crazy a place like BlueSky is whenever emotions run hot, but then I realized that effect is exactly the opposite of a cozy village.
The best and worst part of a cozy village is that you know everyone, but you can't get away from them so the limited diversity means you're always stuck on the same things. If you don't enjoy those exact same things you either keep to yourself or you leave.
In a bustling city, it takes effort to find your tribe. Even though you're in a much larger population center, your in-group can end up being far smaller than it would be in a cozy village because everyone has a much larger number of choices of groups they can belong to.
Being lost and NOT being able to quickly feel like you belong is exactly what you'd expect to experience in a bustling city.
-
This is just me note-taking and cross-referencing.. weaving in public
Gap between socio and technosphere
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 ap…
Discuss Social Coding (discuss.coding.social)
@smallcircles You have confused me no end there. Couldn't find any point in it.
-
@smallcircles You have confused me no end there. Couldn't find any point in it.
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).
-
Complete this sentence:
"I experience #fediverse as a .."
@smallcircles international conference
-
@smallcircles international conference
@jackeric I like that. It is an original take, thanks.
-
Complete this sentence:
"I experience #fediverse as a .."
