If each user is caching it, that would be even more resource intensive on the API than if the app was storing it somewhere and serving it to users. It would mean each time that a user clicks on another user’s profile for the first time, the app would need to pull all of their comments in order to calculate their score. If it were cached on servers at the app level, then you and I requesting the same user profile in a short period would only require api requests to pull all of that user’s comments once.
Storing it centrally means one repository making calls for scores. Storing at the app level means there are N repositories for N apps making calls. Storing it at the install level for each app instance means that you’d have astronomical amount of calls to the API to calculate this number. It would be incredibly expensive to do it that way and could be a behavior that may slow all API response to a crawl.
I would too, but it would undoubtedly be much more resource intensive and so probably not feasible for a free app.
And even if they charged users for it, doing it at the app level would be challenging and inefficient. It’s the kind of thing that really has to be cached, so voyager and any other app that wants the feature would have to independently calculate, store, and recalculate for each lemmy user periodically. Having multiple apps doing this would put more strain on the public api than storing it centrally, and that unwanted strain would most likely cause conflict from the devs that wanted the karma score removed to begin with.
Cook also leaned on Jony Ives for innovation, and he’s more creative with aesthetics than he is with functionality. The Apple Watch would have been even more innovative if Jobs were alive to shepherd it.
There are a few bits wrong here. First off, the Midwest is not simply a massive wide open cattle ranching area with little else around. That’s really the Great Plains area, which is partially in the Midwest but also partially in the West and Southwest. The Midwest is not mostly made up of ranchers or farmers. There are definitely some in various parts, but other parts have none at all.
Ohio, Illinois, Indiana, Missouri, Michigan, Wisconsin, and Minnesota are all part of the Midwest, and your summary doesn’t really describe them well at all. I think you may be doing what I see a lot of coastal Americans do which is to confuse the Midwest with the West or the Southwest because the names are much less intuitive than they seem. These terms rose to prominence in the 19th century before “manifest destiny” colonized the entire continent, so they’re all incredibly East coast-centric. The Midwest is in the mideast, the South is in the southeast, the Southwest is in the south, and the West is the whole western half of the country.
And while cola for breakfast might seem a bit off even to most Americans, it’s not at all uncommon in the Midwest, but what’s weird is that it’s Pepsi in this ad because almost all prefer coke in the Midwest. When I moved out of the Midwest, it took me a while to break the disgusting coke for breakfast habit, but it definitely rings true to me to be characteristic of a Midwest breakfast.
Also, this looks like a regular sized gas station anywhere in the central US. It’s definitely not an area for truckers to fill up their big rigs because there is clearly unleaded at those pumps.
And to back it all up, here is the location map for Casey’s (that made this ad) where it’s clear that they are mostly in the Midwest states I mentioned as well as the Great Plains Midwest states of the Dakotas, Nebraska, and Kansas.
Bruh, as someone who spent over ten years in Texas and got out, you are lying to yourself. Everyone i know that still lives there wants to get out but can’t for one reason or another.
Assuming it’s the Xitter link, luckily for me, Xitter won’t allow me to log in (even directly after I change my password) or let me view much of anything, so no trauma for me today. Thanks Elon!
Ohhhh I had xbmc like a decade ago, before I gave up on the aye matey lifestyle, so I’ll probably choose that over plex as well. Thanks for the info. I’m looking up libreelec now, but I was just assuming it was some other hardware solution in my last comment.
If each user is caching it, that would be even more resource intensive on the API than if the app was storing it somewhere and serving it to users. It would mean each time that a user clicks on another user’s profile for the first time, the app would need to pull all of their comments in order to calculate their score. If it were cached on servers at the app level, then you and I requesting the same user profile in a short period would only require api requests to pull all of that user’s comments once.
Storing it centrally means one repository making calls for scores. Storing at the app level means there are N repositories for N apps making calls. Storing it at the install level for each app instance means that you’d have astronomical amount of calls to the API to calculate this number. It would be incredibly expensive to do it that way and could be a behavior that may slow all API response to a crawl.