aeharding

You can block the lemmynsfw instance.

You have to restart the app. It’s a bug that Apple regressed in iOS 17.4 (there is an open ticket)

Should probably surface error but been hoping Apple would move faster so it wouldn’t be necessary… sigh

Edit: https://bugs.webkit.org/show_bug.cgi?id=277615

No API, its just some JS code that resizes in a canvas.

It’s ez

Voyager app users

It would be cool if it showed up for mentions, but voyager would have a make a separate request to retrieve (unless already cached). Not impossible but definitely a future thing!

Hey! Through DM, about a week ago. I'll copy below (it's nothing sensitive):

Everything seems pretty great, with the only friction I'm working through is regarding user uploads.

It looks like when using 3rd party clients (like Photon or Voyager's PWA) and I try to upload an image that is too large to lemm.ee, lemm.ee is not properly setting the CORS header. This means that Photon/Voyager can't see that lemm.ee is rejecting the upload due to image size. It seems to be working on lemmy.world.

(Please note that Voyager automatically compresses images to fit within 1MB, so it may be best to test with Photon - the same problem can be observed and replicated there.)

lemmy.world:

lemm.ee:

If you have time to take a look, I'd appreciate it! No rush at all.

The issue is lemm.ee disables image uploads until accounts are four weeks old.

From lemm.ee sidebar,

Image uploads are enabled 4 weeks after account creation

I contacted your admin (@[email protected]) about an issue where the response to the image upload doesn't have the proper CORS headers, which prevents Voyager from reading the response. Hopefully that gets resolved at some point so we can get more helpful error messages :)

Woodmans ftw

There’s a PR on GitHub for this I’ve been working on the last few wks. Probably a week or two out.