• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle

  • The lack of an ability to prevent someone from doing something to you, without compromises on your part, is not the same thing as being okay with it being done to you.

    3rd party services can access the posts, because the authors marked them as publicly accessible.

    Those same 3rd party services can also index the posts in a search engine, but this is only because there is no feasible technological barrier to prevent them from doing so. If such an imaginary technology did exist, it would have been deployed already.

    In the mean time, we can only count on a social solution, which is to merely signal our objections to search engine indexing, in the hope that maybe a law could be drafted that uses that as precedent to make indexing without consent illegal.

    Here’s a question for you. Do you think it’s okay for Google or whoever to install invisible cameras everywhere in public spaces, that were explicitly for the purpose of collecting data to develop a facial recognition model to search people without their consent? Public space is public space …


  • Feeds/timelines are first-class citizens in the AT protocol and are decoupled from account hosting.

    On Mastodon, your timelines are computed by the same server that hosts your data. Consequently, signing up to a server to have an account on the fediverse is the same thing as joining a community. You follow the servers rules and share the same local timeline as everyone else on that server.

    On Bluesky, feeds are arbitrary, fungible and provided by any server, and it can be computed/curated/moderated however they like. So communities are “built” around feeds rather than around account hosting providers.

    The AT protocol also has “real” account portability (though I have not seen this demonstrated in practice https://atproto.com/guides/overview#account-portability). On Mastodon, account “portability” is a delicate dance that requires the cooperation of both the origin and destination server.

    Mastodon has something that Bluesky currently doesn’t: real federation. The Bluesky server that everyone signs up to doesn’t federate with anyone else, since the whole protocol is still a work-in-progress.




  • Spam has consistently been the death of the open internet, even the big tech silos struggle with spam (Instagram for example – despite having incredibly invasive techniques for identifying “genuine” users – is STILL inundated with spam commenters). I think instances on the fediverse should reconsider their open registration policy, either totally close registrations when you reach an agreed upon critical mass of users, or adopt some form of invitation or application system for new users. I believe Mastodon supports both in the software.




  • a twitter-like platform needs a big central algorithm that can associate posts with certain topics and interests to be able to serve up an interesting feed

    I grew up on Tumblr and it thrived for the longest time with a chronological timeline.

    most people are just kind of shouting into the void and that endless storm of posts has to be filtered and organized somehow

    Yes, it was done through tagging. Notably, tags in Tumblr didn’t have to be inline.

    Tagging died on Twitter because the inscrutable blackbox of the algorithm made people unsure if tags actually improved the visibility of their posts or not, there’s some folk-wisdom that suggests excessive tagging leads to deboosting of your profile, since it could have been considered spammy. Also, there’s only so many characters in a Twitter post and sometimes there’s just not enough left for relevant tags.


    1. This isn’t just a Mastodon problem, all fediverse softwares struggle to keep an accurate tally of faves/likes/whatevers on posts from remote instances

    2. It doesn’t look like this anymore on mastodon.social

    3. Search isn’t free so it’s up to the admins to decide how good/powerful they want their search bar to be.

    4. It shows all followees/followers of a user if said user is local, but if the user is remote, it will only show local followees/followers of that user because knowing what remote accounts follow what remote users also isn’t free.