It’s not a client issue. It’s a lemmy/instance-specific issue. Look at the following link in your browser, then tap the image to expand. You will see bad image quality. https://lemmy.world/comment/11323036

Edit: Works fine with my vger.social account. Looks like shit on lemmy.world.

Edit 2: Looks like shit on sh.itjust.works and lemmy.world. Which are both running very outdated 0.19.3. Looks great on feddit.org, vger.social, lemm.ee which are running up to date version of Lemmy (0.19.5).

You’re welcome! 💜

It depends on your instance.

This will be resolved once https://github.com/LemmyNet/lemmy/issues/4698 is resolved so please give it a “thumbs up” if you want it!

Can you do a screen recording? THanks!

Go to profile -> hidden posts -> reset

What do you mean, “voyager wasn’t going to be supported”?

The only time I’ve heard that happen is when people had Lockdown Mode enabled.

I don’t think this is possible. To block you need to provide lemmy the instance ID.

This will be fixed next release!

The way it is in lemmy-ui now is fine.

Now do jxl support

Alternate icon support? Voyager already has the ability to select an app icon, and has a themed icon.

Sounds like a nice feature for next Halloween 🎃

Voyager can handle SVGs. The image you linked for the SVG is invalid. When I try to load it in a browser, it says there is a server error.

Mlem in app browser is using an in app browser API that is secure by design. It doesn’t allow snooping or injecting anything. This article is talking about abusive apps like Facebook that roll their own in app browser.

Edit: although on iOS, the secure iOS in app browser api is always using safari engine, so the user choice argument is still valid.

It’s crazy that the in-app browser isn’t an OS-level overlay that the app can’t influence or look at what the user is doing in it.

Android and iOS both have apis for in app browsers that are secure by design. Voyager for Lemmy uses this. Mastodon uses this. Last I checked even Twitter used this. However Facebook does not.

these platforms also offer lower level APIs to build custom interface which are more powerful and flexible (but can be abused). This isn’t necessarily a problem. Custom browser apps need that functionality, and apps sometimes display their own content with web views.

The problem is that app stores allow slapping a skin on this more powerful API and treating it like an in app browser to connect to arbitrary sites. Dumb imo. If you offer an in app browser, it should be required to use the platforms secure in app browser API.

More powerful APIs should only be available to browser apps and displaying your own content in a web view.

This should now be fixed.

Thanks! The issue is with compact mode. I’ll try to get a fix out tonight.

I just checked Android 14 with PWA and it is working as expected. If I tap a photo the post is marked as read.

I assume you’re logged in, maybe could can make a video just in case I am misunderstanding?

It is working for me. Can you provide more information, such as device info and the specific post and double check your hiding settings just in case.