v.0.0.6

v0.0.4 - Per requests and concerns: Defaults changed and options added to prevent overloading servers, hitting rate-limiting, filtering to top x communities, etc!

Thanks for your support!

  • hawkwind@lemmy.managementOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    I actually wrote it with the flip side of your centralization argument in mind. If a community exists outside of the popular ones a user may never even know of its existence. Having more show up SHOULD be better to prevent centralization no? It requires the users to change their browsing behaviour but at least they don’t have gonsearching offsite.

    • aaa @lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Well, yes, accessibility is what most Lemmy users are interested in. The majority of users don’t want to be told to manually crawl through lemmyverse.net, to find the communities that they might be interested in. It is for that reason that I wrote my own tool as well for my own instance, and the users on it.

      Unfortunately, because of that reason, most people would rather register on larger instances like lemmy.ml, or lemmy.world, simply because it is easier to find communities on the site itself of larger instances, than smaller instances that do not run this tool, thus exacerbating the problem of centralisation in current Lemmy era.

      Until Lemmy authors, or Lemmy admins start taking steps to reduce centralisation, be it by blocking registrations, or by somehow redirecting new users to newer or smaller instances, this will only lead to a feedback loop, where inevitably, an instance may grow so large to the detriment of the fediverse, be it sudden collapse of the instance because of funding (see vlemmy), or by hostile takeovers of the protocol (see Threads).