206
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Jul 2023
206 points (97.7% liked)
Selfhosted
39677 readers
456 users here now
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!
founded 1 year ago
MODERATORS
That may explain it... point being, content for remote communities isn't entirely "remote". I'd like to understand what goes where a lot better. I've not found it explained anywhere, and I'm not a coder so can't just "read the code yourself".
I'm not familiar with lemmy, but I did pick up on the lotide code a bit recently (a similar project)
As I understand it, the text or html of the post end up in a sort of mailbox, then your server goes out to pick up the latest posts from there. It gets brought over to your instance, and then it lives there. Whatever happens, the posts your server collected are on your server, that's how they're displayed.
Then when you go to write a post, it's stored locally and if it's on a local community then it's stored there and a copy is sent to the mailbox for others, and if it's a remote community your server will reach out to the other server and drop the post there.
My lotide instance has some older posts from servers that stopped existing a long time ago because although it can't get in touch with the remote community, the posts it did receive are still there.
Yeah post content I understand. Linked or posted images though are not consistently handled, so I'm not sure what circumstances lead to my instance pulling the image from a remote community.
I don't think lemmy typically does. I'm often on networks that block a lot of the Internet, and even thumbnails on posts from other instances or their community images get blocked when I can't communicate with them.
Right now, your profile pic for example is coming from aussie.zone, and the community pic is coming from lemmy.world, but I'm on fbxl lemmy a completely different instance from either of them.
Yeah profile pics are fine. I'm specifically talking about image posts. Next time I spot one I'll see if the post came from a user on my instance. If not, I have no idea why the post image would be on my instance.
If you right click on the image, then click inspect, then you can see the url for the image. Often it's coming from somewhere else.
Incidentally, my soapbox instance is different then lemmy -- it acts as a proxy, so it soaks up all the images and then hosts them from my one server.
Nope... thats what I'm talking about.. image posts to remote communities, with the images being sourced from my instance. Like I said, next time I spot it I'll dig into it further.
What software is your instance running?
I'm on Lemmy 0.18.0 right now. I host a number of other kinds of software too, I've been all-in on the fediverse for a few years.
You can see in this image that the meme I'm currently looking at is hosted on lemmy.world even though I'm on my own Lemmy instance.
Yep, that is nearly but not always the case.