Skip Navigation

  • Looking great, and thanks for the tip!

  • Like others have said, these are Card components. Usually you’d create an empty low-level Card component that has basic props for different styles (rounded, flat, error, etc.), slots for the content inside, and event handlers for interaction. Then, if you wish, you could make another CardGroup component that can contain Card components and position them using flexbox or grid like the example you provided.

    Another possible name for these components would be List or ListItem

  • If you have language settings or are not showing bot accounts, those comments will be hidden too but the comment count still includes them

  •  
        
    curl --request GET \
         --url 'https://lemmy.world/api/v3/post/list?type_=All&sort=New&community_name=memes%2540lemmy.ml' \
         --header 'accept: application/json'
    
      
  • Thank you, looking forward to sharing it! 🎉

  • Yes, this is on the roadmap but it will be some time. There are a couple technical hurdles to jump first due to Lemmynade using server-side rendering for SEO/performance. Once those are nailed down (and the website/PWA are running smooth) we can move on to app store releases :)

  • There is less content here than Reddit because there are less users here—less users creating content each day. Each of our comments and posts have far more weight and impact on the Fediverse because of this. The more we push ourselves to engage, create posts, or moderate communities when we normally wouldn’t before, the faster we will see Lemmy grow!

  • Thanks! Really useful info in there

  • As a dev, Lemmy comments are really difficult to work with and sometimes they go missing. Every app tries to mitigate it their own way, but ultimately we are waiting for Lemmy to improve and have clearer documentation on comments. So to answer your question, it’s probably both a Lemmy and Memmy issue.

    Also, if you have bot accounts disabled/hidden in your settings, it also hides bot comments

  • Can you explain this, or point me in the right direction to learn more?

  • Thanks, I totally agree—just added this to the roadmap for Lemmynade

  • Ah, I wasn’t fully understanding, I see what you’re saying now. There’s no way to know the number of comments on a single level/depth as of now without some extra fetching. I think your best bet at this point would be preloading the next page of comments on the top level, and if no comments are return you then know not to show the “load more” button.

    Then, each time the next page of top-level comments is fetched, you can also fetch the children of each comment. This will prevent unwanted layout shift and ensure all children are fetched. If you don’t do this, I’ve noticed sometimes child comments go missing when I try to fetch multiple levels of comments in one request from a larger comment tree (100+ comments)

  • Might be applicable here—if you have chosen to not show bot accounts, bot account comments will be removed from the response but the comment count doesn’t account for those comments

  • Lemmynade will be right up your alley when the public alpha is released. I just put this down on the features list to make sure it gets added! It’s a full desktop website so it looks great on large screens (or you can install it as a mobile PWA too if you wish). You can follow updates at !lemmynade@lemm.ee

  • I’ve got this in the feature list for Lemmynade—you can tap and hold your profile picture in the bottom-right for quick account switching at any time. This is awesome for times when you write a comment and then suddenly realize you want to post it under a different account (happens to me all the time!)

    Sadly, the alpha version hasn’t been released quite yet so you’ll have to wait. You can follow !lemmynade@lemm.ee to know when it drops

    I’m sure others developers will be implementing this down the road, we’re all working hard to get some good options out there for everyone!

  • It’s hard to estimate because of Lemmy’s many quirks and bugs. I’m hoping to have the alpha version ready for public testing by mid-September, but it might be longer if I’m still having to find workarounds for current Lemmy issues. I promise the wait will be worth it!

  • In my web app, I just say "X more replies..." on that button using the child_count property. It really doesn't matter much to the user how many comments are going to be loaded next in my opinion, and that keeps it simple on our end.

    If you really need to know this, you could consider faking it a bit by fetching an extra level/depth each time the user presses that button. Then, just hide that extra level until the user presses the load more button, and manually count how many comments there are in that next level. This way you can have the correct direct descendant count, each level will load instantly to the user, and you'll be fetching the next level in the background.

  • I know, we're all here trying to find temporary workarounds for these types of things haha, it'll get better