• 0 Posts
  • 87 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2025

help-circle


  • This comm has in the rules “community to talk about the Fediverse and all it’s related services using ActivityPub”. So posts like this are going to be received poorly here

    If you are for real, I think, in presents for parents it’s not about what exactly you buy. It’s about the caring thought. Maybe the guitar would have made her happy and you had a plan to get it. But the plan fell short. It happens. Instead of getting tunnel-visioned on the plan I propose you to think what else could you get her that would make her happy with the funds you have. And next year, start saving another month earlier. Maybe that plan will pan out


  • Ah, but you see “asshole with a lifetime of poor emotional self regulation” is not “scheming fascist with an agenda”. That’s what I’m arguing with in your take

    And in the scope of the question, which used plural “devs losing their minds”, I think that it would be a vilification to effectively say “they snap because they are fascists”

    There are and will be non-fascist (and IMO also non-asshole) devs who snap. And I think some times it will be because of the feeling of responsibility for something, “either I fix it or it won’t get fixed” situation, lack of social/team/peer safety net, … (in my first comment I tried to rather portray the situation than name all those things because I just can’t name all of them)


  • The question I responded to was rather a general one. And I think that seeing all dev-related dramas as “that guy was just fascist all along” is similar to saying “all X are thieves” - a simplification that is easy to choose because it addresses our emotions regarding what has happened but not necessarily always the best explanation

    That is when they have a meltdown and quit the project because demand for bug fixes or new features it too much pressure.

    That requires self-awareness to ask oneself “maybe I need a break?” and I think such decision can be hard to make due to sunken cost fallacy. I think that with the pressure of the pings about bugs and requests etc, it’s easy to get into mindset of “it’s either on or off” with nothing in between. Because 5 bugs solved means only 3 other to go.
    And the second option is to dig in harder and in this case “curate the feed. All of it. Whatever that means”

    I’m not saying that that person did not act out of an agenda. But I can imagine a set of choices that lead to a catastrophic breaking point


  • I think it’s the pressure and the solo developer model

    You put something out. It seems to be running. There are bugs. You fix them. There are more bugs (pareto is a PITA). You fix them too. Someone accuses you of sacrificing kittens in the basement. There are ideas for features and more bugs. Some worded in an entitled or just tone-deaf way. Very often you’re the only one working on the project and saying “I accept PRs” somehow became received as a FU. It becomes hard to put the project away for just a week
    You are perpetually in “I-fix-it” mode
    Not to mention that in order to even start a project like that one needs to have at least a bit of “fuck it, I’ll do it myself” mentality

    It’s a pity that !unfinishedprojects@forum.unfinishedprojects.net wound down. I hoped it might have been a space for projects to find communities. As we see around, it doesn’t require a 10 person team with a kanban board to write something that works. But on the other side of the spectrum I think a project needs some sort of community around it. So even if there’s only one dev, someone else could write the tutorials, less technical parts of docs, help new deployments etc











  • I have also been wondering about this. But

    admins and mods are selected sortitionally( randomly) from people who apply

    That’s your point of starvation. The application

    I think, instead, everyone on the instance should be a voting member. And the decisions should be taken based on some requirement on the votes

    1. person one flags a post -> that’s a vote
    2. maybe add a header that this post is under review? The voting process should probably be taking some time
    3. another person flags the same post -> that’s a vote
    4. someone else says it should not be flagged -> that’s a vote in opposite direction
    5. ??? <- can be changed by an instance wide vote too
    6. post/comment/user is either moderated or not, depending on votes and logic from the previous vote

    In order to boost participation, randomly ask an active account to cast a vote on an ongoing discussion

    I think there should be some way for “backend admin” to step in and ban something. But they should only do that for spam/csam/scam/etc. Nothing else, no matter how crazy or rude the take is
    (btw, maybe the instance could also normalize asking someone to reword their take if it’s rude or can be interpreted badly out of context?)





  • I understand. But with how downvotes are sometimes, but often IMO, used - a vote on agree/disagree, in a way that feature becomes “I don’t want to see opinions of people that disagree with me”. It does make it exotic
    So the chances that it will be developed and tested is rather low, chances that there will be enough social support for having it is rather low