This might be tricky then. I’ll do some poking around and see if there are any obvious performance improvements I can make. But no promises

Is it worse on posts with more comment? What happens if you open a post with 0 comments?

Anything specific or just everything? Admittedly, I don’t spend enough time testing Blorp on older phones.

Blorp dev here. Comment are virtualized. That means anything that isn’t currently in view can get unmounted to keep the comments page super snappy. For small posts, this is definitely overkill, but it means we can smoothly render posts with thousands of comments.

I’ve kinda been waiting for someone to complain about this for me to fix it. What I’ll likely do is implement a custom search box that is compatible with the virtualized comments. I have a lot on my plate rn, but I’ll get this fixed as soon as I have time. Sorry for the inconvenience.

blorp blorp

What was the dealbreaker with Blorp and how can I make it better?

The steaks are very high. I could lose access to my media library for 1-2 evenings (the time it would take me to switch to Jellyfin).

I know modern tools get a lot of hate on Lemmy, but tainwind and shadcn have been amazing to work with. Next.js has been a little bumpy the last few years, but if you know what you’re doing, you can deliver a great UX with React. I’ve been enjoying Vite + React for anything that doesn’t need SSR.

Who’s lightsaber has the largest girth?

deleted by creator

Blorp dev here. I would love to get this resolved. Could you be more specific?

• If you’re on the web: could you link the specific page(s) you are seeing this error on?
• If you’re on the app: which screens are you on (e.g. all feed, local feed, subscribed feed, a specific community feed)

It’s easier to debug things on web, and Blorp shares 99% of the code between app and web. So if possible, could you recreate the issue on web, and link that? Knowing what instance you’re using (I assume sh.itjust.works), is also helpful.

Edit 1: I saw you added a little more context in another comment. I’m having trouble recreating the issue on the all feed using sh.itjust.works. I see the first page of 50 posts loads, when I get to the bottom, it loads the next 50 posts and so on. Maybe describe exactly what’s happening in excruciating detail. It it slow? Does it never load? If you wait 60 seconds, does it eventually load? Are you using a VPN?

Edit 2: It seems others are getting this same error https://sh.itjust.works/post/43676767

Thanks! Blorp is far from perfect. For example, private messaging can and will be improved when I get around to it. But I’m pretty proud of what I built so far!

Arguably the first branch is backwards. I don’t use windows because I fear technology and strongly distrust Microsoft.

This is what the new extra compact posts look like. I can probably tune this a little more, but let me know what you think. That’s currently in beta. Idk if you’re using Google Play, but if you are, you can join the beta for immediate access.

The filter system I described will take more time to implement. Probably a few months, but it’s going to unlock filtering that no other Lemmy/PieFed client currently supports

I don’t think I’m going to add this feature tbh, BUT

I’m currently collaborating with the Interstellar devs to design a very powerful filter engine for both our apps. This will let you load in one or multiple filter files for complex filtering within the app. The specification we designed would allow you to write a filter that says

IF post.thubnail.url has length > 0 THEN hide the post

You can combine that with other checks

AND post.community.url is in this list

And the best part, these filters will be shareable with other users! You will be able to browse or optionally publish a filter you designed.

Instead of building a dozen niche features like this, we can ship one very powerful filter engine that can handle many use cases. How does that sound?

Blorp dev here. Do you mean hide the image posts entirely, or just hide the image from the post? I’m in the process of rolling out an “Extra Compact” post view that renders the image posts without the images. But that won’t roll out to iOS and Android for a few days.

You don’t think watching people age has any effect on young people’s desire to reproduce?

It is kinda ironic having this debate on a platform that isn’t static html