hachyderm.io is one of the many independent Mastodon servers you can use to participate in the fediverse.
Hachyderm is a safe space, LGBTQIA+ and BLM, primarily comprised of tech industry professionals world wide. Note that many non-user account types have restrictions - please see our About page.

Administered by:

Server stats:

9.6K
active users

Good morning Fediverse.

I would really love a fact checking service for ActivityPub related posts. E.g. is this post correct? Not aiming to throw shade at the author, but I suspect that it's very wrong.

E.g. 100 Mastodon Instances having 1 user each, might individually consume more resources than 10 Mastodon Instances having 10 users each. Assuming an appropriate number of posted images and correct follower relations, e.g. every user follows every other user.

Actually one can probably do the test: What consumes less resources

  • a server Abel with Alice and Bob on it (following each other), and posting lots of stuff (including media)
  • a server Abel with Alice on it (and Bob on a second server), both still follow each other and post lots of stuff (the same).

Please note that, I'm not including the resources of Bob's server in the comparison. I'm also confident in some of the answers: In both cases the storage cost for Abel is the same!! 😱😱😱

Elestioj_forrest (@j_forrest@mastodon.elest.io)One the best things you can do to help the decentralized network grow is to self-host apps using things like #ActivityPub. This distributes the resource needs of supporting a large number of users on single instances of applications that use #ActivityPub or similar protocols to "federate" or interoperate with one another. The more servers, the more people can find their community, and the more than can join in and take back their net experience! #selfhost

@helge There is significant overhead to run just one server, and even higher overhead if that server is mastodon or mastodon-like.

Comparatively: grouping users together on a single server is _very_ efficient from both a connection and cost standpoint, especially if they follow each other.

If you take that same network and you spread it between multiple servers you have orders of magnitude higher resource costs per user and there's basically no getting around that with the current architectures. Not even getting into individual administrative costs (time) per person.

Hrefna (DHC)

@helge People fetishize this idea of one person servers, but it's really not a good idea on multiple levels (on SO MANY levels, really) even to the degree that one can technically do it.