The worm does the lobotomy

They sell guards through a 3rd party. They don’t advertise it well, so it took me some time to find them last time.

~/

Pretty sure Uncle Ben said “with great power comes no responsibility, blame the democrats”

I know you’re incredibly busy. If you write 1 sentence of feedback for my Lemmy client I’ll double my contribution again.
https://blorpblorp.xyz/

Just doubled my monthly contribution! Thanks for the reminder.

Yes, it is May

I just completely rewrote my config but there are like 3 more plugins in there I wanna try now.

How much more complicated is NixOS compared to a neovim setup? On paper I love the idea.

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