• 7 Posts
  • 38 Comments
Joined 1 year ago
cake
Cake day: February 16th, 2024

help-circle
rss

  • The point I was making here is you start sabotaging & can end up harming people that may have been allies

    How? The call to sabotage was against fascist programs, like surveillance, illegal arrests, etc. How would sabotaging those hurt people who could have been allies?

    Second, the more you start demanding people do what you want else you’ll sabotage, attack them, etc

    That is nowhere near what is happening here. We have a system of laws that is being broken. Nobody was calling for sabotage when those laws were followed. But people who use less aggressive methods to combat fascism, i.e. writing op-eds, speaking publicly against administration policies, leading protests, have started facing punishments. They are preventing the normal exercise of civilian power, so we have to escalate to sabotage or similar actions. That doesn’t make us like fascists because we are not the ones defying and breaking existing social norms and laws. This is a ridiculous argument.










  • I didn’t cherry pick a statement. I included the part where they said the very first draft.

    I did fail to explain how its a power grab, but that’s was only because I thought it was a fairly obvious one-to-one point. I’ve also added another example. But lemme try again.

    1. Mastodon has a history of pushing features that affect interop with other implementations without seeking feedback from other implementations or outright ignoring the feedback they do receive.
    2. A member of the mastodon team wrote a FEP to formalize a setting related to search indexing. This was the right way to go about it. yey Mastodon was working with other implementations. But that FEP didn’t receive positive feedback and it seems like it was abandoned.
    3. Now mastodon is trying to standardize something using the ideas from that FEP, outside of the FEP process (which is the agreed upon way to collaborate between implementers).
    4. They’re warning on their site that they have deadlines and may not incorporate feedback if they can’t resolve it without breaking deadlines.
    5. They are under no obligation to incorporate it after their initial draft and, historically, mastodon is unwilling to update their work to incorporate other implementers’ feedback.

    A more collaborative way to do this would have been to seek feedback before making a grant proposal and making the grant proposal jointly with other projects so they weren’t the only ones getting paid for it.


  • Mastodon has a history of steamrolling other implementations.

    This means we might not always be able to incorporate all the feedback we get into the very first draft of everything we publish

    The site even warns that theyre on a deadline and may not incorporate feedback.

    EDIT: they also mention a “setting” that determines if a user/post is searchable. theyve presented a FEP to formalize this setting but nearly everyone else had issues with their proposal. as usual for mastodon, this looks like them sidestepping external feedback and just doing what they want












  • Then, there is TikTok algorithm which is a common critic of the app but is how you get a never-ending flow of content which isn’t uninteresting enough for you to turn the app off

    I think there needs to be some kind of discovery algorithm for new users with an empty feed (or even existing users who just wanna find something new) but a federated alternative doesn’t need something as powerful as the tiktok algorithm to be a decent replacement. It doesn’t need to surface a “never-ending flow of content” because it doesn’t have a financial incentive to keep you in the app endlessly.




  • I could see walking through a debug session document with a junior dev to guide them on how to debug classes of issues better. Or if they’re running into a bug and ask for your help, you could write out the first few debugging steps and let them take it from there. That might be easier to understand than “I’d check service X and see if it’s processing Y like it should or just passing it on to Z”. Having a defined way to explain how to debug an issue could be useful