Complete this sentence:
-
Oww, that is interesting. See here what brought me to the #ActivityPub fediverse ages ago on IT timescales..
Read the blog post, and these are astute observation and valuable way of thinking about the networking environment, both offline as well as online, and how they interact together, how they intertwine. #SX envisions a peopleverse (which is a concept, not a name), a hypothetical space where the interaction is seamless and technology unobtrusively serves our day to day needs.
#PersonalSocialNetworking is a powerful instrument to design better social experiences.
Often the talk of the town in the #ActivityPub dev circles is about some feature or other, an app functionality and the extent to which it can be made interoperable. Technical implementation details dominate the discussion. And drama ensues on the broader #fediverse if social impact and other externalities are overlooked in an app design.
When comparing #microblogging we have today, it really is like sticky notes on the fridge, which fall off or are removed by people. And we project all communication modes onto them.
-
Read the blog post, and these are astute observation and valuable way of thinking about the networking environment, both offline as well as online, and how they interact together, how they intertwine. #SX envisions a peopleverse (which is a concept, not a name), a hypothetical space where the interaction is seamless and technology unobtrusively serves our day to day needs.
#PersonalSocialNetworking is a powerful instrument to design better social experiences.
Often the talk of the town in the #ActivityPub dev circles is about some feature or other, an app functionality and the extent to which it can be made interoperable. Technical implementation details dominate the discussion. And drama ensues on the broader #fediverse if social impact and other externalities are overlooked in an app design.
When comparing #microblogging we have today, it really is like sticky notes on the fridge, which fall off or are removed by people. And we project all communication modes onto them.
@smallcircles I very much think you and I have arrived at the same space, perhaps from different directions and with different vocabularies - I'm still very much learning how to communicate my terminologies and I hope it's OK that you've prompted me to shift into some of yours!
My paid-work background is +/- 30 years in "tech support", but much involved roles with titles related to "integration" , "deployment" and "client care". Good tools are made when we start with UX/SX and work back.
-
@smallcircles I very much think you and I have arrived at the same space, perhaps from different directions and with different vocabularies - I'm still very much learning how to communicate my terminologies and I hope it's OK that you've prompted me to shift into some of yours!
My paid-work background is +/- 30 years in "tech support", but much involved roles with titles related to "integration" , "deployment" and "client care". Good tools are made when we start with UX/SX and work back.
@smallcircles I'm now a (hopefully temporarily) unwaged grad student in an interdisciplinary urbanism/planning/systems program mashing that all up with community-first technology planning.
I have a seminar discussion tonight on a recently assigned "The Mayor's Brief" paper, and I took the approach of presenting and argument that Cities need to own their own social technology tools.
Remains to be seen how well I did that!
-
Oww, that is interesting. See here what brought me to the #ActivityPub fediverse ages ago on IT timescales..
@smallcircles Oh, yeah.
I follow Evan, and Julian, but those threads sometimes cause me to glaze over - I've never been "a coder".
That said, I just re-read that one and holy cow, I'm seeing lots of analogies to problems with the DICOM protocol which DID drive my tech services/deployments work for decades.
One of the hardest challenges in keeping a human patient's medical records in order, and secure, is that different stakeholders need different relational connection to different components
-
@smallcircles Oh, yeah.
I follow Evan, and Julian, but those threads sometimes cause me to glaze over - I've never been "a coder".
That said, I just re-read that one and holy cow, I'm seeing lots of analogies to problems with the DICOM protocol which DID drive my tech services/deployments work for decades.
One of the hardest challenges in keeping a human patient's medical records in order, and secure, is that different stakeholders need different relational connection to different components
@smallcircles DICOM data structures get crazy twisted, because every element in a recordbase could potentially be the point which is seen as the "root" from which everything branches.
Radiologists view Images, which have attributes including the Study, the Order, and the Patient.
Clinical care delivery people need Reports, which derive from Studies but also include Orders and Patients as attributes.
-
@smallcircles DICOM data structures get crazy twisted, because every element in a recordbase could potentially be the point which is seen as the "root" from which everything branches.
Radiologists view Images, which have attributes including the Study, the Order, and the Patient.
Clinical care delivery people need Reports, which derive from Studies but also include Orders and Patients as attributes.
Primary care physicians are concerned with Patients, who come with 1:n relationships with attributes such as Orders, Studies, Reports, referrals, results, diagnoses....
Patients don't give a shit about having any attributes at all, they want to feel better and get the hell away from anything to do with medical technology!
I can see AP being at least as ridiculous as DICOM, though social networking is probably slightly lower-stakes for most.
-
@smallcircles I'm now a (hopefully temporarily) unwaged grad student in an interdisciplinary urbanism/planning/systems program mashing that all up with community-first technology planning.
I have a seminar discussion tonight on a recently assigned "The Mayor's Brief" paper, and I took the approach of presenting and argument that Cities need to own their own social technology tools.
Remains to be seen how well I did that!
Totally! Cities should have their own tools. I find the whole #SmartCity trend to be dystopic #SurveillanceCapitalism driven, from what I've seen of it. Large corporations in the driver seat, plenty #BigTech, and a general 'drive for control' by technical means, rather than creating and evolving vibrant and safe living spaces by social means and encouragement of close participation of local residents in sustaining that.
It is hard to find sustenance to focus on the important applied R&D in the more social areas, with most #funding and support reserved for the cold hard tech side. While tech can only ever be supportive of "true social". It must address people's needs.
I'm biased but think its urgent to #fund initiatives like Social coding commons and #SX for fedi to stave off existential challenges. I approached @nlnet among others. Current #EU mandate by @EUCommission for @ngi results in a tech-first "code it and they will come", not a peopleverse.
-
Primary care physicians are concerned with Patients, who come with 1:n relationships with attributes such as Orders, Studies, Reports, referrals, results, diagnoses....
Patients don't give a shit about having any attributes at all, they want to feel better and get the hell away from anything to do with medical technology!
I can see AP being at least as ridiculous as DICOM, though social networking is probably slightly lower-stakes for most.
I think what you will find interesting, and what immediately leads to a sort of mindset shift - which is required to fully grasp the holistic approach that SX follows - is that SX defines #SocialNetworking as follows:
"Any direct or indirect human interaction between people."
Period. That's it. It encompasses that vast scope, which includes both our offline and online worlds (handy, to focus on that peopleverse).
A healthcare system is a complex mulitplayer environment, where many people in different stakeholder roles work with sensitive data. That is the technical perspective.
On the social side, it is a social network, for which you can apply SX as the evolutionary solution design methodology.
-
I think what you will find interesting, and what immediately leads to a sort of mindset shift - which is required to fully grasp the holistic approach that SX follows - is that SX defines #SocialNetworking as follows:
"Any direct or indirect human interaction between people."
Period. That's it. It encompasses that vast scope, which includes both our offline and online worlds (handy, to focus on that peopleverse).
A healthcare system is a complex mulitplayer environment, where many people in different stakeholder roles work with sensitive data. That is the technical perspective.
On the social side, it is a social network, for which you can apply SX as the evolutionary solution design methodology.
@smallcircles Absolutely.
I'm out of it now, but wow, it would be immensely beneficial for a patient to truly *own* their medical data lake and just exchange the relevant records when needed.
It would also be several lifetimes' work to do that correctly, I fear, and there are eleventy-million and one startups making their own wrongheaded attempts at it with "patient portals" and "AI health" and other such malwares.
-
@smallcircles Absolutely.
I'm out of it now, but wow, it would be immensely beneficial for a patient to truly *own* their medical data lake and just exchange the relevant records when needed.
It would also be several lifetimes' work to do that correctly, I fear, and there are eleventy-million and one startups making their own wrongheaded attempts at it with "patient portals" and "AI health" and other such malwares.
Just start small and
evolve. A good example is the Netherlands where I live. In the 50s it was as car-heavy as any US state today, but by following a consistent policy we turned it into a bikers' paradise. And that is now an exemplar for other cities and even countries across the world. An export product 
-
Just start small and
evolve. A good example is the Netherlands where I live. In the 50s it was as car-heavy as any US state today, but by following a consistent policy we turned it into a bikers' paradise. And that is now an exemplar for other cities and even countries across the world. An export product @smallcircles hahaha - your example appears somewhere in my world almost daily - urbanism studies, active transportation folks I follow, and in my fediverse-urbanism interconnections all the time.
It's amazing what we can transform if we get the entrenched and unimaginative status quo out of the way.
-
@lproven ouch, I am sorry. At least it serves the goal of making social networking better. And the results thus far we are a long way on the road towards a Personal social networking paradigm shifts that provides you more control in finding the crowd you're most comfortable with.
https://coding.social/blog/reimagine-social/#personal-social-networking
@smallcircles @lproven LOL I have the ability to keep scrolling.
The foetid actual BS of places like LInkedIn have me scurrying back here where people are bein' themselves. -
Complete this sentence:
"I experience #fediverse as a .."
@smallcircles@social.coop Ghost cozy village.
-
@smallcircles@social.coop Ghost cozy village.
@coffeetomorrow that is an original combination. I like it.
-
@coffeetomorrow that is an original combination. I like it.
-
@smallcircles Personal take, after thinking for quite a while about that: A larger metropolitan area in the global Northwest. Not too densely populated but far-reaching and covering a lot of real estate. A lot of roads and interconnects in between different parts, partly along areas that have been somewhat structured but in the end not really grown into /any/ kind of meaningful use. And a lot of more clearly outlined neighbourhoods of very different kinds, styles, attitudes and openness towards new arrivals or strangers, including places were you'd like to settle and stay for an indefinite amout of time and ... places, people you'd better avoid without taking a closer look or even stopping there.
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.
-
When speaking in a general sense, you can substitute with people, person, human. "The user" becomes "the person", and "user-centric" becomes human-centric or people-centric, whatever fits best in context.
More interesting when not just defaulting to saying "user", is asking the question: Whom are we serving with our software? Who is the audience, who are stakeholders and stakeholder groups that have Needs that must be addressed by our solution?
"Joyful creation", the SX formula that envisions cocreation at scale supported by the social web, discerns between Creators and Clients stakeholder groups. If we apply this formula to Software develpment, then creator might be a Dev, but also Tester, Technical writer, etc. People switch stakeholder hats: A dev being client of an upstream project.
In your case you may have Journalists in a News Media domain. And that "Customer" stakeholder name, may indicate a Sales domain. Or may be a stakeholder group, really.
@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 them -
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.
-
@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.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login