Skip Navigation

User banner
Posts
14
Comments
543
Joined
1 yr. ago

  • I could add something like this. However, for most power users that are scrolling that far to encounter this issue, I recommend using the "hide read posts" feature. This will essentially keep your spot in the feed until reset. It also allows you to pull to refresh, keeping your place (essentially) while also being able to see new posts that percolate up your feed.

    This also helps with other things - if you restart the app and/or device you won't lose your place until you reset hidden posts.

    I might be able to add a long press the hide button to reset hidden posts for those that just want hiding posts to be super temporary. Would that help?

  • Try to login to any instance and submit with blank username/password.

    Alternatively, (bit more complicated but provides a nice interface to browse) you can select an instance in the signup flow, and press the (...) icon in the header to "connect as guest"

  • On voyager it links to the updated content that is crossposted. Might be good to update for other clients though (although this is the Voyager community haha).

    Lemmys crossposting is a bit clunky (。╯︵╰。)

  • What do you mean by searching for other instances?

    You can browse any instance as a guest. Not sure it that’s what you mean!

  • :( It works on lemmy-ui/photon/alexandrite/voyager (maybe others too - these are just ones I've tested that work)

  • ::: spoiler did ::: spoiler u ::: spoiler know ::: spoiler u ::: spoiler can ::: spoiler nest ::: spoiler spoilers? ::: spoiler dog pic

  • Lol. I wish XKCD showed date published.

  • Btw I just found out that lemmy-ui supports markdown citations.

    It’s not documented AFAIK though.

  • It should be fixed in the latest version

  • Yeah open an issue with the Lemmy project.

  • 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!

  • Definitely something I want to add at some point

  • 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