You're quite welcome and I'm glad I was able to help for a change.Thanks for that.... I set it to True and now the site info regarding upcoming events seems to be correct for my time zone.
You're quite welcome and I'm glad I was able to help for a change.Thanks for that.... I set it to True and now the site info regarding upcoming events seems to be correct for my time zone.
Actually I do use a fork of pale moon browser (Lun3r browser) because the last working pale moon browser to support xp is quite old. Thank you.Agree, easily customizable and you know it doesn't do anything behind your back. Maybe try Pale Moon browser - might be less resource-intensive than others.
You're welcome! I use Pale Moon on Linux because I want to keep trackers like YouTube seperate from other things I do.Actually I do use a fork of pale moon browser (Lun3r browser) because the last working pale moon browser to support xp is quite old. Thank you.
Dang .... I was hoping that was the issues so we need to keep trying. Are you using Mypal68 or FF? The reason I ask is because FF uses https://location.services.mozilla.com/v1/geolocate?key=%MOZILLA_API_KEY% for geo location where foedor has geo.wifi.uri;data:text/plain, so it goes nowhere. You could also experiment with https://beacondb.net/v1/geolocate ... which reminds me you could try toggling beacon.enabled to true ans see if that helps. I keep it at false. I hope we can get to the bottom of this for you.Seems like I spoke too soon. After setting "geo.enabled" to True, and checking a web site, the reporting was accurate. But the next time I loaded the same page (a day later) the reported time and countdown for upcoming events is off by an hour again.![]()