Have spun this up on blorp.lemmy.zip and blorp.piefed.zip :)
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!
UK here so unless I change my country I can't use it ;)
There's only one solution - you'll have to move countries 😉
Thank you! It's so validating to see people actually host my project. I'm so grateful for all the hard work instance admins put in. Please don't hesitate to open GitHub issues if you have feature requests or find bugs. Expect PieFed could break as they push breaking API changes, but I'll try and resolve issues quickly.
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
Aren't trailing slashes completely useless?
Trailing slashes actually serve an important purpose in URLs - they indicate you're requesting a directory rather than a file, which affects how servers route reqeusts and can impact caching, redirects, and SEO.
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.
blorp
The Fediverse. Poob has it for you.
Now this I like, just because I have plenty of people who really aren't techy enough and dislike a lot about the fediverse.... I know it's not for everyone but having a simple front end works for loads! Good work here - I like it, I like it a lot
That you! Idk how to explain the fediverse to my mainstream social media friends, but I think a good step 1 is giving them an intuitive front end.
I would love to eventually onboard people to Lemmy and PieFed through Blorp, but that’s a whole other challenge. Idk how to explain the fediverse to people. In a perfect world, I think people who stumbled across Blorp would figure it out with no prior Fediverse knowledge. Idk how to get there.
Would you consider supporting Mbin in the future? I like Lemmy, but I've become used to Mbin (I was originally on /kbin) and I'm somewhat attached to my instance.
Yes! I think I might need Mbin to implement the resolve_object endpoint first. I don't think they have that currently. Basically I need some way to look up posts by activity pub id. There's also a strong possibility I won't implement all of Mbin's functionality. I might just implement the parts that are most similar to Lemmy. But if you're looking for one app to login to Lemmy, PieFed, and Mbin, I would like to be that app.
I basically use Mbin as though it were Lemmy, so personally that would be fine. Thanks for the quick response.
No shade, but this looks like any other front end. Am i missing something?
Idk. There’s a lot of Lemmy clients and many of them are really good. When I started, Voyager didn’t have good support for larger screens, but I think that has changed. I do think I have the best account switching. Voyager will reset the current navigation when you change accounts. Any pages you have open will be cleared. Blorp does not do that. Blorp is also cross platform like Voyager.
But honestly if you prefer another app, you should use it! All the frontend devs are super cool!