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.zipno trailing slash)- Changes the default instance
REACT_APP_LOCK_TO_DEFAULT_INSTANCEset 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.
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.
And posting from piefed, is the result the same?
https://piefed.ca/ – has a trailing slash https://piefed.ca – does not
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).
On a similar but unrelated note, Lemmy also displays the two-hyphens as an em-dash, but unlike the trailing slashes, it does not encode that into the comment, so on piefed you still see the two-hyphens in both comments.
Fun!
I see two separate dashes in voyager
Edit: I misread your comment. I see you pointed out that it doesn’t encode the em dash into the comment itself.
I think that might just be how Lemmy’s default frontend renders markdown. The trailing slash thing happens at the API level. But a quick test shows submitting a comment with two dashes sends back a comment with two dashes.
POST https://lemmy.ml/api/v3/comment