I didn’t see a bug reported for it yet, but I was able to confirm it on Voyager as well as in the wild. Created bug #4172.

Tesseract is ready, though current release is still in backwards-compatible mode for 0.18.x (none of the new 0.19 API features are enabled, but all primary functionality is tested against 0.19.0).

However, it does have issues with the /comment/report/list and /post/report/list endpoints as well as /user/report_count. However, those are also throwing the same HTTP 400 errors as with Lemmy-UI 0.19.0-rc.4 (tested against voyager.lemmy.ml).

The first two throw a 400 with the error not_an_admin even though I am moderating a community.

I assume those are known issues?

Well, all the places that used that were passing it to a function that fuzzed the time somewhat. e.g. 2023-09-01 13:20:55.123456 becomes “1 mo ago”. So timezone really didn’t provide any benefit there.

Yeah, I took out the +Z concatenation in my frontend ahead of 0.19.0 support, and everything works fine without it.

Awesome. I just pushed up the latest release with a few features people had requested earlier today. 1.2.58.1 is current but 1.2.59 is building in GitHub workflow. Should be ready to pull in ~20 minutes or so.

Check out Tesseract.

It supports inline videos and various embeds (Youtube/Invidious/Piped, Spotify, and more).

There it is!

Thanks for checking back.

I want to say the blame lies 100% with me on this one.

When i moved over to the new domain, I forgot to disable my default WAF policy for robots.txt which is set to disallow all. Realized that late yesterday evening and turned that rule off in my load balancer.

and the more instances link to yours, the more likely it will be crawled, in case other instances drop out.

I’ve got a lot of peers in my instances list (lemmy.ml, beehaw.org, feddit.de are the largest peers), and I’ve clicked into the /instances page of many of them; they all show my domain as a peer, so I believe I’m good there.

but right now it has low prio for me as i broke my hand and try to stay away from the keyboard

Well, I definitely thank you for powering through to answer my dumb questions, and I do appreciate your time.

Ok, thanks. My response times are way less than that unless there is some other issue.

I have been dealing with a lot of rate limit errors in lemmy backend, and that may have been my fault. I’m using proxy protocol in front of Nginx, and I didn’t have the right variable set to populate the XFF header from that ($remote_addr vs $proxy_protocol_addr). I usually set those via an include for common proxy headers, but had to remove that include and add the lines manually as some of my defaults were breaking Lemmy UI.

So it may be possible my instance was erroneously rate-limiting the crawl which contributed to that? I made the fix to that Nginx config about half an hour ago. I’ll wait several hours and re-check the community browser to see if that was the cause.

One last question: Is that crawler based on any kind of existing project I can pull and fork a new project from?

Thanks for your insight.

Thanks for the info!

Well, it should have been discovered by now, I would think. My first instance was picked up the same day it went live, so that fits with the 4x a day interval you’re describing.

Any idea on what is considered a high response time? I’m using my instance, and it seems pretty snappy.

With each passing day, the goat farm option sounds better and better. Lol