@realcaseyrollins@alex > The Pleroma and Akkoma devs have been intentionally hostile to Alex Gleason
Either you've not been paying attention or you love sucking Alex Gleason's dick. Knowing the typical behavior of Gleason defenders, I'm betting on the latter.
@realcaseyrollins@alex Let me be honest with you. If you're struggling to stop talking and crying about your idol getting proper consequences for his own piss-poor conduct on a FOSS project, especially when it's close to a year since the incident occurred, log off.
Go outside and touch grass.
Find something better to do in life than continue to waste me and others' mental health energy.
@ilja@helene Literally sold on doing this. I experimented with doing that for my Fuck Gab! project. And it actually is pretty promising as a technology.
Ecto during unit testing: Heheh PSQL connection go brrr
Embed this noticeSean King (seanking@freespeechextremist.com)'s status on Thursday, 28-Jul-2022 07:52:09 JST
Sean KingI feel like in order to get Pleroma to a better place, we are going to have to: 1. Challenge the existing fediverse status quo. 2. Put community guidelines, maintainer guidelines, etc, in place so as to achieve a balance of power over the project. 3. Emphasize working together over picking fights, insults, etc. 4. Emphasize quality of new features over quantity of new features.
This is the only way we'll be able to gain confidence in potential funders and maybe those who currently fork from us.
@hj@Zerglingman@alex@virilemame Agreed. Like I think there is some potential in some of his ideas despite the questionable quality of the work. But his behavior and attitude, especially when it comes to controversial matters and MRs he opens, is extremely difficult to deal with.
@graf@Zerglingman@alex@hj@virilemame Seems like you've literally only seen the MRs related to the "notice compatibility routes" BS. I've been working on other things such as adding editing to the frontend of Pleroma for example. Saying I'm a "child" and a "f*ggot" is just disingenuous and says a lot more about you, Graf.
If that is all you have, please just leave me. Block me. I'm more than happy to work together with you guys on the Soapbox side. But this is not gonna work if you're gonna hurl insults at me and others just because we happen to not always agree with Alex.
@realcaseyrollins Dude, Gleason literally started by merging that notice compatibility routes MR despite that Pleroma's community found it controversial. This could've all been prevented if Gleason didn't abuse his power as a maintainer. He's also the reason that we're working on a community guidelines, too. And frankly, just leave me and block me if you're so angry about some dumb URL schemes that literally nobody gives a crap about, ok? Or you could just reply and I'll do the rest of the work.
Literally, all you have to do if you want notice compatibility routes in Pleroma (like there is Soapbox) is uncomment a few lines in an Nginx configuration that I put in there with the help of the awesome @ilja and @tusooa. It's not that hard.