Salta al contenuto
Citiverse è uno spazio aperto a tutte le comunità. Se vuoi aprire un gruppo locale o una sezione per la tua organizzazione, puoi contattare gli amministratori: pagina dei contatti.

Enabling Sensitive Conversations with Consent Boundaries: Moa, a Platform for Discussing PhD Advising Relationships [as a testcase] | Proceedings of the ACM on Human-Computer Interaction

Fediverse
3 2 0
  • scritto ultima modifica di supersquirrel@lemmy.ca
    #1

    I think this is a really interesting example of how the Fediverse has so much potential that goes far beyond the visions of social media that Corporations and rightwing extremist billionaires could ever provide us.

    Yes a great use of a social media platform, if structured well and locally moderated by human beings, could absolutely be useful for certain cases like this in a way that would be superbly difficult to arrange otherwise.

    Individuals who suffer from problematic power dynamics, such as mistreatment or abuse from someone in power, can benefit from identifying allies, whether it is to seek advice or remedial action. Here, we use the word “ally” to refer to any individual who is sympathetic and can offer some kind of help, ranging from sharing useful information to actively navigating the situation together. Example contexts include workplace bullying [91], political persecution [57], and sexual harassment [23]. In contexts where potential allies are initially unknown, however, someone must make at least a partial disclosure of their experience for what we call ally discovery1 to succeed. But, disclosure is risky because the exact conditions under which these situations arise heighten concerns of exposure and retaliation [3, 21]. That is, one cannot know whom to trust about an issue until one discloses being affected by it; yet one cannot disclose before knowing whom to trust.

    Some of the most helpful information in navigating problematic power dynamics can come from individuals who share similar traits regarding the context, e.g., women working with the same manager. How can we facilitate the flow of information in such situations, so that individuals who need it most can discover allies while maintaining one’s anonymity? We consider this problem in the context of PhD students experiencing advising challenges. Because the advising relationship is fraught with power dynamics and ripe for exploitation [14, 47, 54, 80], ally discovery is critical for enabling students to connect with peers who might offer advice or partnership toward remedial action. Yet, research shows that ally discovery within the same PhD program can be difficult [24, 27].

    ...

    Social media platforms are typically structured around a predefined network (e.g., followers) or space (e.g., group) [92]. In contrast, Moa focuses on the question: “How does each user want to design their audience per post or comment?” As a result, Moa does not implement any network model nor does it include user profile pages (REQ3).4 Furthermore, instead of letting users have access to the same content if they are in the same space, Moa’s users see different sets of posts (and comments) depending on their own and others’ consent boundaries (Section 4.2). In terms of the Form-From matrix [92], we believe Moa is closest to a Threaded Space, but consent boundaries considerably weaken both the threading and the space.

    ...

    Taking a consent-centered approach was essential to developing Moa. While consent and privacy are closely related, there is a subtle difference in emphasis. Speaking strictly from an engineering standpoint, consent boundaries are like privacy settings—they give different permissions to different sets of users. But, they differ from traditional privacy settings with respect to the categories of user-sets that can be formed, the granularity of control, and most importantly, the way the categories align with users’ own preferences for control. Below, we reflect further on how consent differs from privacy, and what consent means for system development.

    To begin, privacy is a fuzzy concept—scholars disagree on how exactly to define it, though definitions cluster around themes such as the right to be left alone, restriction of access, secrecy, control over personal information, personhood, and intimacy [77]. One relevant ambiguity in the context of computing is about who provides privacy: Privacy can be conferred to a user by the user themselves, or by a privacy-protecting system.

    In contrast, the essence of consent is that it is strictly user-determined. The only entity who can grant an individual’s consent is the individual herself; there is no definition of “consent” in which a system can grant itself consent to do something to a user that the user does not herself wish to allow.
    Thus, relying on the term “privacy” can obscure the central role of the user, as privacy encompasses multiple, often ambiguous meanings. Arguably, the reason why "user-centered privacy" is a term distinct from general privacy is because the user-centeredness of privacy is not a given. Yet, even within the usable privacy and security community, discussions of consent have been limited to the notice-and-choice paradigm [13]. Consent is not cast as a foundational principle for system design.

    Based on this view, systems frequently define privacy options in advance (i.e., the system is conferring some privacy), with users only able to accept or decline them. In practice, these options are often difficult to find or understand, further limiting true user consent. For instance, many of Facebook’s privacy settings are often hidden [30].

    As the feminist affirmative consent framework recommends [35],14 consent should not merely be a mechanism for relaxing privacy constraints, but a foundational principle of design: individuals affected by an action should have the agency to define exactly what their consent boundary is, in the way that they conceive as relevant to a particular context.

    ...

    Currently, Moa is maintained by the lead author in order to minimize privacy risks. Running the platform with 47 users turned out to be feasible—the lead author was diligent in moderating and seeking user feedback, and no incidents of abuse or negative feedback occurred. However, how could Moa and the concept of consent boundaries scale?

    One way to scale is having multiple instances of Moa, one per organization or group, each with its own administrator, similar to Mastodon. This approach reflects an important assumption that local system admins are important for earning users’ trust, which was confirmed by our Phase 3 study. And, just as research shows that Reddit’s moderators have their own network of giving each other support [9], we imagine that there should be a support network for Moa’s administrators and moderators. This would ensure that each instance is not entirely isolated, and that when sensitive incidents happen, there would be cross-instance resources on how to resolve them.

    It is possible to imagine building Moa as a larger, monolithic platform such as Facebook or Reddit, but we imagine even on such a platform, communities would have their own moderators—each trusted by their respective communities—who are empowered to provide the kind of meaningful oversight over identity that the Moa prototype included. For this study, it was easy for users to verify and understand that the moderator was also a PhD student in the same institution. At larger scale, there would need to be a process for selecting such moderators, and proving their identity to other members of the community.

    In terms of consent boundaries, they are likely to be applicable to other contexts beyond PhD advising, such as among workplace employees [18, 67], survivors of sexual misbehavior by one group of people [16, 48], or potential whistleblowers at the same organization [19].

    One aspect of the Moa prototype described in this paper was that there was an implicit consent boundary formed by the community of PhD students from the same institution—no user needed to consider whether their content would be revealed to non-students. Communities could be formed much like Slack’s channels around different topics, though additional mechanisms such as member-sponsored invitations to join or formal background checks would be required to ensure that community members satisfy membership requirements.

    We also imagine consent boundaries could be used in general platforms such as Facebook or Reddit, likely in less sensitive contexts. Consent boundaries could help users carve out a group of people they want to interact with, without having to designate a particular space or network [92].
    6

  • I think this is a really interesting example of how the Fediverse has so much potential that goes far beyond the visions of social media that Corporations and rightwing extremist billionaires could ever provide us.

    Yes a great use of a social media platform, if structured well and locally moderated by human beings, could absolutely be useful for certain cases like this in a way that would be superbly difficult to arrange otherwise.

    Individuals who suffer from problematic power dynamics, such as mistreatment or abuse from someone in power, can benefit from identifying allies, whether it is to seek advice or remedial action. Here, we use the word “ally” to refer to any individual who is sympathetic and can offer some kind of help, ranging from sharing useful information to actively navigating the situation together. Example contexts include workplace bullying [91], political persecution [57], and sexual harassment [23]. In contexts where potential allies are initially unknown, however, someone must make at least a partial disclosure of their experience for what we call ally discovery1 to succeed. But, disclosure is risky because the exact conditions under which these situations arise heighten concerns of exposure and retaliation [3, 21]. That is, one cannot know whom to trust about an issue until one discloses being affected by it; yet one cannot disclose before knowing whom to trust.

    Some of the most helpful information in navigating problematic power dynamics can come from individuals who share similar traits regarding the context, e.g., women working with the same manager. How can we facilitate the flow of information in such situations, so that individuals who need it most can discover allies while maintaining one’s anonymity? We consider this problem in the context of PhD students experiencing advising challenges. Because the advising relationship is fraught with power dynamics and ripe for exploitation [14, 47, 54, 80], ally discovery is critical for enabling students to connect with peers who might offer advice or partnership toward remedial action. Yet, research shows that ally discovery within the same PhD program can be difficult [24, 27].

    ...

    Social media platforms are typically structured around a predefined network (e.g., followers) or space (e.g., group) [92]. In contrast, Moa focuses on the question: “How does each user want to design their audience per post or comment?” As a result, Moa does not implement any network model nor does it include user profile pages (REQ3).4 Furthermore, instead of letting users have access to the same content if they are in the same space, Moa’s users see different sets of posts (and comments) depending on their own and others’ consent boundaries (Section 4.2). In terms of the Form-From matrix [92], we believe Moa is closest to a Threaded Space, but consent boundaries considerably weaken both the threading and the space.

    ...

    Taking a consent-centered approach was essential to developing Moa. While consent and privacy are closely related, there is a subtle difference in emphasis. Speaking strictly from an engineering standpoint, consent boundaries are like privacy settings—they give different permissions to different sets of users. But, they differ from traditional privacy settings with respect to the categories of user-sets that can be formed, the granularity of control, and most importantly, the way the categories align with users’ own preferences for control. Below, we reflect further on how consent differs from privacy, and what consent means for system development.

    To begin, privacy is a fuzzy concept—scholars disagree on how exactly to define it, though definitions cluster around themes such as the right to be left alone, restriction of access, secrecy, control over personal information, personhood, and intimacy [77]. One relevant ambiguity in the context of computing is about who provides privacy: Privacy can be conferred to a user by the user themselves, or by a privacy-protecting system.

    In contrast, the essence of consent is that it is strictly user-determined. The only entity who can grant an individual’s consent is the individual herself; there is no definition of “consent” in which a system can grant itself consent to do something to a user that the user does not herself wish to allow.
    Thus, relying on the term “privacy” can obscure the central role of the user, as privacy encompasses multiple, often ambiguous meanings. Arguably, the reason why "user-centered privacy" is a term distinct from general privacy is because the user-centeredness of privacy is not a given. Yet, even within the usable privacy and security community, discussions of consent have been limited to the notice-and-choice paradigm [13]. Consent is not cast as a foundational principle for system design.

    Based on this view, systems frequently define privacy options in advance (i.e., the system is conferring some privacy), with users only able to accept or decline them. In practice, these options are often difficult to find or understand, further limiting true user consent. For instance, many of Facebook’s privacy settings are often hidden [30].

    As the feminist affirmative consent framework recommends [35],14 consent should not merely be a mechanism for relaxing privacy constraints, but a foundational principle of design: individuals affected by an action should have the agency to define exactly what their consent boundary is, in the way that they conceive as relevant to a particular context.

    ...

    Currently, Moa is maintained by the lead author in order to minimize privacy risks. Running the platform with 47 users turned out to be feasible—the lead author was diligent in moderating and seeking user feedback, and no incidents of abuse or negative feedback occurred. However, how could Moa and the concept of consent boundaries scale?

    One way to scale is having multiple instances of Moa, one per organization or group, each with its own administrator, similar to Mastodon. This approach reflects an important assumption that local system admins are important for earning users’ trust, which was confirmed by our Phase 3 study. And, just as research shows that Reddit’s moderators have their own network of giving each other support [9], we imagine that there should be a support network for Moa’s administrators and moderators. This would ensure that each instance is not entirely isolated, and that when sensitive incidents happen, there would be cross-instance resources on how to resolve them.

    It is possible to imagine building Moa as a larger, monolithic platform such as Facebook or Reddit, but we imagine even on such a platform, communities would have their own moderators—each trusted by their respective communities—who are empowered to provide the kind of meaningful oversight over identity that the Moa prototype included. For this study, it was easy for users to verify and understand that the moderator was also a PhD student in the same institution. At larger scale, there would need to be a process for selecting such moderators, and proving their identity to other members of the community.

    In terms of consent boundaries, they are likely to be applicable to other contexts beyond PhD advising, such as among workplace employees [18, 67], survivors of sexual misbehavior by one group of people [16, 48], or potential whistleblowers at the same organization [19].

    One aspect of the Moa prototype described in this paper was that there was an implicit consent boundary formed by the community of PhD students from the same institution—no user needed to consider whether their content would be revealed to non-students. Communities could be formed much like Slack’s channels around different topics, though additional mechanisms such as member-sponsored invitations to join or formal background checks would be required to ensure that community members satisfy membership requirements.

    We also imagine consent boundaries could be used in general platforms such as Facebook or Reddit, likely in less sensitive contexts. Consent boundaries could help users carve out a group of people they want to interact with, without having to designate a particular space or network [92].
    6

    scritto ultima modifica di
    #2

    Too long and seemingly structurally disconnect, so mind started to slip, but from the points I was able to catch, sounds like those anonymous boards of old I hear about. Iirc there has been an implementation of that in the fediverse already, though it's been some months so can't remember the name.

  • scritto ultima modifica di supersquirrel@lemmy.ca
    #3

    Ok I should clarify in quotes at the top that this platform fundamentally requires a trusted entity to confirm the identity of users and crucially everyone has to genuinely trust in that process. This tool is a great facilitator once you get there but it is important to emphasize that the designers created this tool for the step after that.

    The implications for the Fediverse (though you could run this software on ActivityPub but on an isolated but still federated network right?) are as a tool to use within a larger social network structure to connect people in new generative ways that are difficult to get going otherwise.

  • The Button game returns: Season 5 is Live on the Fediverse

    Fediverse fediverse
    2
    2 Votazioni
    2 Post
    22 Visualizzazioni
    davel@lemmy.mlD
    Aping Redditisms isn’t really my bag, but you kids have fun. This reminds me though of Cards Against Humanity’s Holiday Hole project a decade ago, which coincided with Trump’s first election victory.
  • 17 Votazioni
    15 Post
    35 Visualizzazioni
    snoopy@piefed.socialS
    Well, both side were wrong. However, we were accusated of : being nazi, bullshit ! being zionist, bullshit ! being transphobe, bullshit ! being centrist, bullshit ! being anti-anarchist, bullshit ! using social credit, bullshit ! shadowbanning, bullshit ! You may want start this story with dbzer0 supporting "murder all zionists" and check that mod that banned lot people for zionism... Some people that still accuse us about this and that...they completly missed my point with my message on yptb. Yes, i deleted some post, some comment were deleted by our staff. You are on piefed.social, so there is some bias...so, yes it is more neutral here. But i consider this serie of posts are the first step for moving on and let Rimu share his own point of view.
  • 2 Votazioni
    102 Post
    87 Visualizzazioni
    openstars@piefed.socialO
    It's been a couple weeks and I wanted to add another perspective about this. I noticed a user downvoting posts, https://lemvotes.org/user/FarStare@lemmy.dbzer0.com if it helps to have specifics. In the more than one full year of existing, they have never once contributed via making a post, never once commenting even, just doling out up- and down-votes in roughly equal proportion, and even those nearly exclusively via posts but almost never comments. I am not concerned about receiving votes from PugJesus - either up or down, as PugJesus has earned the right to speak on behalf of the community. But who is this other person who is influencing how others see my content? Are they male or female? Do they have a degree of some kind? Do they primarily visit meme communities, as the vote pattern might suggest, or other communities as well? So how do I feel about people who use the Threadiverse more than others? My answer is more complex and nuanced than simply yay or nay. I might prefer the opposite of the implemented feature even - the more someone posts (including comments?), the more upvotes they are allowed to make? Have they not earned such? Also, if votes were exposed, each individual could decide for themselves how they wanted to make use of voting - perhaps someone would ban PugJesus, or conversely write special code (a 3rd party app / API recipient?) to highlight posts that PugJesus upvoted (isn't that how "boosting" works? at least re-tweeting does). It's really difficult to guess what someone wants, as each person wants different things. Which is why ultimately in an effort to make things more fair & equitable, the solution can end up making it less so. I like the follow-up suggestion to leave this new option OFF by default, so that an instance admin would have to specifically opt-in, perhaps as part of an overall suite of features limiting things like posts and comments as well. Although really, I think other approaches might work better - e.g. why would someone want to limit themselves to "some" of PugJesus' content, wouldn't they rather simply have it all or else ban him from the instance and therefore have none? I am not seeing the benefit realistically of having "some", especially when the delimiter is not based on community or overall content but simply what time of day (based on an arbitrary threshold for when they starts and ends to restart the next period) the votes are cast?
  • My latest FOSS Academic post is a doozy.

    General Discussion mastodon fediverse canada
    2
    1 Votazioni
    2 Post
    37 Visualizzazioni
    julian@activitypub.spaceJ
    @rwg@aoir.social usually there's a carve out for smaller instances. If this affects all social networks regardless of size, this makes my business as a purveyor of hosted forums essentially untenable. Watching closely.
  • 0 Votazioni
    2 Post
    36 Visualizzazioni
    aral@mastodon.ar.alA
    @df @aslakr Nice
  • 0 Votazioni
    1 Post
    26 Visualizzazioni
    Nessuno ha risposto
  • 1 Votazioni
    1 Post
    14 Visualizzazioni
    Nessuno ha risposto
  • 0 Votazioni
    1 Post
    28 Visualizzazioni
    Nessuno ha risposto

Citiverse è un progetto che si basa su NodeBB ed è federato! | Categorie federate | Chat | 📱 Installa web app o APK | 🧡 Donazioni | Privacy Policy

Il server utilizzato è quello di Webdock, in Danimarca. Se volete provarlo potete ottenere il 20% di sconto con questo link e noi riceveremo un aiuto sotto forma di credito da usare proprio per mantenere Citiverse.