#socialcomputing — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #socialcomputing, aggregated by home.social.
-
BESC 2026 is coming to Bangkok,Thailand! The International Conference on Behavioural and Social Computing will be held from 26–28 October 2026. https://besc-conf.org/2026
Submission Deadline: 01 June 2026. Focus on AI, NLP, computational social science, behavioural and psychological sciences. #SocialComputing #AI #NLP #BehaviouralComputing -
BESC 2026 is coming to Bangkok,Thailand! The International Conference on Behavioural and Social Computing will be held from 26–28 October 2026. https://besc-conf.org/2026
Submission Deadline: 01 June 2026. Focus on AI, NLP, computational social science, behavioural and psychological sciences. #SocialComputing #AI #NLP #BehaviouralComputing -
BESC 2026 is coming to Bangkok,Thailand! The International Conference on Behavioural and Social Computing will be held from 26–28 October 2026. https://besc-conf.org/2026
Submission Deadline: 01 June 2026. Focus on AI, NLP, computational social science, behavioural and psychological sciences. #SocialComputing #AI #NLP #BehaviouralComputing -
BESC 2026 is coming to Bangkok,Thailand! The International Conference on Behavioural and Social Computing will be held from 26–28 October 2026. https://besc-conf.org/2026
Submission Deadline: 01 June 2026. Focus on AI, NLP, computational social science, behavioural and psychological sciences. #SocialComputing #AI #NLP #BehaviouralComputing -
We are pleased to announce that the first issue of ACM Transactions on Social Computing (2026) is now released! #ACM #SocialComputing @ACM @sigchi https://dl.acm.org/toc/tsc/2026/9/1
-
We are pleased to announce that the first issue of ACM Transactions on Social Computing (2026) is now released! #ACM #SocialComputing @ACM @sigchi https://dl.acm.org/toc/tsc/2026/9/1
-
We are pleased to announce that the first issue of ACM Transactions on Social Computing (2026) is now released! #ACM #SocialComputing @ACM @sigchi https://dl.acm.org/toc/tsc/2026/9/1
-
We are pleased to announce that the first issue of ACM Transactions on Social Computing (2026) is now released! #ACM #SocialComputing @ACM @sigchi https://dl.acm.org/toc/tsc/2026/9/1
-
Can we have a safer internet without constant censorship? 🔍
Our latest research says yes - but we need better tools. We developed a more precise classifier that tells the difference between someone being offensive and someone actually inciting violence.
We tested it on 3.5M Gab posts and found that AI (with the right prompting) is getting much better at understanding that crucial gray area.
Details for the #TrustAndSafety and #SocialComputing community: https://blog.corifaklaris.com/2026/03/04/developing-a-precise-approach-to-identifying-inciting-speech-online/
-
Can we have a safer internet without constant censorship? 🔍
Our latest research says yes - but we need better tools. We developed a more precise classifier that tells the difference between someone being offensive and someone actually inciting violence.
We tested it on 3.5M Gab posts and found that AI (with the right prompting) is getting much better at understanding that crucial gray area.
Details for the #TrustAndSafety and #SocialComputing community: https://blog.corifaklaris.com/2026/03/04/developing-a-precise-approach-to-identifying-inciting-speech-online/
-
Can we have a safer internet without constant censorship? 🔍
Our latest research says yes - but we need better tools. We developed a more precise classifier that tells the difference between someone being offensive and someone actually inciting violence.
We tested it on 3.5M Gab posts and found that AI (with the right prompting) is getting much better at understanding that crucial gray area.
Details for the #TrustAndSafety and #SocialComputing community: https://blog.corifaklaris.com/2026/03/04/developing-a-precise-approach-to-identifying-inciting-speech-online/
-
Can we have a safer internet without constant censorship? 🔍
Our latest research says yes - but we need better tools. We developed a more precise classifier that tells the difference between someone being offensive and someone actually inciting violence.
We tested it on 3.5M Gab posts and found that AI (with the right prompting) is getting much better at understanding that crucial gray area.
Details for the #TrustAndSafety and #SocialComputing community: https://blog.corifaklaris.com/2026/03/04/developing-a-precise-approach-to-identifying-inciting-speech-online/
-
Fantastic ICSC 2025 in Shanghai! Look forward to ICSC 2026 in Oxford! https://icsc-conf.github.io/2025/ #socialcomputing #FudanUniversity
-
Trust in tech is more than just code. New #CSCW2025 research uncovers how trust is built in Chinese NFT communities. The study finds that traditional Confucian values like "guanxi" (social connections) and "mianzi" (face) are crucial, shaping technological, institutional, and social trust.
This qualitative analysis of WeChat groups and interviews offers vital insights for designing trustworthy decentalized communities.
-
Trust in tech is more than just code. New #CSCW2025 research uncovers how trust is built in Chinese NFT communities. The study finds that traditional Confucian values like "guanxi" (social connections) and "mianzi" (face) are crucial, shaping technological, institutional, and social trust.
This qualitative analysis of WeChat groups and interviews offers vital insights for designing trustworthy decentalized communities.
-
Trust in tech is more than just code. New #CSCW2025 research uncovers how trust is built in Chinese NFT communities. The study finds that traditional Confucian values like "guanxi" (social connections) and "mianzi" (face) are crucial, shaping technological, institutional, and social trust.
This qualitative analysis of WeChat groups and interviews offers vital insights for designing trustworthy decentalized communities.
-
Trust in tech is more than just code. New #CSCW2025 research uncovers how trust is built in Chinese NFT communities. The study finds that traditional Confucian values like "guanxi" (social connections) and "mianzi" (face) are crucial, shaping technological, institutional, and social trust.
This qualitative analysis of WeChat groups and interviews offers vital insights for designing trustworthy decentalized communities.
-
Our paper "EasyHypergraph: an open-source software for fast and memory-saving analysis and learning of higher-order networks" has been published in Humanities and Social Sciences Communications (a Nature Portfolio Journal). In this work, we present EasyHypergraph, a comprehensive, computationally efficient, and storage-saving hypergraph computational library. Any comment is very welcome! https://www.nature.com/articles/s41599-025-05180-5 @nature.portfolio #hypergraph #socialcomputing #nature #research
-
Our paper "EasyHypergraph: an open-source software for fast and memory-saving analysis and learning of higher-order networks" has been published in Humanities and Social Sciences Communications (a Nature Portfolio Journal). In this work, we present EasyHypergraph, a comprehensive, computationally efficient, and storage-saving hypergraph computational library. Any comment is very welcome! https://www.nature.com/articles/s41599-025-05180-5 @nature.portfolio #hypergraph #socialcomputing #nature #research
-
Our paper "EasyHypergraph: an open-source software for fast and memory-saving analysis and learning of higher-order networks" has been published in Humanities and Social Sciences Communications (a Nature Portfolio Journal). In this work, we present EasyHypergraph, a comprehensive, computationally efficient, and storage-saving hypergraph computational library. Any comment is very welcome! https://www.nature.com/articles/s41599-025-05180-5 @nature.portfolio #hypergraph #socialcomputing #nature #research
-
Your submissions and special issue proposals to ACM Transactions on Social Computing are warmly welcomed! Let me know if you have any question. @ACM #ACM #socialcomputing
-
Your submissions and special issue proposals to ACM Transactions on Social Computing are warmly welcomed! Let me know if you have any question. @ACM #ACM #socialcomputing
-
Your submissions and special issue proposals to ACM Transactions on Social Computing are warmly welcomed! Let me know if you have any question. @ACM #ACM #socialcomputing
-
Your submissions and special issue proposals to ACM Transactions on Social Computing are warmly welcomed! Let me know if you have any question. @ACM #ACM #socialcomputing
-
Our next #HCIISeminarSeries guest is David Widder @davidthewid, postdoctoral fellow at Cornell Tech Digital Life Initiative (and
@scsatcmu.bsky.social
alumnus)! Join us.🎙️AI Supply Chains: Tools to Locate Power & Responsibility in AI Production for Critical, Accountable Computing
📅Friday, January 31
🕜1:30-2:30pm
📍NSH 1305+livestream
🔗https://hcii.cmu.edu/news/event/2025/01/hcii-seminar-series-david-widder
#CarnegieMellon #ComputerScience #HumanComputerInteraction #CriticalComputing #SocialComputing #ResponsibleAI
-
Our next #HCIISeminarSeries guest is David Widder @davidthewid, postdoctoral fellow at Cornell Tech Digital Life Initiative (and
@scsatcmu.bsky.social
alumnus)! Join us.🎙️AI Supply Chains: Tools to Locate Power & Responsibility in AI Production for Critical, Accountable Computing
📅Friday, January 31
🕜1:30-2:30pm
📍NSH 1305+livestream
🔗https://hcii.cmu.edu/news/event/2025/01/hcii-seminar-series-david-widder
#CarnegieMellon #ComputerScience #HumanComputerInteraction #CriticalComputing #SocialComputing #ResponsibleAI
-
Our next #HCIISeminarSeries guest is David Widder @davidthewid, postdoctoral fellow at Cornell Tech Digital Life Initiative (and
@scsatcmu.bsky.social
alumnus)! Join us.🎙️AI Supply Chains: Tools to Locate Power & Responsibility in AI Production for Critical, Accountable Computing
📅Friday, January 31
🕜1:30-2:30pm
📍NSH 1305+livestream
🔗https://hcii.cmu.edu/news/event/2025/01/hcii-seminar-series-david-widder
#CarnegieMellon #ComputerScience #HumanComputerInteraction #CriticalComputing #SocialComputing #ResponsibleAI
-
Our next #HCIISeminarSeries guest is David Widder @davidthewid, postdoctoral fellow at Cornell Tech Digital Life Initiative (and
@scsatcmu.bsky.social
alumnus)! Join us.🎙️AI Supply Chains: Tools to Locate Power & Responsibility in AI Production for Critical, Accountable Computing
📅Friday, January 31
🕜1:30-2:30pm
📍NSH 1305+livestream
🔗https://hcii.cmu.edu/news/event/2025/01/hcii-seminar-series-david-widder
#CarnegieMellon #ComputerScience #HumanComputerInteraction #CriticalComputing #SocialComputing #ResponsibleAI
-
Welcome to submit to our Special Issue on "Artificial Intelligence for Social Computing" in Tsinghua Science and Technology (due: May 10, 2025)! https://www.sciopen.com/journal/message_news/get_by_id?id=1877234468479660033&issn=1007-0214 #ai #socialcomputing #socialmedia
-
Welcome to submit to our Special Issue on "Artificial Intelligence for Social Computing" in Tsinghua Science and Technology (due: May 10, 2025)! https://www.sciopen.com/journal/message_news/get_by_id?id=1877234468479660033&issn=1007-0214 #ai #socialcomputing #socialmedia
-
Welcome to submit to our Special Issue on "Artificial Intelligence for Social Computing" in Tsinghua Science and Technology (due: May 10, 2025)! https://www.sciopen.com/journal/message_news/get_by_id?id=1877234468479660033&issn=1007-0214 #ai #socialcomputing #socialmedia
-
This Friday, our next #HCIISeminarSeries guest will be Amy Bruckman, Regents’ Professor, School of Interactive Computing at Georgia Institute of Technology. Join us!
🎙️ "The Crisis in 'Knowledge': What HCI Practitioners Need to Know, and What We Can Do"
📅 Friday, March 1
🕜 1:30pm
📍 NSH 1305 + livestream
🔗 Details: https://buff.ly/3uQEO86
-
This Friday, our next #HCIISeminarSeries guest will be Amy Bruckman, Regents’ Professor, School of Interactive Computing at Georgia Institute of Technology. Join us!
🎙️ "The Crisis in 'Knowledge': What HCI Practitioners Need to Know, and What We Can Do"
📅 Friday, March 1
🕜 1:30pm
📍 NSH 1305 + livestream
🔗 Details: https://buff.ly/3uQEO86
-
This Friday, our next #HCIISeminarSeries guest will be Amy Bruckman, Regents’ Professor, School of Interactive Computing at Georgia Institute of Technology. Join us!
🎙️ "The Crisis in 'Knowledge': What HCI Practitioners Need to Know, and What We Can Do"
📅 Friday, March 1
🕜 1:30pm
📍 NSH 1305 + livestream
🔗 Details: https://buff.ly/3uQEO86
-
This Friday, our next #HCIISeminarSeries guest will be Amy Bruckman, Regents’ Professor, School of Interactive Computing at Georgia Institute of Technology. Join us!
🎙️ "The Crisis in 'Knowledge': What HCI Practitioners Need to Know, and What We Can Do"
📅 Friday, March 1
🕜 1:30pm
📍 NSH 1305 + livestream
🔗 Details: https://buff.ly/3uQEO86
-
📣 Calling all #academics #scientists and #researchers of Mastodon. 👩🔬
Following on from my previous thread a few months back now (https://mastodonapp.uk/@jrashf/110205174439235868), why should social scientists and the wider research community be interested in Mastodon?
I'm thinking of putting together a research proposal and I would really appreciate your ideas.
Please consider boosting! :ivory_boost:
#socialmedia #research #mastodon #fediverse #socialcomputing #socialnetwork #study
-
📣 Calling all #academics #scientists and #researchers of Mastodon. 👩🔬
Following on from my previous thread a few months back now (https://mastodonapp.uk/@jrashf/110205174439235868), why should social scientists and the wider research community be interested in Mastodon?
I'm thinking of putting together a research proposal and I would really appreciate your ideas.
Please consider boosting! :ivory_boost:
#socialmedia #research #mastodon #fediverse #socialcomputing #socialnetwork #study
-
A while back, Cory Doctorow had an article that made the rounds called “Tiktok’s Enshittification“, and then a follow-up called “Gig apps trap reverse centaurs in wage-stealing Skinner boxes“, both of which are well worth the time to read. I’m fairly certain that’s where the term “enshittification” was coined, and damn if it doesn’t make a lot of sense:
Here is how platforms die: first, they are good to their users; then they abuse their users to make things better for their business customers; finally, they abuse those business customers to claw back all the value for themselves. Then, they die.
I call this enshittification, and it is a seemingly inevitable consequence arising from the combination of the ease of changing how a platform allocates value, combined with the nature of a “two sided market,” where a platform sits between buyers and sellers, holding each hostage to the other, raking off an ever-larger share of the value that passes between them.
Cory Doctorow, “Tiktok’s Enshittification“
He also talks a fair bit about “twiddling,” which is part of that process:
Twiddling is the key to enshittification: rapidly adjusting prices, conditions and offers. As with any shell game, the quickness of the hand deceives the eye. Tech monopolists aren’t smarter than the Gilded Age sociopaths who monopolized rail or coal – they use the same tricks as those monsters of history, but they do them faster and with computers:
https://doctorow.medium.com/twiddler-1b5c9690cce6
[…]
Platforms don’t just hate it when end-users twiddle back – if anything they are even more aggressive when their business-users dare to twiddle. Take Para, an app that Doordash drivers used to get a peek at the wages offered for jobs before they accepted them – something that Doordash hid from its workers. Doordash ruthlessly attacked Para, saying that by letting drivers know how much they’d earn before they did the work, Para was violating the law.
Cory Doctorow, “Gig apps trap reverse centaurs in wage-stealing Skinner boxes“
There’s a third recent article that I feel is part of this same thread, “Let the Platforms Burn“, which likens the online ecosystem to a forest ecology: if you let systems entrench themselves and prevent competition, it’s like not allowing small fires to clear the underbrush, and when a fire does eventually happen, it’s so much worse than it would be otherwise.
But HP is still in business. Apple is still in business. Google is still in business. Microsoft is still in business. IBM is still in business. Facebook is still in business.
We don’t have those controlled burns anymore. Yesterday’s giants tower over all, forming a thick canopy. The internet is “five giant websites, each filled with screenshots of the other four.”
[…]
Companies cannot unilaterally mediate the lives of hundreds of millions — or even billions — of people, speaking thousands of languages, living in hundreds of countries.
The problem with, say, Meta, is only partially that Mark Zuckerberg is personally monumentally unsuited to serving as the unelected, unaccountable permanent social media czar for three billion people.
The real problem is that no one should have that job. That job shouldn’t exist. We don’t need to find a better Mark Zuckerberg.
We need to abolish Mark Zuckerberg.
Cory Doctorow, “Let the Platforms Burn“
And then later (I suppose it’s worth noting: these are all long reads):
The platforms aren’t merely combustible, they’re always on fire. Once you trap hundreds of millions — or billions — of people inside a walled fortress, where warlords who preside over have unlimited power over their captives, and those captives the are denied any right to liberate themselves, enshittification will surely and inevitably follow.
[…]
Rather than building more fire debt, we should be making it easy for people to relocate away from the danger so we can have that long-overdue, “good fire” to burn away the rotten giants that have blotted out the sun.
Cory Doctorow, “Let the Platforms Burn“
That’s definitely some food for thought. There have been several responses to these various articles, and Mike Masnick over at TechDirt has an article, “Seven Rules For Internet CEOs To Avoid Enshittification” laying out some things tech CEOs could do (going forward) to try and break out of the enshittification cycle (or at least stave it off for a bit). Whether any are willing to actually do those things (or whether their financiers would allow it) is a separate matter. (I’m not going to quote the list here as that’s most of the article, but go read it. Most of it feels like what should be common sense, but who ever said companies had common sense?)
Personally, I’m quietly hoping that in the great social pendulum that swings between diversification and consolidation, we’re starting to swing back towards diversification. I’ve never liked the silos, and if we go back to having a broad range of smaller services, I think that’ll be better, healthier. I don’t think it’ll be a quick or painless process, though: entrenched platforms are going to do their best to claw back control (and not through improving their services so much as through regulatory and legal efforts). Also, a lot of open source tools have been historically neglected (despite being used heavily by corporations), and have always had a usability barrier (a big reason why people moved towards silos in the first place – they’re easy, and actually pay designers to make it easy). But I’m still hoping things aren’t so broken that we can’t get there.
- More
#cory-doctorow #enshittification #social-computing #social-media #technology
https://nadreck.me/2023/07/enshittification-and-what-to-do-about-it/
-
A while back, Cory Doctorow had an article that made the rounds called “Tiktok’s Enshittification“, and then a follow-up called “Gig apps trap reverse centaurs in wage-stealing Skinner boxes“, both of which are well worth the time to read. I’m fairly certain that’s where the term “enshittification” was coined, and damn if it doesn’t make a lot of sense:
Here is how platforms die: first, they are good to their users; then they abuse their users to make things better for their business customers; finally, they abuse those business customers to claw back all the value for themselves. Then, they die.
I call this enshittification, and it is a seemingly inevitable consequence arising from the combination of the ease of changing how a platform allocates value, combined with the nature of a “two sided market,” where a platform sits between buyers and sellers, holding each hostage to the other, raking off an ever-larger share of the value that passes between them.
Cory Doctorow, “Tiktok’s Enshittification“
He also talks a fair bit about “twiddling,” which is part of that process:
Twiddling is the key to enshittification: rapidly adjusting prices, conditions and offers. As with any shell game, the quickness of the hand deceives the eye. Tech monopolists aren’t smarter than the Gilded Age sociopaths who monopolized rail or coal – they use the same tricks as those monsters of history, but they do them faster and with computers:
https://doctorow.medium.com/twiddler-1b5c9690cce6
[…]
Platforms don’t just hate it when end-users twiddle back – if anything they are even more aggressive when their business-users dare to twiddle. Take Para, an app that Doordash drivers used to get a peek at the wages offered for jobs before they accepted them – something that Doordash hid from its workers. Doordash ruthlessly attacked Para, saying that by letting drivers know how much they’d earn before they did the work, Para was violating the law.
Cory Doctorow, “Gig apps trap reverse centaurs in wage-stealing Skinner boxes“
There’s a third recent article that I feel is part of this same thread, “Let the Platforms Burn“, which likens the online ecosystem to a forest ecology: if you let systems entrench themselves and prevent competition, it’s like not allowing small fires to clear the underbrush, and when a fire does eventually happen, it’s so much worse than it would be otherwise.
But HP is still in business. Apple is still in business. Google is still in business. Microsoft is still in business. IBM is still in business. Facebook is still in business.
We don’t have those controlled burns anymore. Yesterday’s giants tower over all, forming a thick canopy. The internet is “five giant websites, each filled with screenshots of the other four.”
[…]
Companies cannot unilaterally mediate the lives of hundreds of millions — or even billions — of people, speaking thousands of languages, living in hundreds of countries.
The problem with, say, Meta, is only partially that Mark Zuckerberg is personally monumentally unsuited to serving as the unelected, unaccountable permanent social media czar for three billion people.
The real problem is that no one should have that job. That job shouldn’t exist. We don’t need to find a better Mark Zuckerberg.
We need to abolish Mark Zuckerberg.
Cory Doctorow, “Let the Platforms Burn“
And then later (I suppose it’s worth noting: these are all long reads):
The platforms aren’t merely combustible, they’re always on fire. Once you trap hundreds of millions — or billions — of people inside a walled fortress, where warlords who preside over have unlimited power over their captives, and those captives the are denied any right to liberate themselves, enshittification will surely and inevitably follow.
[…]
Rather than building more fire debt, we should be making it easy for people to relocate away from the danger so we can have that long-overdue, “good fire” to burn away the rotten giants that have blotted out the sun.
Cory Doctorow, “Let the Platforms Burn“
That’s definitely some food for thought. There have been several responses to these various articles, and Mike Masnick over at TechDirt has an article, “Seven Rules For Internet CEOs To Avoid Enshittification” laying out some things tech CEOs could do (going forward) to try and break out of the enshittification cycle (or at least stave it off for a bit). Whether any are willing to actually do those things (or whether their financiers would allow it) is a separate matter. (I’m not going to quote the list here as that’s most of the article, but go read it. Most of it feels like what should be common sense, but who ever said companies had common sense?)
Personally, I’m quietly hoping that in the great social pendulum that swings between diversification and consolidation, we’re starting to swing back towards diversification. I’ve never liked the silos, and if we go back to having a broad range of smaller services, I think that’ll be better, healthier. I don’t think it’ll be a quick or painless process, though: entrenched platforms are going to do their best to claw back control (and not through improving their services so much as through regulatory and legal efforts). Also, a lot of open source tools have been historically neglected (despite being used heavily by corporations), and have always had a usability barrier (a big reason why people moved towards silos in the first place – they’re easy, and actually pay designers to make it easy). But I’m still hoping things aren’t so broken that we can’t get there.
- More
#cory-doctorow #enshittification #social-computing #social-media #technology
https://nadreck.me/2023/07/enshittification-and-what-to-do-about-it/
-
The past few days I've been thinking a lot again about one of the thought/design models most influential on my own #OpenSource practice: Frank Duffy's architectural pace layers (and Stewart Brand's subsequent extension to different contexts), their different timescales and interactions as basis for resilient system design:
1. Each layer exists & operates independently, moves at different timescales (from seconds to millennia and beyond)
2. Each layer influences and only interacts with its direct neighbors"Fast layers innovate, slow ones stabilize." — S.Brand
I always found that model super helpful for analyzing and deciding how to deal with individual projects and components in terms of focus/effort, and asking myself which layer this thing might/should be part of. Lately though, I keep on trying to figure out how to better utilize that model to orient my own future practice, also with respect to the loose theme of #PermaComputing and how to frame and better organize my own approaches to it, incl. how to reanimate or repurpose some of the related, discontinued, but not invalid research & projects I've been doing along these lines over the past 15 years...
I understand and appreciate most of the focus on #FrugalComputing & #RetroComputing-derived simplicity as starting points and grounding concepts for attempting to build a more sustainable, personal, comprehensible and maintainable tech, but these too can quickly become overly dogmatic and maybe too constraining to ever become "truly" permanent (at least on the horizon of a few decades). I think the biggest hurdles to overcome are social rather than technological (e.g. a need for post-consumerist, post-spectacular behaviors), so I'm even more interested in Illich/Papert/Nelson/Felsenstein-inspired #ConvivialComputing, #SocialComputing, IO/comms/p2p, #Accessibility, UI, protocol and other resiliency design aspects becoming a core part of that research and think the idea of pace layering can be a very powerful tool to take into consideration here too, at the very least for guiding (and questioning) how to approach and structure any perma-computing related research itself...
Given the current physical and political climate shifts, is it better to continue working "upwards" (aka #BottomUpDesign), i.e. primarily focusing on first defining slow moving, low-level layers as new/alternative foundations (an example here would be the flurry of VM projects, incl. my own)? Or, is it more fruitful and does the situation instead call for a more urgent focus on fast-moving pace layer experiments and continuously accumulating learnings as fallout/sediment to allow the formation of increasingly more stable, but also more holistically informed, slower moving structural layers to build upon further?
It's a bit of chicken vs. egg! In my mind, right now the best approach seems to be a two-pronged one, alternating from both sides, each time informing upcoming work/experiments on the opposite end (fast/slow) and each time involving an as diverse as possible set of non-techbro minds from various fields... 🤔
-
The past few days I've been thinking a lot again about one of the thought/design models most influential on my own #OpenSource practice: Frank Duffy's architectural pace layers (and Stewart Brand's subsequent extension to different contexts), their different timescales and interactions as basis for resilient system design:
1. Each layer exists & operates independently, moves at different timescales (from seconds to millennia and beyond)
2. Each layer influences and only interacts with its direct neighbors"Fast layers innovate, slow ones stabilize." — S.Brand
I always found that model super helpful for analyzing and deciding how to deal with individual projects and components in terms of focus/effort, and asking myself which layer this thing might/should be part of. Lately though, I keep on trying to figure out how to better utilize that model to orient my own future practice, also with respect to the loose theme of #PermaComputing and how to frame and better organize my own approaches to it, incl. how to reanimate or repurpose some of the related, discontinued, but not invalid research & projects I've been doing along these lines over the past 15 years...
I understand and appreciate most of the focus on #FrugalComputing & #RetroComputing-derived simplicity as starting points and grounding concepts for attempting to build a more sustainable, personal, comprehensible and maintainable tech, but these too can quickly become overly dogmatic and maybe too constraining to ever become "truly" permanent (at least on the horizon of a few decades). I think the biggest hurdles to overcome are social rather than technological (e.g. a need for post-consumerist, post-spectacular behaviors), so I'm even more interested in Illich/Papert/Nelson/Felsenstein-inspired #ConvivialComputing, #SocialComputing, IO/comms/p2p, #Accessibility, UI, protocol and other resiliency design aspects becoming a core part of that research and think the idea of pace layering can be a very powerful tool to take into consideration here too, at the very least for guiding (and questioning) how to approach and structure any perma-computing related research itself...
Given the current physical and political climate shifts, is it better to continue working "upwards" (aka #BottomUpDesign), i.e. primarily focusing on first defining slow moving, low-level layers as new/alternative foundations (an example here would be the flurry of VM projects, incl. my own)? Or, is it more fruitful and does the situation instead call for a more urgent focus on fast-moving pace layer experiments and continuously accumulating learnings as fallout/sediment to allow the formation of increasingly more stable, but also more holistically informed, slower moving structural layers to build upon further?
It's a bit of chicken vs. egg! In my mind, right now the best approach seems to be a two-pronged one, alternating from both sides, each time informing upcoming work/experiments on the opposite end (fast/slow) and each time involving an as diverse as possible set of non-techbro minds from various fields... 🤔
-
The past few days I've been thinking a lot again about one of the thought/design models most influential on my own #OpenSource practice: Frank Duffy's architectural pace layers (and Stewart Brand's subsequent extension to different contexts), their different timescales and interactions as basis for resilient system design:
1. Each layer exists & operates independently, moves at different timescales (from seconds to millennia and beyond)
2. Each layer influences and only interacts with its direct neighbors"Fast layers innovate, slow ones stabilize." — S.Brand
I always found that model super helpful for analyzing and deciding how to deal with individual projects and components in terms of focus/effort, and asking myself which layer this thing might/should be part of. Lately though, I keep on trying to figure out how to better utilize that model to orient my own future practice, also with respect to the loose theme of #PermaComputing and how to frame and better organize my own approaches to it, incl. how to reanimate or repurpose some of the related, discontinued, but not invalid research & projects I've been doing along these lines over the past 15 years...
I understand and appreciate most of the focus on #FrugalComputing & #RetroComputing-derived simplicity as starting points and grounding concepts for attempting to build a more sustainable, personal, comprehensible and maintainable tech, but these too can quickly become overly dogmatic and maybe too constraining to ever become "truly" permanent (at least on the horizon of a few decades). I think the biggest hurdles to overcome are social rather than technological (e.g. a need for post-consumerist, post-spectacular behaviors), so I'm even more interested in Illich/Papert/Nelson/Felsenstein-inspired #ConvivialComputing, #SocialComputing, IO/comms/p2p, #Accessibility, UI, protocol and other resiliency design aspects becoming a core part of that research and think the idea of pace layering can be a very powerful tool to take into consideration here too, at the very least for guiding (and questioning) how to approach and structure any perma-computing related research itself...
Given the current physical and political climate shifts, is it better to continue working "upwards" (aka #BottomUpDesign), i.e. primarily focusing on first defining slow moving, low-level layers as new/alternative foundations (an example here would be the flurry of VM projects, incl. my own)? Or, is it more fruitful and does the situation instead call for a more urgent focus on fast-moving pace layer experiments and continuously accumulating learnings as fallout/sediment to allow the formation of increasingly more stable, but also more holistically informed, slower moving structural layers to build upon further?
It's a bit of chicken vs. egg! In my mind, right now the best approach seems to be a two-pronged one, alternating from both sides, each time informing upcoming work/experiments on the opposite end (fast/slow) and each time involving an as diverse as possible set of non-techbro minds from various fields... 🤔
-
The past few days I've been thinking a lot again about one of the thought/design models most influential on my own #OpenSource practice: Frank Duffy's architectural pace layers (and Stewart Brand's subsequent extension to different contexts), their different timescales and interactions as basis for resilient system design:
1. Each layer exists & operates independently, moves at different timescales (from seconds to millennia and beyond)
2. Each layer influences and only interacts with its direct neighbors"Fast layers innovate, slow ones stabilize." — S.Brand
I always found that model super helpful for analyzing and deciding how to deal with individual projects and components in terms of focus/effort, and asking myself which layer this thing might/should be part of. Lately though, I keep on trying to figure out how to better utilize that model to orient my own future practice, also with respect to the loose theme of #PermaComputing and how to frame and better organize my own approaches to it, incl. how to reanimate or repurpose some of the related, discontinued, but not invalid research & projects I've been doing along these lines over the past 15 years...
I understand and appreciate most of the focus on #FrugalComputing & #RetroComputing-derived simplicity as starting points and grounding concepts for attempting to build a more sustainable, personal, comprehensible and maintainable tech, but these too can quickly become overly dogmatic and maybe too constraining to ever become "truly" permanent (at least on the horizon of a few decades). I think the biggest hurdles to overcome are social rather than technological (e.g. a need for post-consumerist, post-spectacular behaviors), so I'm even more interested in Illich/Papert/Nelson/Felsenstein-inspired #ConvivialComputing, #SocialComputing, IO/comms/p2p, #Accessibility, UI, protocol and other resiliency design aspects becoming a core part of that research and think the idea of pace layering can be a very powerful tool to take into consideration here too, at the very least for guiding (and questioning) how to approach and structure any perma-computing related research itself...
Given the current physical and political climate shifts, is it better to continue working "upwards" (aka #BottomUpDesign), i.e. primarily focusing on first defining slow moving, low-level layers as new/alternative foundations (an example here would be the flurry of VM projects, incl. my own)? Or, is it more fruitful and does the situation instead call for a more urgent focus on fast-moving pace layer experiments and continuously accumulating learnings as fallout/sediment to allow the formation of increasingly more stable, but also more holistically informed, slower moving structural layers to build upon further?
It's a bit of chicken vs. egg! In my mind, right now the best approach seems to be a two-pronged one, alternating from both sides, each time informing upcoming work/experiments on the opposite end (fast/slow) and each time involving an as diverse as possible set of non-techbro minds from various fields... 🤔
-
Personal: I am very happy to announce that I have accepted a tenure-track Assistant Professor position at the University of Groningen. Looking forward to further collaborations, and am glad to continue working within the Information Systems Group at the Bernoulli Institute.
@academicchatter get in touch if you are working on #networkscience, #datascience, #misinformation, #polarization, #privacy, #crowdsourcing #SocialComputing #complexsystems @academicsunite
-
Personal: I am very happy to announce that I have accepted a tenure-track Assistant Professor position at the University of Groningen. Looking forward to further collaborations, and am glad to continue working within the Information Systems Group at the Bernoulli Institute.
@academicchatter get in touch if you are working on #networkscience, #datascience, #misinformation, #polarization, #privacy, #crowdsourcing #SocialComputing #complexsystems @academicsunite
-
Personal: I am very happy to announce that I have accepted a tenure-track Assistant Professor position at the University of Groningen. Looking forward to further collaborations, and am glad to continue working within the Information Systems Group at the Bernoulli Institute.
@academicchatter get in touch if you are working on #networkscience, #datascience, #misinformation, #polarization, #privacy, #crowdsourcing #SocialComputing #complexsystems @academicsunite
-
Personal: I am very happy to announce that I have accepted a tenure-track Assistant Professor position at the University of Groningen. Looking forward to further collaborations, and am glad to continue working within the Information Systems Group at the Bernoulli Institute.
@academicchatter get in touch if you are working on #networkscience, #datascience, #misinformation, #polarization, #privacy, #crowdsourcing #SocialComputing #complexsystems @academicsunite
-
HiveMind: Is there any work on the notion of "algorithmic anger" or something similar?
I define AA (yes, pun intended) as the anger we feel when the algorithmic mediations in our lives (e.g., social media) screw us over (e.g., shadowban, deboost, etc.).
It's revealing how much frustration a broken algorithm can create. It's a testament to how much our lives are governed by black boxed, arbitrary, and broken algorithmic systems.
-
HiveMind: Is there any work on the notion of "algorithmic anger" or something similar?
I define AA (yes, pun intended) as the anger we feel when the algorithmic mediations in our lives (e.g., social media) screw us over (e.g., shadowban, deboost, etc.).
It's revealing how much frustration a broken algorithm can create. It's a testament to how much our lives are governed by black boxed, arbitrary, and broken algorithmic systems.
-
HiveMind: Is there any work on the notion of "algorithmic anger" or something similar?
I define AA (yes, pun intended) as the anger we feel when the algorithmic mediations in our lives (e.g., social media) screw us over (e.g., shadowban, deboost, etc.).
It's revealing how much frustration a broken algorithm can create. It's a testament to how much our lives are governed by black boxed, arbitrary, and broken algorithmic systems.
-
HiveMind: Is there any work on the notion of "algorithmic anger" or something similar?
I define AA (yes, pun intended) as the anger we feel when the algorithmic mediations in our lives (e.g., social media) screw us over (e.g., shadowban, deboost, etc.).
It's revealing how much frustration a broken algorithm can create. It's a testament to how much our lives are governed by black boxed, arbitrary, and broken algorithmic systems.
-
Calling all #academics #scientists and #researchers of Mastodon. In the context of social media and the role of the Fediverse, what areas of research are poorly understood or under-researched? What are consider up-and-coming and novel?
#socialmedia #research #mastodon #fediverse #socialcomputing #socialnetwork #study
-
Calling all #academics #scientists and #researchers of Mastodon. In the context of social media and the role of the Fediverse, what areas of research are poorly understood or under-researched? What are consider up-and-coming and novel?
#socialmedia #research #mastodon #fediverse #socialcomputing #socialnetwork #study
-
#recruiting for internships, PhD students, post-docs, academic positions, or non-academic positions focused on research in #socialcomputing or #computationalsocialscience?
Post your call in https://www.reddit.com/r/CompSocial/ to target our growing community of students, researchers, and practitioners!
-
#recruiting for internships, PhD students, post-docs, academic positions, or non-academic positions focused on research in #socialcomputing or #computationalsocialscience?
Post your call in https://www.reddit.com/r/CompSocial/ to target our growing community of students, researchers, and practitioners!
-
#recruiting for internships, PhD students, post-docs, academic positions, or non-academic positions focused on research in #socialcomputing or #computationalsocialscience?
Post your call in https://www.reddit.com/r/CompSocial/ to target our growing community of students, researchers, and practitioners!
-
#recruiting for internships, PhD students, post-docs, academic positions, or non-academic positions focused on research in #socialcomputing or #computationalsocialscience?
Post your call in https://www.reddit.com/r/CompSocial/ to target our growing community of students, researchers, and practitioners!
-
Thought I'd post an (academic) #introduction. :D I am an Assistant Professor at the University of #Groningen, with current research focus on #largscale #networkanalysis (#networkscience) working within the #InformationSystems Group; I previously worked on #humancomputation (don't like the term), #socialcomputing, #distributedsystems at #tuwien. Interested in socio-tech. issues, including #ethics #privacy, tech #policy
#academicsofmastodon #complexnetworks #complexsystems
@academicchatter -
Thought I'd post an (academic) #introduction. :D I am an Assistant Professor at the University of #Groningen, with current research focus on #largscale #networkanalysis (#networkscience) working within the #InformationSystems Group; I previously worked on #humancomputation (don't like the term), #socialcomputing, #distributedsystems at #tuwien. Interested in socio-tech. issues, including #ethics #privacy, tech #policy
#academicsofmastodon #complexnetworks #complexsystems
@academicchatter -
Thought I'd post an (academic) #introduction. :D I am an Assistant Professor at the University of #Groningen, with current research focus on #largscale #networkanalysis (#networkscience) working within the #InformationSystems Group; I previously worked on #humancomputation (don't like the term), #socialcomputing, #distributedsystems at #tuwien. Interested in socio-tech. issues, including #ethics #privacy, tech #policy
#academicsofmastodon #complexnetworks #complexsystems
@academicchatter