Trying to follow Kbin communities from my Lemmy instance is a bit broken. If I try to open one, e.g. https://lemmy.nauk.io/c/linux@kbin.social from my instance, It gives me 404 and the logs show the following error:

2023-06-11T11:01:46.475407Z  WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: couldnt_find_community: error decoding response body: missing field `properties` at line 1 column 182
   0: lemmy_apub::fetcher::resolve_actor_identifier
             at crates/apub/src/fetcher/mod.rs:16
   1: lemmy_apub::api::read_community::perform
           with self=GetCommunity { id: None, name: Some("linux@kbin.social"), auth: Some(Sensitive) }
             at crates/apub/src/api/read_community.rs:30
   2: lemmy_server::root_span_builder::HTTP request
           with http.method=GET http.scheme="http" http.host=lemmy.nauk.io http.target=/api/v3/community otel.kind="server" request_id=e1b55819-fd89-4c89-a145-3ba606fb28b7 http.status_code=400 otel.status_code="OK"
             at src/root_span_builder.rs:16
LemmyError { message: Some("couldnt_find_community"), inner: error decoding response body: missing field `properties` at line 1 column 182

Caused by:
    missing field `properties` at line 1 column 182, context: "SpanTrace" }

Is this a known error in 0.17.3, if not, I should file an issue.

Edit: filed an issue

      • bdonvr@lemmy.rogers-net.comEnglish
        1·
        1 year ago

        That’s probably because lemmy.ml “discovered” that community long before my instance did. I should get all NEW posts from today onwards, but not old ones. It’s supposed to grab the top 20 current posts so that it doesn’t look empty, but I’m guessing that’s a kbin-lemmy incompatibility

    • Loccy@feddit.ukEnglish
      1·
      1 year ago

      Any time I try to go the Kbin web site as a regular end user, it routes through a Cloudflare “are you human?” Captcha. I wonder if this is causing the issue. If I try a similar URL on my instance I get “404: couldn’t find community”, but if my instance is getting the same Cloudflare nonsense back, it would probably explain it.