There's a lot of customer culture attitude in Mastodon-the-community, where people treat Gargron and other devs, the instance admins, moderators, etc. like service workers. It's a spoiled, entitled attitude, where "the customer is always right" and it's okay to be abusive or demeaning to people providing a service when they don't give you what you want.
The fediverse isn't a corporate model. When you're rude or demeaning to someone here, you're being abusive to volunteers building a playground
@frankiesaxx I've only been here a week - any particular reason the admins don't summarily boot rude people out of their instances…?
Some do. (Those people often move to another instance, and sometimes start carrying a grudge.)
> the customer is always right
That shit needs to die as soon as possible.
The customer has certain rights, that's for sure: they parted with some fraction of their resources and need compensation and then some.
But "always right"? Hell no.
As a "former-but-present" tech support guy, I assure you that some customers are dumb as fuck, ignorant as fuck, rude as fuck for no real reason, and they intend to stay that way, causing infinite frustration, sometimes for the whole operation. Such nutcases just can't be "always right". They are only right as the still clock is sometimes right.
Building on this: This also extends to people posting their annoyance at lacking features into the anonymous void, or worse: mention the devs.
This is not how it works – going onto GitHub (or in case of apps, whereever they are hosted) filing an issue or upvoting an existing one, and helping out with triaging while you are there, if you have five spare minutes – that's how it is done.
Haha what you mean sceaming my demands into the void in an increasingly abusive way isn't actually the best way to get them noticed? ;)
But seriously I think also people have to learn how to deal better with hearing "no" even when they do use the right channels.
@frankiesaxx Definitely. I'm just annoyed at people choosing passive criticism over participatory criticism. And, yes, I ask all of those I see if they have opened/voted for issues already.
Hehe "what's the ticket number?"
Seriously though it's a huge problem with people just saying stuff and then expecting it to happen. Charitably, maybe most people are just unaware how many people make random requests and demands through a variety of channels, and that it's just not possible to keep track of handling them all that way. Less charitably, I've also dealt with people who think they're too important to use the systems that are set up to handle requests & issues.
@frankiesaxx One of the hardest parts of all this, is that a lot of the people moving to Mastodon et al are non-technical people who felt socially vulnerable on birdsite.
They're helpless to change anything about how Mastodon or any instances work, but feel very invested in the network protecting them from abuse, harrassment, etc.
People in that situation behave a lot like children, because children are legitimately needy and relatively helpless: they seek help by being loud and insistent.
@frankiesaxx It's not really OK to treat service workers like shit either. Not that I think you meant that...
No it is definitely not okay to treat service workers (or *anyone*) badly. Unfortunately it's a thing a lot of people do, especially in the customer - service dynamic. :/
@frankiesaxx Volunteer's building a playground are also accountable for the safety of the children who play there. Unless they want it to be a playground dominated by bullies and pedophiles on the hunt for targets. In which case, cool analogy.
The question is how to handle this. Many in the diaspora* community for example want to stay the way it is; they don't want an Eternal September.
But others are in it to "free the internet". So what do "we" want, and how to achieve it?
"We" are having materially different experiences in all of those spheres, so much so that I am no better off on masto than I am on Twitter.
How do you address the general ignorance about that in a way that prevents the current slide of masto into FOSS Chapo Trap House.
@mep1911 @frankiesaxx Yeah, I know. I didnt say they were easy, I just know where they're likely to be found, namely where you dont want to look. I also know when you tell me you dont want to look at those "cans of worms" its more than likely because *you* ironically want easy answers.
Ask yourself why you're so afraid of the cans of worms that make up "We". Unpack that and you'll find your direction.
I think there's room for everyone. Objectively, not everyone want the same thing out of a platform, and one of the strengths of a federated model is that it allows people to make choices in how their digital space operates.
It's not like a physical space, there's really low cost to letting people have their space to create silos or anarchist thunderdomes if that's they want. The problem comes when some people want to dictate to everyone.
@frankiesaxx agree in principle, but i took your OP to be more about the problem of getting people to join and stay in the federated model (or a p2p model, which i'd prefer) in the first place.
their friends and family are not there, many features they expect and love are not there, maybe they even *want* such a platform to be more more "moderated" and "civil", hence they're complaining.
actually, the silent majority doesn't complain and just leaves.
@frankiesaxx and they don't have a background in foss culture after all, so they don't know how to constructively contribute and communicate properly.
and it seems obviously quite impossible for foss/decentralized projects to compete with facebook on development resources, so it's really difficult.
my hypothesis is a decentralized model will have to offer something really new that everybody wants and the old world can't provide due to some technological reasons.
(like what bitcoin does 🤣 )
@frankiesaxx I dunno, I agree with this mostly, but also a lot of people just don't come from walks of life where github is an obvious thing. Is there a good guide for non-techies to get involved on github?
Also to be the devil's advocate, if developers don't feel priveleged to have a community bring to life the code they are creating despite a minority of those people rudely demanding things than they should do something else (I say that in the most loving way possible).
@frankiesaxx but also, being a jerk to devs isn't ok, and I totally don't support it for all the reasons you said
@Alonealastalovedalongthe It doesn't matter how much perceived privilege someone else has, they're still a human being, and being abused and demeaned and treated like garbage takes an emotional toll. Putting up with rudeness and abuse should not be the price for *anyone* in FOSS projects or communities. I don't actually know why this is such a controversial position to people lol
@frankiesaxx Fair enough, I was more speaking to "why don't the devs make this feature I want ughh" and less "the devs are trash and I hate them for being terrible people"
@Alonealastalovedalongthe Understood : ) -- I think there's a huge difference between "I wish the software would do this thing arggh" and personal attacks and abuse when they don't implement it to the user's spec or implement something as user doesn't like, though. And I think most people (devs and users both) understand the difference. I hope.
@frankiesaxx I do think we are speaking to a tension in open source software though, where devs pursue development on their own terms and users advocate for issues that matter to them. How these two things meet is bound to get messy from time to time. It would be really cool if someone wrote a guide for getting involved in mastodon development in ways that a relatively inexperienced programmer could productively. Maybe it already exists?
@Alonealastalovedalongthe I honestly don't know if there is one.
My specific post was prompted by seeing it in Mastodon (in both Mastodon-part-of-the-fediverse and Mastodon-the-project) but I don't think it's unique to Mastodon, or even FOSS. My comparison was with service workers because it's an attitude I see in wider culture too.
long, a bit philosophical
fediverse meta, devs-users relationships
@vi @frankiesaxx Yes definitely. I think devs tend to think of fediverse problems through a technical lens and a lot of users think of fediverse problems through the lens of broader societal issues. There is an inherent bias to software development inherited by a bias in society towards providing opportunity and encouragement to certain types of people to program. Which isn't to minimize the work any individual has to put in to be a programmer.
fediverse meta, devs-users relationships
@Alonealastalovedalongthe programming for federated social networks is a really messy, human pursuit and is unavoidably steeped in broader issues in our culture and I think sometimes users (incorrectly or not) perceive devs as only seeing the technical side of it. Anyways, I am way out of my depth here, so I will leave it at thattt. Thanks to all the devs who put in hardwork to build and maintain this community though!
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!