#socialcomputing

Carnegie Mellon HCI Institutecmuhcii@hci.social
2025-01-29

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

đź”—hcii.cmu.edu/news/event/2025/0

#CarnegieMellon #ComputerScience #HumanComputerInteraction #CriticalComputing #SocialComputing #ResponsibleAI

2025-01-09

Welcome to submit to our Special Issue on "Artificial Intelligence for Social Computing" in Tsinghua Science and Technology (due: May 10, 2025)! sciopen.com/journal/message_ne #ai #socialcomputing #socialmedia

Carnegie Mellon HCI Institutecmuhcii@hci.social
2024-02-29

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: buff.ly/3uQEO86

#cmuhcii #HumanComputerInteraction #SocialComputing

2023-10-19

📣 Calling all #academics #scientists and #researchers of Mastodon. 👩‍🔬

Following on from my previous thread a few months back now (mastodonapp.uk/@jrashf/1102051), 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

2023-07-11

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.

#cory-doctorow #enshittification #social-computing #social-media #technology

https://nadreck.me/2023/07/enshittification-and-what-to-do-about-it/

Karsten Schmidttoxi@mastodon.thi.ng
2023-06-17

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... 🤔

Diagram of a building seen as pace layers (from Stewart Brand's How Buildings Learn and adapted from Duffy's 1990 paper "Measuring building performance"). The layers (from slowest to fastest) are: Site, Structure, Skin, Services, Space Plan, Stuff
Mirela Rivenimirela
2023-06-13

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 , , , , , @academicsunite

Upol Ehsanupol@hci.social
2023-06-03

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.

#academia #academicchatter #socialcomputing #research

AI generated art depicting collective human rage against malfunctioning algorithms
2023-04-15

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

Sanjay Kairamskairam@hci.social
2023-01-06

#recruiting for internships, PhD students, post-docs, academic positions, or non-academic positions focused on research in #socialcomputing or #computationalsocialscience?

Post your call in reddit.com/r/CompSocial/ to target our growing community of students, researchers, and practitioners!

Mirela Rivenimirela
2022-12-30

Thought I'd post an (academic) . :D I am an Assistant Professor at the University of , with current research focus on () working within the Group; I previously worked on (don't like the term), , at . Interested in socio-tech. issues, including , tech

@academicchatter

Sanjay Kairamskairam@hci.social
2022-12-01

We're so close to 100 members over at reddit.com/r/CompSocial/ -- come join the fun!

CompSocial is intended to be a hub for folks across the social computing / computational social science space to share resources, engage in discussions, and learn about what's new in the field.

#socialcomputing #CSCW #computationalsocialscience #hci #CHI #ICWSM

Sanjay Kairamskairam@hci.social
2022-11-23

WAYRT? (What Are You Reading Today)

We're starting a new Wednesday tradition at CompSocial...

Come by and tell us about the papers, blog posts, tutorials, articles, anything that you've been reading lately that might be of interest to the broader #socialcomputing / #onlinecommunities / #computationalsocialscience community.

reddit.com/r/CompSocial/commen

Sanjay Kairamskairam@hci.social
2022-11-20

We're at 42 members and counting over at reddit.com/r/CompSocial/

Please come join us if this feels relevant to you and your work. We're hoping to make this a valuable source of community-contributed content, including paper links and discussions, CFPs, academic/industry job postings, and more.

#HCI #socialcomputing #computationalSocialScience #CSCW2022 #ICWSM #contentmoderation

Sanjay Kairamskairam@hci.social
2022-11-18

For all my #HCI / #SocialComputing / #CompSocSci friends here, I'm excited that we have Mastodon as a space to support this community in the post-Twitter times.

I think Reddit could serve a valuable auxiliary function as a place to host lasting discussions across the community. Join me at reddit.com/r/CompSocial/ and let's co-create a thriving community there!

#CHI #CSCW #ICWSM

2022-11-16

post-migration re-#introduction:

I'm an assistant professor in the School of Information at #umich. I develop computational methods to study conversations, in the vein of #computationalsocialscience #datascience #nlp #nlproc, with #socialcomputing #cscw #emca #hci #linguistics in my peripheral vision.

I have a dog whose yawns, out of context, can be construed as screaming. I maintain a messy mapping of books to cafés at tisjune.github.io/recreation/

Sanjay Kairamskairam@hci.social
2022-11-15

Just had a great time presenting on "Crafting Social Experiences Online" in @asb's "Design of Online Communities" class. The students, as always, had fantastic questions.

If you're teaching a social computing class in the spring and are looking for guest speakers 👋🏽

#HCI #socialcomputing #onlinecommunities

Sanjay Kairamskairam@hci.social
2022-11-14

Is anyone familiar with prior work that explores *who* provides feedback in online communities?

There is some work on identifying "experts" in knowledge-sharing communities, but is there research identifying what kinds of users are doing the social/community work of welcoming and encouraging new participants?

Any pointers at all, even peripherally relevant, would be appreciated!

#HCI #socialcomputing #computationalSocialScience #litreview

Cori Faklaris 👩🏻‍💻Heycori@hci.social
2022-11-12

Been thinking more about how to introduce “design friction” to improve our online interactions. Mastodon has many, such as the lack of a quote-post function, that constrain virality. But, we lose the pro-social effects of virality, such as visibility into a conversation going on outside of our own “filter bubble.”

More on the antivirality of Mastodon: uxdesign.cc/mastodon-is-antivi

#ux #userexperience #HCI #CSCW #socialcomputing #socialmedia #design #News

justinetisjune
2022-11-10

hi folks! Tomorrow 10-11am ET, Michael Nebeling is hosting an office hour for applicants in technical HCI. I'll be participating with @parastoo, @dj, and Amy Pavel. We'll discuss some of the questions that we've been compiling at: docs.google.com/document/d/1UJ

the range of research interests we span (words! sights! sounds! VR!) gives a good indication of our intended scope, so we're hoping the session will be helpful for lots of people interested in doing a PhD!

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst