Ope!

Yeah, FUCK trump but the amount of easily disproven misinformation being shared on Lemmy is alarming. Mods need help?

You need to update the app

Looks like a Lemmy bug but I’d have to investigate further. The cached Lemmy media is still photo despite user submitting video

Edit: Workaround in next release!

Hi, Voyager dev here, I’d like to see a very small, terse API for clients devs to make a more seamless experience!

The MVP IMO would be a way to automatically log the user in when opening the Canvas, perhaps by

• well known Canvas user handle for client to automatically DM for OTP
• client waits for OTP in DMs
• client adds a query parameter with the user handle and OTP to the URL to open browser, so user is automatically logged in with 0 clicks!

And I could see stuff beyond this. Like an API to know event metadata, docs on how to embed Canvas in app (would be great for engagement)

Anywho simple is best but would be awesome for tighter integration of apps/clients with a documented API!

Definitely something I want to add at some point

StickerApp is much better anyways.

Of course 😁

Hi there!

So, I’ve investigated this problem many times, and in the case of your example post its the same issue I’ve seen before.

On your instance (mander.xyz), the image is not available. As an example, try to load the following link (in your browser):

https://mander.xyz/post/15080092 (MUST OPEN IN BROWSER)

As you can see the image is broken, because the image is not cached on mander.xyz, and also the original link is broken.

However, when you tap the “link” button in Voyager you are viewing the post on feddit.org where the image is cached. That’s why this works:

https://feddit.org/post/538582 (MUST OPEN IN BROWSER)

This also explains why the image works for some people and not others. Because at some point the original image link broke, and some instances had the image cached by then, but not others.

That’s also why usually the image will work on the origin server (in this case, feddit.org). Because the image was originally posted there, and that server was the first one to cache it (before the origin image broke).

I’ve thought about some workarounds for this scenario. Voyager could theoretically request the post payload from the origin lemmy instance (AP URL) and then use that cached image URL. However, this reduces privacy somewhat because your lemmy app is now connecting to an arbitrary lemmy instance.

Maybe it will be a setting in the future.

As others said, other apps are also affected by this issue because it’s not a Voyager specific issue.

Another side note, this could potentially be fixed in Lemmy backend. Lemmy devs could fetch the cached image from the upstream Lemmy server instead of using the original image URL, if it is broken.

Edit: I made a request in Lemmy issue tracker. https://github.com/LemmyNet/lemmy/issues/4899

(╯°□°）╯︵ ┻━┻

Hey, sorry I just noticed this (feel free to tag me next time).

Are you still experiencing federation issues?

It should be working. Have you tried restarting your phone?

Yep that makes sense. I am more thinking about VFR flight in the context of ultralights. So let me rephrase- in the context of ultralights (VFR) the vast majority of US airspace does not require talking to ATC or even having a radio onboard.

I’m an unlicensed ultralight pilot and I know where I can and cannot fly. Every ultralight pilot I know also knows where to fly (and how to read a sectional).

Join us !paramotor@lemmy.world

Sure but the vast majority of US airspace is uncontrolled.

Thanks, I can confirm

Edit: should be fixed next version!

Try restarting your app. That can happen if an API request fails (or if you Lemmy instance isn’t federated with the target instance)

You can disable embedding cross posts in settings to get to the original Lemmy implementation if you prefer.

I would like to add filter by action/mod eventually but not yet implemented. There might be a request on GitHub, if not already that would be a good place to start.