• 1 Post
  • 16 Comments
Joined 26 days ago
cake
Cake day: August 28th, 2025

help-circle

  • If computing these tags is not expensive, they can be computed and stored internally in the app at client side. If this will work and will be useful, it can be moved to server-side in one of lemmy’s updates. Each post will have have probable tags in metadata with % of how sure an algorithm was about assigning this tag. Personally, I think affecting your feed by picking appropriate instance doesn’t work, and I do hope other instance-independent ways to browse lemmy will become available. But right now I haven’t found a time even to check Lemmy’s api to see what’s already available.



  • I think it’s a matter of sorting. Do you know how does it work? I don’t. Would be interesting to know. Why exactly those posts are shown in the feed? Is it “sort all by upvotes count descending”? Probably not, because this way you will get popular post from previous year. Is it “same, but filtered to those posted within last week”? Probably not. I think interacting with lemmy’s api can shed some light on this topic. Probably you can use whatever sorting you like.









  • Probably there’s too small userbase for continuous subscribable block lists. I think I’ve seen some people sharing their blocklists on anonymous imageboards. When you can import/export block lists as plain text, probably it is enough.

    Consider checking syntax where it’s already implemented and adding this import/export functionality.

    A step forward could’ve been adding some logic: e.g. some keywords are filters for posts, some for comments, some for community/instance name. Maybe complex filtering can make federated “global” feed much more satisfying.