6
Always show link below post not working as expected (sh.itjust.works)
submitted 2 months ago by to c/summit@lemmy.world
12 comments fedilink hide all child comments
 

I have always show link below post disabled but in post and comments view for post the link is always shown below.

In settings, based on the example, when toggling this setting no link should be displayed below and I guess tapping directly on image should open the link?

Is there something I don't understand or is it a known bug? I couldn't find any post about it! If it is really a bug then it's strange that no one would have reported it before.

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 2 months ago (4 children)

In your example the post has both an image and regular link which is why the app shows both. The app will not show both if the post is a purely image post. An example is something like: https://lemmy.world/post/51036218

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] [S] 1 point 2 months ago (3 children)

    You're right but looking at raw the image is actually flagged as a thumbnail. Thunder, Jerboa and browser ui open the link when tapping on it.
    I believe Summit incorrectly flag posts as text when there is a link followed by a thumbnail. Thunder and webui flag this kind of posts as a link.

    Summit probably already does something special as it shows the thumbnail first : raw shows the link is before thumbnail. But imho, it should combine the link and it's thumbnail.

    As I keep tapping on the thumbnail which is never what I want to see, is it possible if no official info exists on how to handle such cases to at least add an : "open links for links followed by a thumbnail if tapped" or "Show links followed by a thumbnail as an image link" ?

    Hope I am not coming as negative. No matter what Summit is a great app and I am grateful for the enormous time you're probably spending on it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 2 months ago* (2 children)

    It's a valid question/suggestion. This was just how I chose to implement this feature from the start which was to keep the thumbnail and link separate. I think most apps do combine them so that tapping on the image opens the link instead of the image.

    When I was designing this I wanted to give a clear way to interact with the link vs the image. Combining them makes it murkier. Eg. what if someone actually wanted to download the thumbnail?

    I think combining them definitely makes more sense for optimizing for the most common case though.

    I think given the behavior of other apps this is probably a losing battle for me. I'll give this more thought and revisit the design of this.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 2 months ago (1 child)

    what if someone actually wanted to download the thumbnail?

    I would expect a long press to show an option to display the thumbnail. I just checked with your purely image post example and it seems that the context menu is already perfect.
    For comparison Thunder just shows a purely image post as if the picture was embedded and only shows a combined image and link when the link is a different URL.

    Thanks for considering it!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •