Open kr428 opened 7 months ago
You mean 21a4308f
, right? Can reproduce, but only with larger images. Investigating.
Seems like we have 2 issues here:
1) pixelfed.social returns different image_matrix_limit
on the api/v1/instance
and api/v2/instance
endpoints. This triggers newer Tusky builds to resize the image before uploading it -> https://github.com/pixelfed/pixelfed/issues/4780
2) This does not explain why the resized image is rejected however. Could be a Tusky bug, will investigate further when I have more time.
Sending direct messages from a Pixelfed account does not work either, it just doesn't ever finish. Neither does accessing old direct messages work anymore (shows Tusky error page) (Tusky 24 beta, pixelfed.social)
Sending direct messages from a Pixelfed account does not work either, it just doesn't ever finish. Neither does accessing old direct messages work anymore (shows Tusky error page) (Tusky 24 beta, pixelfed.social)
Seems, though, this is an unrelated issue. (Personal observation is that direct messages in pixelfed are still, in general, notoriously unreliable and likely to be broken more often than not, not just API/app-wise... 😔)
Sending direct messages from a Pixelfed account does not work either, it just doesn't ever finish. Neither does accessing old direct messages work anymore (shows Tusky error page) (Tusky 24 beta, pixelfed.social)
Also a pixelfed issue, see https://github.com/pixelfed/pixelfed/issues/4789
tusky nightly 24a4308f : Uploading images to pixelfed.social doesn't work anymore. Steps to reproduce: Either "share via" an image to tusky, or create a new post and either take a new picture or select one from the gallery. Upload will start and then fail stating an HTTP 403 error. Fails all the time. Seems broken at least in the last three nightlies, works well in stable.