9 ms·

No, it does not. An uncaught error where you don't catch and gracefully handle errors in your promises is not the users' fault. It's sloppy workmanship.

jdbernard 4y ago
I'm sure they'd be happy to give you a refund. :)
- jason-phillips 4y ago
  The point is not that one makes available one's site for free. The point is that the quality of the work is sloppy, price of said service notwithstanding. There are many other ways to approximate a client's geolocation so as to prevent displaying an embarrassing error where one did not first check whether the object's property was truthy or not. Justifying terrible UX by saying, "it's free," is a terrible strategy, tbh. Free shit is still shit.
  - thedragonline 4y ago
    Uh, then don't use it? Problem solved methinks.
  - mbostleman 4y ago
    But, all moral posturing notwithstanding, is it not also true that if the OP just gets a browser or a browser version or a browser configuration that supports geolocation that they will be back in business?
  - shadowgovt 4y ago
    It's not just that the key isn't populated; it's that it's undefined. FWIW, my browser (Chrome) works on the site even if I choose not to share geolocation; I assume because the API is populated even if it then refrains from sharing. Your point isn't quite wrong but it also isn't quite right; geolocation is supported by every browser listed on Mozilla's documentation (https://developer.mozilla.org/en-US/docs/Web/API/Navigator/geolocation https://developer.mozilla.org/en-US/docs/Web/API/Navigator/g...) so if a browser isn't at least stubbing out that API these days, it's not w3c-compliant, and non-w3c-compliant browsers will sometimes just break on some pages. It is, of course, still incumbent on the developer to go that extra mile if they want to catch that last 1% of users, but users of exotic browsers get an exotic experience also.
    - jason-phillips 4y ago
      None of the browsers on my iPhone will render this site, W3C compliant or not. In any event, I would never tell my users that it's their fault that my app didn't check the truthiness of the object's property. Seems particularly hostile to one's users and customers, free product or not.
      - shadowgovt 4y ago
        Ever written a website that checks whether `window` is defined? Technically, we should be checking everything. Practically, nobody does.
      - deleted 4y ago
        [deleted]
      - 8note 4y ago
        That's a monopoly problem, no? Apple doesn't actually let you use different browsers. You should try it on an android phone?
      - robocat 4y ago
        FYI: renders on iPad with iPadOS 16.1 (iPad so no GPS). Either way, you are coming across to me as somewhat petulant - you could be right but politeness has its place too.
        B1FF_PSUVM 4y ago
        > (iPad so no GPS) That's WiFi only iPads - the iPads with 3G/4G comms used to have GPS, at least the 2011 iPad2 did. Probably still do, my current cheap Android tablet with 4G does.
      - michaelmrose 4y ago
        If you aren't paying the bills you aren't a customer. You are a recipient of a gift who is lecturing the creator on workmanship.
      - teh_klev 4y ago
  - jorgesborges 4y ago
    Here’s a blog post by the author of the app for more insight into the amount of work and details put into it. https://james.darpinian.com/blog/how-see-a-satellite-tonight-works https://james.darpinian.com/blog/how-see-a-satellite-tonight...
- ipaddr 4y ago
  On my time which is worth $/per hour? That will be the day.
modeless 4y ago
If you get this error, you intentionally broke your browser, or are using a browser which doesn't support standard, essential functionality. This is not the same thing as declining or blocking geolocation permission, which is supported and does not cause errors. This specific error means you deleted the standard functions that implement the geolocation API, which is a completely different thing. That's fine too, you're welcome to browse the web with a broken configuration, but you have to realize that it will break things. You're not automatically entitled to request that every site support your broken configuration. It should also be noted that browsing with a non-default configuration like this makes you an easy target for fingerprinting. Note that the site absolutely requires some form of geolocation to work at all. Satellite viewing times are location specific and without a precise location the site can't show you anything useful.
- jason-phillips 4y ago
  > This specific error means you deleted the standard functions that implement the geolocation API That's a rather flimsy straw man. I did no such thing. > You're not automatically entitled to request that every site support your broken configuration. Goodness, now I'm entitled. I did no such thing; I just said that blaming your users for your sloppy coding is a terrible strategy.
  - modeless 4y ago
    You say you're using iOS Safari. I'm interested to know how you were able to configure it to delete navigator.geolocation, apparently without realizing what you were doing. I don't plan to support a broken configuration like that, but if you can figure out the cause then I could file a WebKit bug on your behalf.
    - kortilla 4y ago
      Why would it be on OP’s behalf? If it’s just a configuration that WebKit supports it’s either violating the standard or you’re not handling it correctly on your site. It has nothing to do with the OP at that point.
