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!
Thank you! We’re still using the PieFed backend, so they deserve just as much credit. That have been incredible devs to work with.
I find it too buggy to use. I loaded it up to give some specific examples but it won’t even load any posts. So I guess that’s a good example of how buggy.
Sorry, I would love to get this resolved. Are you using PieFed.zip? There also might be errors in the JavaScript console that will give a good hint to what the error is. If you’re not sure how to do that, you can search how to find JavaScript console in your browser or choice. Happy to work though the bugs here of over DMs.
Solving these types of bugs makes the app better for everyone. Please don’t hesitate to bug me with these types of errors.
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).
This might take a few back and forth messages to solve. Two questions:
- Are you using a VPN? I’ve found Lemmy/PieFed instances often don’t play nice with a VPN
- 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.
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.
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 @[email protected] 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.
hmm the only problem ive had in the day or so of using it was search taking a little to load but ive havent had a problem where it wouldnt load out right
I wonder if that’s a PieFed optimization issue. They’re still very new and likely have room to improve performance. But I’m happy to look into the issue and I can forward my findings onto the PieFed devs.
Do you have many communities blocked? All the Lemmy apps I use sometimes fail to load posts in the All feed, but I think it might have something to do with my account blocking thousands of communities.
In your case (especially if you’re instead using Piefed), perhaps Blorp has a distinct glitch if its own, or there’s an unrelated glitch common to them all, or something is problematic with the Lemmy API regarding mass-blocking. In any case, it’s definitely something that should be fixed.
I’ve ironed out a lot of the PieFed bugs, but looks like this is another one. Hopefully we can get this fixed. I just need some debug info.
I would also love to work with someone with many blocked communities/users to make sure Blorp works for them.
