Cleans your butt and the toilet at the same time. I’m not seeing the problem here

OOOOOO I MEMEBER

It’s the other way around for me. Opens bag of chips. Cat hears plastic bag. Cat “that food is for me 👀”

This is very sad news

It’s giving ET

Finally they rewrote playstation in rust

What about Lemmy’s rate limiting?

I’m working on a client, and I would be worried that making too many requests for a nice to have feature would rate limit a request for a core feature of the app. Though I supposed some sort of throttle queue would solve that.

I’m already using a throttle queue to slow down refreshing stale data in my app. That way data that I’m asking for right now takes priority over refreshing a bunch of old data.

My cat tried to swat a sandwich out of my had yesterday. He’s 17 and very slow, but for sandwich, he’s fast.

I’m not a recycling list expert, but I think the more keys you use the less react is able to reuse components in the list. So this is one area where keys are actually worse. You may be able to use them only on the image part of the post, but packages like expo-image have a recyclingKey prop you are supposed to use instead. But I found expo image to not work very well so 🤷

But I think think the app we were referring to isn’t react native? Idk how native recycling lists work tbh so maybe you’re right about the key thing.

100% guessing here, but native apps sometimes use recycling virtualized lists. That means as you scroll the list will reuse the container that renders the post title and image. Often the image is still being fetched but you already know the title. So as you scroll, it reuses a post you previously saw, instantly swaps in the new title, but the new image is still loading, so an image from a previously post in the list is displayed.

the result is you many only need to render and reuse 10 posts in the list, even if the list contains hundreds of posts.

Idk if that made any sense at all, but keep an eye out if the title is new but the image was previously seen.

deleted by creator

deleted by creator

Hmmm there seems to be a vscode in my vim.

Wait really? Shit I’m like 1 year into learning vim. What editor should I switch to that will magically make me a good coder?

My app is very early stages, but it already supports web, iOS and Mac. Android will be launching in a couple weeks, and hopefully Linux not too long after that. My goal is to build a truly cross platform lemmy app and one that doesn’t feel like it’s designed primarily for small or large screen sizes but rather takes advantage of the space available. Offline support is already decent, and multi account imo is more intuitive then other lemmy clients.

• Try the web version blorpblorp.xyz
• Join TestFlight for iOS
• Download the Mac app

I use Apple products which are definitely more closed source. I would prefer open source but there are unfortunately more variables in play then just “is it open source”.

I’m using brave lol. As a web developer I really need to test the work I do on a chromium based browser. Brave seems to be the best chromium based browser that still supposed ad blocking after the whole manifest v3 thing.

So let me pose this question to you. As someone that needs to use Chromium for work, what’s the best Chromium based browser that still supports ad blocking?

I get that Firefox is better. Heck Tor is even better. But realistically what is something I can actually use to get real work done?

Edit: ok I read the article. That is kinda bad. So please find me a chromium based alternative that I can use for work

I don’t use Photon, but I glanced at the source code and it looks like they are also using Tanstack Virtual, which my Lemmy client uses. My app is in beta an doesn’t have many users, but I think I solved this feed issue.

You need to do a few things:

1. On scroll, save the first item being rendered in the virtual list + the offset of that item from the top (offset can be negative or positive)
2. Pause the virtualization when the list is no longer visible (use IntersectionObserver)
3. When the user returns to the list, reenable virtualization while simultaneously recalculating initalOffset to be passed to the virtual list.

You have to recalculate initalOffset when returning to the list, NOT when you are scrolling through the list. If you try to calculate it while scrolling the feed, you will drift a few posts upwards/downwards. Using initial item + offset yields a much more stable result.

It’s all pretty messy, but take a look at my spaghetti code.

wtf did I just watch

That’s what I do