• 6 Posts
  • 152 Comments
Joined 1 year ago
cake
Cake day: October 6th, 2024

help-circle

  • I’ve been kicking around this idea for awhile where Blorp has a filter engine. You can define and combine a bunch of rules like post body contains text and community name does not contain. The rules are bundled into a “file” and given a name. E.g. no US politics is a file you can subscribe to. The file can be auto updated if you choose to subscribe to updates. Blorp would come with a bunch of predefined filter files, but you can create and share your own.

    I really think this would be a killer feature, but there is a little complexity in implementing it. I also want to collaborate with Interstellar devs so you can use the same filter files in either app. Anyway, I’ve been procrastinating building this about will take me a couple months.

    But what do you think?






  • I think what’s happening is the app is refreshing in the background, and it’s not smart enough to tell the difference between initial launch and background refresh. I would either have to think of a solution to tell the difference, or have a toggle to disable automatic refresh entirely, so you always have to pull to refresh. But even I solved the refresh issue, I think it will still throw you to the top of the feed :/








  • I don’t think caching benefits Lemmy and PieFed content that is changing very rapidly (e.g. new comments). That type of caching makes more sense for Lemmy/PieFed images.

    However, bot traffic can get very expensive these days with all the AI crawlers. Cloudflare offers very good tooling to block these bots. I know there are other open source tools and I’m not defending Cloudflare, but it’s also easy to criticize when you’re not the person running the instance. From what I’ve seen, all the admins work very hard to keep the threadiverse running. I’m guessing that’s why a lot of instances are using Cloudflare.