• 0 Posts
  • 7 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle
  • There are two tensions here:

    1. Community building
    2. Code production

    Community building can be done without any coding, coding can be done without any community. However, to build a large project you need them both.

    In a large volunteer project like this, not everything can be worked on. You become selective. We are going to major on this thing, or specifically talk about that project to get community engagement and get the thing done. This drives the project, she helps it to stop chasing hairs. Someone has to decide what feature is going in this release to make it ready to be a release candidate.

    That group of people, ultimately making and influencing those decisions, is the CoC.

    Let’s take a for-instance: Sign up boxes.

    For years, Linux sign up allows you to record random data into your profile, office, phone number, etc. These are text, and can be anything. Now, what if there’s a rising need to add a minicom number(minix, used to be used by the deaf to send messages to an organisation, before email). As a hearing person, this is going to be a low priority for me, so I work on something else. I’ve got spare capacity, so if the project leaders are calling for help on this thing, I can go and help.

    This, ultimately, builds a better over-all product, but it’s not something I’d have noticed by myself, because I’m not part of the deaf community.

    In our example with NixOS, asking for someone from the community to be a representative on it is not about code quality, but about the issue of visibility. Is there some need that that section of the community needs? Is there a way that the community can do y thing to make the os as a whole more accessible? I don’t know the answer, because I’m not a member of that community, just as I’m not a member of the deaf community.

    In this case, the merit, the qualification, for being on the CoC is being a member of a section of the community. It brings valuable a viewpoint, and adds a voice at the table that can make a real difference. Most coders know that having a wish list of features at the start can make it infinitely easier to add them, than having to go back an rewrite to make them happen. Having a voice that might need that feature makes a difference

    The debate for CoC is about merit, but merit isn’t just stubbornly focused on a single talent, it can also be about life experience.



  • However, unlike Reddit, there’s alternatives. You might not like the community on @lemmy.world, but you might like the community on @anotherlemmythatmight.exist.

    Because of the federated nature, communities will naturally fracture and focus. Here, a bad faith mod will just kill a community on instance a, and people will move to instance b.

    We’ve already seen things happen like this under the banner of ‘free speech’, where people believe that free speech means free from consequences. If you think that, there are plenty of instances out there. Lemmy.world isn’t one of them.

    This means that you can find your favourite community in places with different server rules. Which means it will be the community - the people, the mods, the knowledge, that grows one, not just the fact the names taken.


  • Why do big companies always mark you as spam, and why is it always Hotmail?

    My experience is that I have to remove myself from spamhouse once every couple of months, because Hotmail decided that my 5 emails to different accounts was spam. TBF, it’s better than silently failing which is annoying as hell.

    The problem with email is the same is always been: antiquated software.

    The email protocol was never designed for an internet with bad actors and bots. It’s from the early hopeful days. We absolutely need a better email system - however, it’s simple use, the fact anyone can run one, it’s simplicity, is what made it so useful.

    The difference with Lemmy(et. al.) Is that the protocol is designed in the modern age, and isn’t required to also keep up with bad actors for legacy reasons. If Meta decide to join and fill it full of bad actors, Lemmy has a choice email never had. Lemmy can choose to add verification, peer-conversation, trust keys.

    It however still has the same basic problem: to be useful for everyone, it has to work with everyone. The discussions and decisions about how that happen are not just technological, but also moral and ideal-based.

    Meta, then, in this context, is the first spam email server. How Lemmy/the community/etc respond will be the challenge.



  • I think it is very much a case of developers building, or expanding apps. It’s easy to forget that many of these apps are in their developments infancy, because so (technically speaking) is the server software.

    There will also, inevitably, be an interplay between app developer and server developer. Work arounds producing accepted items that other apps need to include (for those that remember, think text colour codes on IRC, mostly driven by mIRC (short have history, YMMV, etc etc)

    Mind you, I’m wondering if all this federation will bring people back to IRC…


  • I have to say this is quite a worrying abuse. Both of software, and of privacy.

    It’s being deployed for something it’s not meant for, and being used to remove liberties for it. Of course, much of this will be lost to media circles as in CSA cases, the presumption is guilt in the public’s mind.

    Whatever the truth of the original conviction, the use of this software as a condition of bail should be banned, and abhorrent to anyone who values justice.

    That is not to say the software doesn’t have it’s uses - especially in cases of porn addiction. However, the software is nowhere near good enough to be used in legal cases. It says so itself. It errs, intentionally, on gathering more data, on being more conservative, simply because it’s not good enough to make the judgement on its own.

    That’s before we look at the unintentional consequences of impinging on the freedom of an innocent person (‘Hannah’), and the way in which the software is not ‘intelligent’ enough to make judgements on whether or not it should take a photo of emails. It also led to fear of accessing help (and an inability to access help).

    Use of this software in this way is an abuse.