If you’ve paid careful attention to our sticky, you may have noticed Lemdro.id hosts a few slick web app interfaces for Lemmy. Give them a try!

These are active projects, so please do report any bugs to their respective GitHub pages linked below.

What do you think of them? What kind of tools would you like to see for Lemmy?

Lemdro.id Interfaces

  • cole@lemdro.id
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    2
    ·
    edit-2
    11 months ago

    lemdro.id is just a frontend, however it does have a special shortcut to the backend that allows it to function better under heavy load (on lemdro.id specifically)

      • cole@lemdro.id
        link
        fedilink
        English
        arrow-up
        8
        ·
        11 months ago

        Yes! There are 3 different “types” of Lemmy backends in our infrastructure. “scheduled” types, of which there can only be one, run scheduled federation traffic as well as some smaller load balanced load of requests. The “external” type handles generic requests same as “scheduled” except without scheduled federation tasks. These can spin up or down all the way to 0, as sometimes the scheduled instance can handle everything on its own.

        Finally, there is “internal”. These are dedicated backend instances that are not publicly exposed and therefore do not handle any federation traffic at all. Lemmy-ui communicates with this internal backend, meaning that our UI has a path that is entirely separate to the federation traffic and should stay responsive no matter what!

    • ijeff@lemdro.idM
      link
      fedilink
      English
      arrow-up
      4
      ·
      11 months ago

      I think they mean whether the entirety of lemdro.id is just a webapp like vger.app, rather than an instance as well.

      • cole@lemdro.id
        link
        fedilink
        English
        arrow-up
        5
        ·
        11 months ago

        ah, well this is why you usually do the communications stuff haha, I misunderstand people