I’ve been working on a Threadiverse frontend for almost a year called Blorp. Originally it was Lemmy only, but now it also includes PieFed. (source code) (try web version)

I just Dockerized the frontend and started publishing the Docker image, and I would love your feedback!

  • REACT_APP_DEFAULT_INSTANCE (e.g. https: //lemmy.zip no trailing slash)
    • Changes the default instance
  • REACT_APP_LOCK_TO_DEFAULT_INSTANCE set this to “true” or “false”
    • When true, this prevents the frontend from logging into other instances. Perfect if you host your own Lemmy instance and want this frontend to exclusively be used with your instance. You can still log into multiple accounts on the locked instance
    • When false, you can log into as many accounts across as many instances as you want. You can even mix and mach Lemmy and PieFed
# pull the latest Blorp image
docker pull christianjuth/blorp:latest

# run it on port 8080 (host → container), passing any runtime env‑vars you need
docker run -d \
  --name blorp \
  -p 8080:80 \
  -e REACT_APP_DEFAULT_INSTANCE="https://lemmy.zip/" \ # BUT without the trailing slash!
  -e REACT_APP_NAME="Blorp" \
  -e REACT_APP_LOCK_TO_DEFAULT_INSTANCE="false" \
  christianjuth/blorp:latest

Edit: I cannot get the trailing slash in https://lemmy.zip/ to go away, but make sure you exclude it. Idk what sorcery is going on with Lemmy, but it seems impossible to link a domain without a trailing slash. I’ll make the docker image more forgiving in the next update.

  • moseschrute@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    11 days ago

    I was today years old when I learned Lemmy doesn’t let you have links without a trailing slash

    POST https://lemmy.ml/api/v3/comment

    • moseschrute@piefed.social
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      11 days ago

      It get’s even weirder. I’m now writing this from PieFed. If you view this comment from PieFed it won’t have the trailing slash, but from Lemmy it will. https://piefed.social

      Thank you for coming on this journey with me.

      • cecilkorik@lemmy.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        11 days ago

        Very interesting I wonder what happens if I post both trailing and non-trailing options, do they both get canonized into the same format?

        https://piefed.ca/ – has a trailing slash https://piefed.ca/ – does not

        Thank you for having me along on this journey. I don’t really know where it’s leading, but maybe it’s about the weird software behaviors we discover on the way.

          • cecilkorik@lemmy.ca
            link
            fedilink
            English
            arrow-up
            2
            ·
            11 days ago

            Yup, they all have trailing slashes when viewed on Lemmy, and 3/4 have trailing slashes when viewed on piefed. So only piefed actually respects what was originally typed. Lemmy adds a trailing slash when you’re adding the comment, and also adds a trailing slash when reading a comment posted that doesn’t originally have a trailing slash. Intriguing (and slightly annoying).

      • shnizmuffin@lemmy.inbutts.lol
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 days ago

        No, not at all.

        They are a shorthand for “give me the index of this directory” rather than “give me the first file you find named this.” In some configurations, the presence of absence of a trailing slash dramatically reduces the amount of computation an HTTP server must execute before responding to the request.