david422 4y ago
Maybe you should email the site and let them know instead of complaining on some random forum?

jdbernard 4y ago

I'm sure they'd be happy to give you a refund. :)

jason-phillips 4y ago
The point is not that one makes available one's site for free. The point is that the quality of the work is sloppy, price of said service notwithstanding. There are many other ways to approximate a client's geolocation so as to prevent displaying an embarrassing error where one did not first check whether the object's property was truthy or not. Justifying terrible UX by saying, "it's free," is a terrible strategy, tbh. Free shit is still shit.
- thedragonline 4y ago
  Uh, then don't use it? Problem solved methinks.
- mbostleman 4y ago
  But, all moral posturing notwithstanding, is it not also true that if the OP just gets a browser or a browser version or a browser configuration that supports geolocation that they will be back in business?
- shadowgovt 4y ago
  It's not just that the key isn't populated; it's that it's undefined. FWIW, my browser (Chrome) works on the site even if I choose not to share geolocation; I assume because the API is populated even if it then refrains from sharing. Your point isn't quite wrong but it also isn't quite right; geolocation is supported by every browser listed on Mozilla's documentation (https://developer.mozilla.org/en-US/docs/Web/API/Navigator/geolocation https://developer.mozilla.org/en-US/docs/Web/API/Navigator/g...) so if a browser isn't at least stubbing out that API these days, it's not w3c-compliant, and non-w3c-compliant browsers will sometimes just break on some pages. It is, of course, still incumbent on the developer to go that extra mile if they want to catch that last 1% of users, but users of exotic browsers get an exotic experience also.
  - jason-phillips 4y ago
    None of the browsers on my iPhone will render this site, W3C compliant or not. In any event, I would never tell my users that it's their fault that my app didn't check the truthiness of the object's property. Seems particularly hostile to one's users and customers, free product or not.
    - shadowgovt 4y ago
      Ever written a website that checks whether `window` is defined? Technically, we should be checking everything. Practically, nobody does.
    - deleted 4y ago
      [deleted]
    - 8note 4y ago
      That's a monopoly problem, no? Apple doesn't actually let you use different browsers. You should try it on an android phone?
    - robocat 4y ago
      FYI: renders on iPad with iPadOS 16.1 (iPad so no GPS). Either way, you are coming across to me as somewhat petulant - you could be right but politeness has its place too.
      - B1FF_PSUVM 4y ago
        > (iPad so no GPS) That's WiFi only iPads - the iPads with 3G/4G comms used to have GPS, at least the 2011 iPad2 did. Probably still do, my current cheap Android tablet with 4G does.
    - michaelmrose 4y ago
      If you aren't paying the bills you aren't a customer. You are a recipient of a gift who is lecturing the creator on workmanship.
    - teh_klev 4y ago
- jorgesborges 4y ago
  Here’s a blog post by the author of the app for more insight into the amount of work and details put into it. https://james.darpinian.com/blog/how-see-a-satellite-tonight-works https://james.darpinian.com/blog/how-see-a-satellite-tonight...
ipaddr 4y ago
On my time which is worth $/per hour? That will be the day.

modeless 4y ago

If you get this error, you intentionally broke your browser, or are using a browser which doesn't support standard, essential functionality. This is not the same thing as declining or blocking geolocation permission, which is supported and does not cause errors. This specific error means you deleted the standard functions that implement the geolocation API, which is a completely different thing. That's fine too, you're welcome to browse the web with a broken configuration, but you have to realize that it will break things. You're not automatically entitled to request that every site support your broken configuration. It should also be noted that browsing with a non-default configuration like this makes you an easy target for fingerprinting. Note that the site absolutely requires some form of geolocation to work at all. Satellite viewing times are location specific and without a precise location the site can't show you anything useful.

jason-phillips 4y ago
> This specific error means you deleted the standard functions that implement the geolocation API That's a rather flimsy straw man. I did no such thing. > You're not automatically entitled to request that every site support your broken configuration. Goodness, now I'm entitled. I did no such thing; I just said that blaming your users for your sloppy coding is a terrible strategy.
- modeless 4y ago
  You say you're using iOS Safari. I'm interested to know how you were able to configure it to delete navigator.geolocation, apparently without realizing what you were doing. I don't plan to support a broken configuration like that, but if you can figure out the cause then I could file a WebKit bug on your behalf.
  - kortilla 4y ago
    Why would it be on OP’s behalf? If it’s just a configuration that WebKit supports it’s either violating the standard or you’re not handling it correctly on your site. It has nothing to do with the OP at that point.

david422 4y ago

Maybe you should email the site and let them know instead of complaining on some random forum?