• 14 Posts
  • 42 Comments
Joined 9 months ago
cake
Cake day: February 16th, 2024

help-circle







  • 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














  • PWAs were not liked when they came out.

    By some ppl. There were also ppl who did like them. As soon as the desktop support was axed, fans of the feature started complaining immediately.

    at the time, people in general did not like PWAs as a concept. Independent of the browser

    Again, I think this is a sampling issue, because my experience was the complete opposite.

    And one of the key parts of PWA features was the “Progressive” part. The site works without those features and you don’t have to use them so removing the support never made much sense to me.




  • 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.




  • A regular two rail train is much simpler and cheaper to operate. The idea these techbros have that everything is made better with individual pods is pretty wasteful

    These are existing, abandoned tracks. There were regular two rail trains there but nobody used them

    The point of this seems to be reusing those tracks instead of tearing them out and replacing them. And this would still help reduce car traffic and ownership even if it’s less effective than regular public transit