71–80 of 110 posts
Earlier quoted context omitted.
But the observation is wrong or at a minimum, gussied up to make it look interesting. If you're calmly producing clickbait, it's still clickbait.
The headline that I wrote is a fact, pure and simple.
https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
Earlier quoted context omitted.
> possibility of any third party script getting blocked I'd say it's not unreasonable. You're giving your third parties the ability to break your business. Third party scripts are blocked or just fail to load all the time, APIs change suddenly, etc.
>Third party scripts are blocked or just fail to load all the time What's your strategy for dealing with jquery not getting loaded? >APIs change suddenly, etc. That's going to be an issue regardless of you check whether the script is loaded or not.
Host it on your own infrastructure so that it's the same reliability as your site itself?
Earlier quoted context omitted.
Why should I, the developer go out of my way to accommodate people going out of their way (by installing an adblocker/script blocker) to break my app? If you're going out of your way to create a non-standard execution environment, any breakages is on you.
Ad blockers should not be considered "non standard". Even if blockers do count as non-standard, random scripts not loading should not be capable of bringing down your site, and this should've been clear even before the npm left-pad debacle.
The website has every right to server you the content as they seem fit.
You are not entitled to an experience other than the one they are willing to provide.
The sourced ingredients are indeed regional. The menu is regional as well. The website is built on top of their mobile ordering platform. The mobile ordering platform requires your location to be able to route your order to the “correct” McDonald’s. This is done via requesting your location from Google or via location services within the mobile app. This platform is used by a lot of different QSRs. Or Quick Service R…
Earlier quoted context omitted.
And yet if you want your app to be listed on the iPhone App Store, it must be equally functional if the user denies location. So, I always do it, and have no problems, although sometimes it is slightly more annoying to use the app.
Almost any non-mapping application for location is just as well served by “zip-code”.
On the other hand, postal codes can sometimes apply to a handful of buildings, and sometimes can apply to entire cities, depending on the country and local area, so they can either be very unhelpful or almost as invasive as sharing your precise location.
Earlier quoted context omitted.
>Third party scripts are blocked or just fail to load all the time What's your strategy for dealing with jquery not getting loaded? >APIs change suddenly, etc. That's going to be an issue regardless of you check whether the script is loaded or not.
> What's your strategy for dealing with jquery not getting loaded? Host it on your own infrastructure so that it's the same reliability as your site itself?
The sourced ingredients are indeed regional. The menu is regional as well. The website is built on top of their mobile ordering platform. The mobile ordering platform requires your location to be able to route your order to the “correct” McDonald’s. This is done via requesting your location from Google or via location services within the mobile app. This platform is used by a lot of different QSRs. Or Quick Service R…
"Yeah but", do you need Google Maps do do the geolocation?
Earlier quoted context omitted.
Ad blockers should not be considered "non standard". Even if blockers do count as non-standard, random scripts not loading should not be capable of bringing down your site, and this should've been clear even before the npm left-pad debacle.
There are websites that look for ad-blockers and demand you turn them off. The website has every right to server you the content as they seem fit. You are not entitled to an experience other than the one they are willing to provide.
The only reason the site has so much control is that the browser makers gave it away. The browser makers should have retained much more control over the user experience. The site of course should have complete control over the words that appear on the site (and the ordering of the words of course) and some other things.
That was the fundamental mistake of the web. If people wanted to create a new internet protocol for serving user experiences over the net such that the user need not explicitly install any app, that would've been OK with me. The mistake was achieving that goal by extending the internet protocol that was quickly become society's most important way of distributing words (writings).
I've completely gotten off the subject of ad blockers.
Earlier quoted context omitted.
Almost any non-mapping application for location is just as well served by “zip-code”.
I’d rather not be picked up by Uber at the middle of whichever area shares my postal code, and I’d rather not get my food delivered there. On the other hand, postal codes can sometimes apply to a handful of buildings, and sometimes can apply to entire cities, depending on the country and local area, so they can either be very unhelpful or almost as invasive as sharing your precise location.
The sourced ingredients are indeed regional. The menu is regional as well. The website is built on top of their mobile ordering platform. The mobile ordering platform requires your location to be able to route your order to the “correct” McDonald’s. This is done via requesting your location from Google or via location services within the mobile app. This platform is used by a lot of different QSRs. Or Quick Service R…
Why can't you just select a particular McDonald's, set a (first-party, essential) cookie to say that address is "my restaurant" and then show nutrition facts/delivery destination with that location? You don't need to know which room in my house I'm sitting in to tell me how many calories are in a McChicken.