On the Fireside Fedi interview with Jerry ( the admin of Infosec.Exchange Mastodon instance ) a scary truth was suddenly revealed ( on 34:11 ): Just to keep the instance up and running he needs to spend up to $5000 a month, pretty much out of his pocket. Donations to the instance barely cover any of that. And if he will ask people to pay to use it, they will, rightfully so, switch to a different instance.
  • Ben Matthews@sopuli.xyzEnglish
    11·
    2 days ago

    That makes sense, to store only popular stuff, or temporarily - especially for ‘heavier’ images (although as we see with lemm.ee, that leads to issues when an instance dies). Yet I also wonder about the scalability of just the minimum meta-info, whose size does depend on the protocol design.
    For example with Lemmy every upvote click propagates across the network (if i understand correctly, mastodon doesn’t propagate ‘likes’ so consistently, presumably for efficiency, but this can make it seem ‘empty’). Maybe such meta-info could be batched, or gathered by a smaller set of ‘node’ instances, from which others pick up periodically - some tree to disperse information rather than directly each instance to each other instance ?
    As the fediverse grows, gathering past meta-info might also become a barrier to new entrant instances ?

    • rglullis@communick.newsEnglish
      2·
      5 hours ago

      mastodon doesn’t propagate ‘likes’ so consistently, presumably for efficiency.

      It is not a matter of efficiency, but solely of how AP works. All it takes is someone one an server to to follow a community for that server to receive every vote/post/comment, while to get a whole conversation thread on Mastodon you’d need to be on the same server as the original poster or your server would need to have at least one person following every server involved in the conversation.