• 0 Posts
  • 111 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle






  • Same, but it is feasible outside the API as well by creating a lookup table. You could use the same to track whether the comment is collapsed, viewed comments, etc. Just make a table with:

    • comment ID
    • whatever flags you’re interested in
    • row creation time
    • data from the post - modified time, for example

    Then as you’re creating posts, reference that db and make the appropriate changes. Have an option to clear old settings after some time based on the row creation time (say, a week) so storage doesn’t grow indefinitely

    It’s feasible, but there’s a fair amount of work there.



  • The lemmy feed has gotten better, and I think it’s intended to mimic Reddit’s feed somewhat, but it still seems to include a ton of posts from popular communities that seem to drown out the less popular ones.

    So if you’re looking for new communities, all will probably not be a very efficient way to do it since you’ll need to sift through a ton of content from more popular communities (and your new niche community won’t be popular at the start).

    Also, and I could be wrong on this, I think it only shows posts from communities your instance tracks. So if nobody on your instance has looked for a given community, it won’t appear in all unless it happens to be hosted on your instance. I haven’t verified that, just that’s how I expect it to work given how other things on Lemmy work.

    So the better solution seems to be to use a directory like this one and search for communities that way. That’s what I do, and it seems pretty effective. I browse through that periodically and find interesting communities that way.

    And yeah, it’s cool that lemmy let’s you do it, I just personally don’t find a ton of value there, at least not as this point. Maybe it’ll be more useful once communities have stabilized a bit more and the feed itself has matured. But for now, it just seems like a ton of noise to me.


  • I use this directory, which works pretty well. I’ll subscribe to anything that looks interesting, then unsubscribe from the ones that end up not working out. On Reddit, I would just search, so hopefully the search improves so I don’t need an external resource.

    And I personally just search every few weeks or when I want something specific.

    What if something interesting happens

    Then you miss out. I personally don’t have much FOMO, so it’s not a big deal for me. Most communities don’t have a lot of posts, so it’s not hard to get caught up if I’m late by a week or two.

    I personally find that I skip over most content when I visit local or all, so it feels like a huge waste of time vs looking at my subscriptions. I don’t like a lot of the high volume communities (memes and other similar content), so for me, sifting through a ton of uninteresting (to me) content isn’t fun. I’d rather miss a few things than spend tons of time scrolling past things I dislike.

    Everyone is different though, and it was just an honest question. If it doesn’t work for you, it doesn’t work.


  • Is it? I almost never looked at /r/all on Reddit, and most of my subreddit discovery was by searching for keywords. /r/all had such a poor signal to noise ratio (I’m not interested in memes) that it was functionally useless for me, and I feel the same way about Lemmy and stack exchange.

    The only time I do anything like “all” on Lemmy is when I see all posts on my instance (or for stack exchange, a given site). I like to think my instance generally has a better signal to noise ratio than the larger instances, so it has some limited utility for me.

    I know other people use Lemmy differently, so it was a serious question. It fits my needs well, so maybe it would work well for others.





  • Yup, and it’s one thing I absolutely hated about new reddit.

    For example, some links the worked just fine on new reddit didn’t work on old Reddit or third party apps because Reddit allowed nonstandard links. And then there was spoiler tags, which used a bespoke syntax that took a while for third party apps to support and has edge cases that caused rendering issues. Spoiler tags still don’t work on Jerboa because it’s not part of the market spec, but at least Lemmy documents it so it’ll probably come eventually.

    We should stick to standards as much as possible so things work well across clients.