Edit: Filtering appears to be fully broken for me, with "Error: Could not retrieve items. Please contact support." (Originally thought it was just filtering on sockets with a '/').
It may make sense to run an hourly or daily job to collect data from the API and then implement the filters exclusively within your back-end. This pattern can work well with rate-limited APIs and a dataset that changes fairly slowly. There's some risk that an item shown will already be sold (user would click back and try another).
When it comes to filtering, there's enough unique selections a user can make that, if you're letting the eBay API handle filtering for you, will cause far too many cache misses.
At a previous job I considered a system that would use synchronous API calls to the backend API until it went down (or we got rate limited). When the backend was unavailable we'd switch to filtering in our service using the data we'd previously cached.
I.E. if a cached query asked for (cpu>=3.0Ghz, cores>=2) we can also answer (cores>=4) by filtering the previous result. This wouldnt be able to find any CPUs with less than 3Ghz, unless it there were other cached responses. This works well when a "best effort" response is desirable, even when it's incomplete.
That's a very good idea, thanks! I think I'll have to do exactly that. Maybe in the fallback scenario, I can display a warning that data might be incomplete.
Curious whether you've tried with the new (non-PPA) repo directly from Mozilla as of v122 [1]. I think the old PPA was also Mozilla, so I don't know what may have changed aside from being more publicly acknowledged. Might be worth a try?
I don't have an Ubuntu VM at-hand but on Debian bookworm it installed fine, and (after tweaking one line in profiles.ini to point to my old ESR profile) it loaded and played Widevine-protected videos without any issues.
There are instances in other articles, including the latest one from December. It's a WordPress site and the links are baked into the HTML so yes, it's likely running a compromised plugin.
I do not mean to invalidate your experience, but generally speaking it seems like both no and yes to sugar rush/sugar crash.
"Double-blind trials have shown no difference in behavior between children given sugar-full or sugar-free diets, even in studies specifically looking at children with attention deficit hyperactivity disorder or those considered sensitive to sugar. A 2019 meta-analysis found no positive effect of sugar consumption on mood but did find an association with lower alertness and increased fatigue within an hour of consumption, known as a sugar crash." [0] [1] (emphasis mine)
I prefer iagree@reallymymail.com, much more convincing - Mailinator alias domain, for those cases where you get "Thanks! We've sent the details to your email." If they block the submission for it, I know that we can't ever do business.
My understanding was more that Coke Zero was originally targeted at men, who apparently viewed "diet" sodas as being for women. [0]
"We're positioning Coke Zero as a defender and celebrator of guy enjoyment."
It doesn't hurt that it's a chance to reformulate without people complaining about the change like "New Coke" (which was allegedly based on the Diet Coke of the time[1]) and so the Zero branding has likely expanded across the Coca-Cola lineup and other brands to expand that reach and introduce changes - and incidentally give them a chance to mess with their agreements with bottlers the same way as when they switched to high-fructose corn syrup [2] [3].
I don't find that weird - if I'm going to be drinking a coke (of whatever flavor), caffeine-free Diet Coke is my preference over regular/Zero. It is a different formula, even if it only comes down to the blend of sweeteners. Obviously I don't know the actual formulas, but each has a different blend of sweeteners based on the labels, and now I've added "The Real Thing" to my reading list. Different people prefer different blends, like the other commenters who prefer monkfruit, erythritol or stevia.
