• 0 Posts
  • 43 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle










  • Have you heard of TV tropes? It’s a wiki of … well, tropes in story telling (warning: for some people following a single link to https://tvtropes.org/ means they find themselves half a day later with 32 tabs open and having read up on all kind of story tropes while having forgotten what time is).

    On the one hand it will help you recognize the tropes and figure out how many of them are used in all story telling (yes, even the good ones), but on the other hand it can help appreciate that it’s not the tropes or the broad strokes that make up a story, but how well it’s told.

    There’s a reason there are so many movies/stories/plays that are just re-tellings of some Shakespear play or another: it doesn’t matter that the outcome is known from the start. The journey and how well it’s told is what’s important.

    So basically: “Oh yeah, that guy’s gonna betray me. I wonder how and why exactly!”






  • I don’t know the details of this specific project, but assuming that it’s really like many other projects basically a one-person-show at the moment there’s IMO several possible scenarios:

    1. moderation federation doesn’t get fixed quickly enough, kbin instances get mass-defederated and the project effectively dies (some kbin instances and fans will stick around, but they will be a minority and effectively be little defederated islands)
    2. the main dev finds good co-devs and enough time to on-board them in a sane way despite his lack of time at the moment and they can develop and merge a fix for the defederation issue in time to avoid mass-defederation
    3. #1 happens but someone (apparently mbin, as linked elsewhere) forks the project and takes over as a successor and most kbin instances eventually switch over to mbin.

    All of these scenarios have happened to various projects at various times for various reasons, so it’s really hard to tell which one it is.

    Of course there’s also the chance that despite not having much time and not finding/adding co-devs the main dev finds just enough time to fix this issue and the project continues to limp along. That would basically just postpone the other three options IMO, since this is unlikely to remain the only major issue. Problems tend to happen with software.

    Edit: oh, and I forgot that it can also be a mixture of both of those: a fork exists, but the original project also continues and both just live on next to each other with slightly different goals/communities behind them. That’s not even necessarily a bad thing.




  • What I find interesting that everyone just seems to argue that moderation actions should be federated out when the author claims that that’s already how it “should” be (i.e. that’s already the intent but it’s not working). I never wrote code for either software and haven’t even run my own instance or I’d try to reproduce the issue, because I suspect it isn’t hard to pinpoint the problem if the fundamental code is already there.