@HerraBRE@rysiek One of the most important things I've learned about security during last few years is that it consists of not just Confidentiality and Integrity, but also Availability. So a situation where you can't connect to a server, or decrypt a message, is still treated as a security failure. There's often (always?) a tradeoff between Availability and the other two components, but it's not true that security people don't care about Availability.

the Pleroma community ethos is not the same as the ethos of the GNU social instances that Mastodon hates. the Pleroma community ethos is one of finding solutions to problems and keeping out the bullshit, whatever that may be.

yes, it is a different ethos to that of Mastodon, but it is an appropriate ethos considering what we're trying to build -- software anyone is entitled to use and contribute to.

@kaniini@href I know this but I'm in a position of convincing others that this is the case.

The pleroma devs are about the code, quality of code and reasonable features and reasonable prioritization of development.

As a professional programmer I <3 this approach.

It can be a pain in the ass to put forth to non-devs though.

I deployed pleroma *because* you and other are decidedly non-assholes by default and focused on building good code and being reasonable about said code.

Aside from the code the pacmaning of gnusocial instances by pleroma puts the non-programmer ethos in a difficult position. I don't assume you are pro-jackass admin but at the same time your software is taking over those instances.

@mayel I want to hug everyone on SocialCoop because you are so cool and I kinda want to help but I'm pretty happy with my instance and I'm not sure I can take more responsibilities beyond Tusky and I'm terrible sysadmin so I can only wish you all good luck!