Andrew

I made a post here: https://lemmy.world/post/16949903

Hi. I raised an Issue on the crawler's repo a couple of weeks ago. Still waiting for a response though ...

Yeah, maybe. I'll leave it with you ...

Fixed now - a community called "wave" music caused a JSON deserialization error (because JSON uses " for its own purposes).

It's been 2 weeks since I raised the Issue for 0.19.4 / 5 instances on lemmyverse - given that there's been no response, we might have to give up with these lists anyway.

The last time I raised an Issue, the dev did respond, but it was a full week later. Maybe just considered low priority vs. other stuff in his life, rather than unmaintained. Hopefully, anyway. We'll see ...

For lemmyverse, the issue for it is here: https://github.com/tgxn/lemmy-explorer/issues/184

We'll have to wait until that dev responds, or maybe until Lemmy devs change their mind about not providing a nodeinfo 2.0 response for 0.19.4 instances.

EDIT: ah, me and Blaze were commenting at the same time, it seems.

More and more stuff won't feature as instances continue to upgrade to 0.19.4, as lemmyverse.net doesn't yet support it (there was something like 582 instances listed yesterday on there, it's 572 now).

Hello. This data is sourced from lemmyverse.net, which uses its own crawler, distinct from the lemmy-stats one. The underlying issue is likely the same, so I've filed a bug here (past experience suggests that the dev won't be that quick responding to it though)

The instance I'm on is defederated from links.hackliberty.org. I'm not certain why, but I looked at it to find it's a place for conspiracy theories, including '9/11 Truth' stuff, so it's probably that.
There looks to be a bit of indecision about the right instance for a new 'privacy' community, so I'm just mentioning this in regard to that.

Nothing yet for today (Sunday), because the crawler at lemmyverse has failed. More info is here: https://github.com/tgxn/lemmy-explorer/actions/runs/9434433542/job/25986550190 - it's bailed because there are 6011 communities missing from that run compared to the previous one. I've seen that number before, which suggests it's a single instance with that many communities which is failing to give a response.

EDIT: the midday run worked though.

Context: https://www.theguardian.com/politics/article/2024/jun/07/rishi-sunak-says-sorry-for-leaving-d-day-event-early-to-record-tv-interview

*removed externally hosted image*

lemm.ee have upp'd to 0.19.4, and presumably turned on the Image Proxying thing - this is what I get for: https://lemm.ee/post/34040618
*removed externally hosted image*

{"error":"unknown","message":"Request error: error sending request for url ([http://127.0.0.1:8080/image/original?proxy=https://ichef.bbci.co.uk/news/1024/branded_news/be3c/live/2a45fdb0-20ee-11ef-a3ab-e73c00cc3104.jpg)](http://127.0.0.1:8080/image/original?proxy=https://ichef.bbci.co.uk/news/1024/branded_news/be3c/live/2a45fdb0-20ee-11ef-a3ab-e73c00cc3104.jpg)): operation timed out"}

This isn't really my area, but I'll have a crack. From what I understand, Lemmy uses the 'meta og:image' tag to grab a thumbnail. Inspecting your site, I can see that that tag is in the html head. However, if you just 'curl' the URL, then it isn't in the results. Using 'curl' for URLs from sites that are known to work in terms of generating thumbnails (theguardian and bbc), the tag is visible in the result.

This suggests that your site is using further scripting on page load to provide the meta tags, whereas perhaps Lemmy can only get them if they are provided immediately. There are other sites (like Reuters), who use additional scripting, that Lemmy is unable to get thumbnails for also (e.g. https://lemmy.world/post/16203031)

Most people will be unaffected ('cos their instance already has a copy), but trippingthroughtime has a broken outbox, so it won't come with old posts if it's a fresh discovery. Issue should be fixed in Lemmy's 0.19.4 update.

This is for other frontends, but I remember reading something about image uploads not working when you're self-hosting due an issue with CORS. I don't know what CORS is, really, so can't expand on it. It may be that you need to upload the image to a filehost like postimages.org and link to the inline version of that instead.

I like to pretend that I'm !native plant gardening@mander.xyz when I don't mow my lawn, but I've subscribed in the hope I'll start doing it properly.

Okay. Will do.

Oh, right: lemmy.ca now has a 'content bot', hot linking stuff from Reddit.

Oh, okay. Citing the specs is a good argument killer.

There's a Closed Issue relating to this at https://github.com/LemmyNet/lemmy/issues/3540
From there you can navigate to the right place to open a new Issue if you want.

That's arguably the expected behaviour - for a discussion, 'link' effectively takes you to the comments, for an article (or a link to a image), it takes you there instead.

You could use 'guid' instead - that always links to the post on Lemmy, and it usually contains a useful thing on other sites' RSS feeds.