is it a complicated process? why do some instances support several alternative frontends while others don’t?

  • Björn Tantau@swg-empire.de
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    12 hours ago

    They have to install that somewhere and configure it to use that instance by default.

    It’s not super complicated but also not trivial.

    Edit: It’s not about “supporting” a frontend. It’s about “offering” them.

  • Illecors@lemmy.cafe
    link
    fedilink
    English
    arrow-up
    2
    ·
    11 hours ago

    It’s more code that can be abused. Balancing availability and security is never a straightforward task.

  • Shadow@lemmy.ca
    link
    fedilink
    arrow-up
    2
    ·
    11 hours ago

    It’s usually just an extra container and a little vhost config. There’s very little to it, hence why lemmy.ca has all of them as options.

  • asudox@lemmy.asudox.dev
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    11 hours ago

    Because people have different tastes. Be glad you have choices.

    Edit: It is not complicated. Setting up Tesseract for my instance was very easy (one new podman container and a change in the caddy config). Some instances might offer less frontend options most likely because hosting something costs money and requires extra maintenance so they don’t want to host something that they think people won’t use.