Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
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
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.
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