this post was submitted on 07 Sep 2024
6 points (87.5% liked)

Meta

625 readers
20 users here now

Discussion about the aussie.zone instance itself

founded 1 year ago
MODERATORS
6
URL question. (aussie.zone)
submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]
 

My web dunce question of the week is,

Why would the images url be linked to aussie.zone when the community is blahaj.zone and the poster is lemm.ee?

Is it as simple as the lemm.ee poster might have seen it on aussie.zone and cross posted, or copied over from there?

Edit,

So, just checked this post on the sync app, (using Jerboa for the post), and sync has recognised the image as a URL? I'm confused, i loaded it in Jerboa like i'd normally load a screenshot as an image. Anyway, sorry if the picture doesn't display.

I'm just trying to understand the lemmy system a little better, not trying to highlight a perceived problem.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 2 months ago* (last edited 2 months ago) (1 children)

It's the new caching system. Our server detects images uploaded to other instances and goes to download them itself, caches them, and serves them to you.

Frustratingly, your images aren't showing up for me. Neither the one in this post nor your recent !perth post. All I can see is the title & text.

[–] [email protected] 3 points 2 months ago (1 children)

Ah, that makes sense.

Frustratingly, your images aren't showing up for me. Neither the one in this post nor your recent !perth post. All I can see is the title & text.

Ah, that one might be a different, its a link to the certificate, not a screenshot. I also entered it in the link field not under 'upload image'. Don't know if those details would make a difference.

It grabbed the image and displayed it for me when i's making the post though.

[–] [email protected] 5 points 2 months ago

Both images work just fine on my phone. It's just on the web that it doesn't work for me. So obviously it's a problem with the web client, not the server.