Over the past few months I’ve been putting my UX Interviewing hat on and helping @jenniferplusplus’s Letterbook project, by talking to a variety of people doing moderation work, largely in the Fedi space
-
@[email protected] @[email protected] I talk about these problems not because I expect immediate solutions but because I hope that aspiring implementations will use it to find better solutions to the problems we face. I hope that I can laugh with people 1-2 years from now and go "haha yeah mod tools when I first started were in the Stone Age. the network was at a turning point where it needed growth to survive but didn’t have the appropriate resources to accommodate growth"
-
@[email protected] @[email protected] I really love role systems, conditional access, mandatory access controls. It makes me happy that you’re prioritizing permissions. Misskey’s role system is a start and while I am getting major improvements (upstream has taken feedback and is making a bunch more extended permissions) that takes time and still doesn’t fix the underlying problem of "moderator" & "administrator" flags on accounts. Still trying to do it step by step, but you have the benefit of not having a legacy codebase needing major refactoring to support modern features.
-
@[email protected] @[email protected] What i'd really like to see one day is the deprecation of "IsAdministrator" and "IsModerator" flags for misskey. I want things to follow something like Discord or Active Directory (yes, Microsoft Active Directory). Creating policies for users, governing what resources they have access to. Not having a specific flag for "administrator" that gives nearly full control of the instance (or the "root" flag which gives you 100% control. administrators can't create accounts but root can create accounts... it's a mess). Ideally instance software should accommodate a variety of hierarchy. It's sad that discord beats instance software on this front.
-
@[email protected] @[email protected] Sure, discord has the concept of "ADMINISTRATOR" permission which just encapsulates all permissions. But that's not the same because you can make roles with specific permissions like MANAGE_MESSAGES. Here? If I wanted to give someone the ability to suspend users? There is no "SUSPEND_USERS". There is only administrator/moderator. And honestly I forgot which one actually gives you the ability to do that. I personally follow the philosophy of least privilege, if I do not need a permission i do not give it to myself. Same goes for everyone else on the mod team. If someone just needs the ability to suspend a user they shouldn't have access to DEFEDERATION and causing a diplomatic crisis. administrators certainly shouldn't be able to just grab all of our credentials (Yes, anyone with admin role can just grab the key for S3 and other instance configuration. There's nothing stopping them. Something you'd expect "Root" to only have access to but no).
-
@puppygirlhornypost2 @mattly We have an ADR open for discussion about authorization and organizing claims. I need to clean it up, but I could do that sooner than not. Would you be interested in looking it over? Particularly from the perspective of how it reflects the actions that mods and admins need to take?
-
-
@puppygirlhornypost2 @mattly Hooray!
This gives me an excuse to put off trying to cobble together a new federation debugging solution (because docker keeps failing at this)
-
while writeups like this are sort of a byproduct of my process (writing is a way of honing thoughts), I’ve found repeatedly they accomplish two things:
1, illustrating to stakeholders just how bad a particular problem is
2, and this gives me great personal satisfaction, helping a bunch of people who *care* and feel neglected feel like they’ve been heardThis is a form of social work, but it exists nearly everywhere in places that build software
-
One of the reasons I decided to consult instead of go back into a salaried role after my previous employer was shut down is that I’ve found, repeatedly, that management often has *big feels* about anyone with an “engineering” title actually *talking* to practitioners: “Stay in your lane"
Sometimes you need the people asking questions of the practitioners to have a deep understanding of the technical issues involved, because *those matter a lot* in figuring out what’s possible/feasible to build
-
the other reason I chose to pursue consulting is because this sort of social research/discovery work, and the design that follows, very often leads to immense conflicts with engineers who have social capital with other engineers
by challenging their assumptions *and* being able to speak their language, I’ve committed the gravest of sins: prioritizing something not purely technical
*that* is perhaps the biggest source of burnout I’ve had in salaried jobs
-
@mattly Stupid management has those feels. Smart management understands that silos are artificial, sometimes necessary evils, but should not just be accepted as "the way things are done." Cargo cult management is everywhere, though. I'm not saying I'm a great manager but a more philosophical approach beats dogmatism nine times out of ten.
-
I haven’t done anything like this in public / for open source before, mostly because of time & dealing w/ burnout from the salaried job,
but also because I get the sense that many people steering OSS projects aren’t going to welcome the social research/discovery work for the same reasons
There are very few OSS projects that take interface design seriously, and I think this is the main reason you don’t get more designers contributing to those projects
-
@[email protected] it’s also why there’s not widespread adoption.
-
@[email protected] i mean this too, you see people commonly complain about software like discord for not adding X feature. It's corporate software, they provide enough "shiny" features and lean in a bit that people get over it. When someone is making an "alternative" to corporate software, and is hellbent on not listening to community feedback or ways of making the UI/UX more accessible... why pick the one that has drawbacks such as less features, or slow releases instead of the big popular one.
-
@tclark yeah, unfortunately it seems the vast majority of places where software is the product have taken on these cookie-cutter roles because that’s how it’s done or that’s how the big companies do it
and I mean, shipping software is hard enough as it is, why reinvent the management wheel?
(the answer “because the existing management wheel sucks” is not acceptable)
-
@[email protected] and honestly? I think this is a driving factor to why people are going to bluesky. Sure, it's not "decentralized" like here but it has features people want. It works good enough that it's a "why bother" for people when looking at mastodon, akkoma and the variety here. Why use half solutions that feel jank, broken in places when you can have something that feels seamless.
-
@mattly for the record, I really do appreciate how big and valuable a gift it is that you're doing this work
-
@puppygirlhornypost2 when I look at any program on my computer I’ve paid for (and there are lots) it’s because the OSS equivalent is comparatively terrible
in the Geordi no/point format:
Inkscape -> Affinity Designer
Ardour -> Bitwig
Emacs/Vim/VSCode -> Sublime Text
LogSeq -> Obisidianit goes on. Krita gets it right, but I think part of that is no one is more “this has to feel right or I ain’t usin’ it” than visual artists
-
@jenniferplusplus it’s part of what needs to be done if this space is to eventually flourish, and I want to see it flourish, and I’m happy to have found a place I can contribute this type of work where it feels welcome
-
@[email protected] @[email protected] I also appreciate the work you put in. Unlike conversations I've had with FOSS people before (not anyone on fedi thankfully) you actually respected what I had to say, you weren't ready to go "well, isn't $X enough?" you kept it an open conversation without downplaying or diminishing what I was trying to convey. You seem to care a lot about getting it done right and in a way that prioritizes the needs of everyone over the ease of implementation.
