i honestly HATE the standard piefed ui thats what kept me away from the site as a regular user, BUT THIS UI! i feel right at home and it runs so smooth! great work whoever works on this!

  • Schwim Dandy@piefed.zipEnglish
    1·
    4 months ago

    Here’s what I see in console. I compared to piefed.zip’s vanilla UI and the errors seem to only occur on their blorp install. Seems to be mostly cloudflare errors. I did a shift-refresh and the cloudflare challenge appears, which I complete, resulting in the Blorp page load with shadowboxes for articles that stay for about 15 seconds before they are replaced by “Nothing to see here”

    Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015. (Reason: CORS request did not succeed). Status code: (null).

    None of the “sha512” hashes in the integrity attribute match the content of the subresource at “https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015”. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”. home InstallTrigger is deprecated and will be removed in the future. local.adguard.org:2:11348 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015. (Reason: CORS request did not succeed). Status code: (null).

    None of the “sha512” hashes in the integrity attribute match the content of the subresource at “https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015”. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”. home Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://piefed.zip/nodeinfo/2.1. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 403.

    Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://piefed.zip/nodeinfo/2.1. (Reason: CORS request did not succeed). Status code: (null).

    Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://piefed.zip/nodeinfo/2.1. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 403.

    Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://piefed.zip/nodeinfo/2.1. (Reason: CORS request did not succeed). Status code: (null).

    • Mose13@lemmy.worldMEnglish
      5·
      4 months ago

      This might take a few back and forth messages to solve. Two questions:

      1. Are you using a VPN? I’ve found Lemmy/PieFed instances often don’t play nice with a VPN
      2. Does https://blorp.piefed.zip/ work? Potentially since that version of Blorp lives on a domain owned by PieFed.zip, it might be immune to the CORS error.
      • Schwim Dandy@piefed.zipEnglish
        2·
        4 months ago

        If I disable my VPN, Blorp will load posts. I guess it’s a misconfigured cloudflare setup as I can view posts on piefed.zip without issue when the VPN is enabled.

        • Mose13@lemmy.worldMEnglish
          1·
          4 months ago

          This is a bit outside my expertise, but I imagine the blocking Cloudflare applies is not an exact science. They likely combine many signals and use that to determine which requests get blocked. I’m guessing VPN and the origin of the request (e.g. blorpblorp.xyz) are two of those signals.

          Anyway, I’ll forward this @Demigodrick@lemmy.zip to see if there is anything that can be done. Sorry for the inconvenience. I’ll see if I can add better error messaging within Blorp when this happens.