James Moberg

@reincdr @fastly @DigitalElement @Cloudflare Too costly compared to what we were able to get from Fastly. We were previously with Edgio and another service that I can't recall at the moment, but they both went bankrupt.

@gamesover @fastly @DigitalElement I am a bit curious. Have you tried @Cloudflare? They use our IP geolocation data. You get our data via requests header.

.@fastly recently changed their on-prem WAF deployments to use @DigitalElement for geolocation. I inquired. Their annual contracts are $20k minimum. #yikes We're leveraging a $20/mo Basic plan from IPAPI.is. Free plan: 1k/day Max cost w/DB included: $200/mo

@reincdr @fastly @DigitalElement I like the extra metadata available (VPN, Tor, mobile, hosting, etc.) We've rolled out on application-based captcha using these signals and it's drastically reduced abuse. (We auto-whitelist known + beneficial third-party IP ranges.)

@gamesover @fastly @DigitalElement If you are comfortable with country and ASN data, you can bring that cost down to $0 with IPinfo Lite. We offer unlimited requests for the API, and you can also use the offline database. ipinfo.io/lite

Also of note, the website uses WordPress. I'm not knocking the tech, but I've found that most WordPress website owners don't really know what they are doing and are overly reliant on third-party plugins that they didn't author or understand.

I previously reported this issue once within the last year or so and received the same treatment. Hopefully this additional detail will enable them to identify the issue, take responsibility and add some steps to ensure their offerings remain up-to-date in the future.

I received an email from a software provider regarding a 3/13 update. I downloaded directly from their official website. It was the older version from 2/3. :( I reported the issue. They responded that I was "doing it wrong" & blamed my firewall & antivirus. ???

The fix, if not using AWS CLI or SDK, is to proactively invalidate the cache prior to announcing any new releases. #tooEasy AWS Console: CloudFront ➤ Your Distribution ➤ Invalidations ➤ Create Invalidation BOTTOM LINE: Don't globally announce & then serve stale content.

The stake holder that I reported the issue to is a one-man show and claims I'm literally the only person who reported this. I'm guessing his audience may either not notice, not care enough to report or avoid using the official website for new releases.

I just used Globalping by @jsDelivr to retrieve HTTP headers from multiple providers to confirm if a @cloudfront file is "fresh" when accessed from multiple nodes. This approach is a huge timesaver and will quickly identify issues when software providers have cache invalidations that fail or never happen.

I receive lots of spoofed calls via my @Ooma VOIP line. They can't (or won't) fix it and it's pretty bad (ie, 4-12 calls per day). I asked @Copilot if it could jump in, converse with the abusive caller to waste they time. It refused. I asked @grok and... game on! #letsGo

I will occasionally use @Copilot when explicitly reviewing MSSQL, but it was unusable today. I only got the warning message only after attempting to submit the prompt. Does this happen often?

Most of the duration was due to manually reviewing the next steps and clicking "yes" to continue.

I used @claudeai on my laptop to fix the spelling of an argument for a third-party dotNET executable. The vendor's help contradicted usage. No recompilation required. The "patch" is the same direct modification that I would have performed in the 80's using my Commodore 64.

I've identified another javascript library from 2005 that we used on some #ColdFusion web applications. The site & documentation were long gone, but archive․org unearthed them. Here's the modernized version of "Fade Anything Technique" (FAT). Enjoy! github.com/JamoCA/fade-an…

I was using a jQuery plugin from 2012 to extend normal dropdown (select) elements to be searchable, but it had a couple of issues and was no longer maintained. Here is the modernized version of "searchabledropdown". Enjoy! github.com/JamoCA/searcha…

I guess I tweeted too soon. This morning, it's back to using Metric rather than Imperial. Apparently it's inconsistent. The weather results may be based on the source data provider rather than my preferences. I don't even have Bing weather notifications enabled.

Up until I tweeted, local notification units in California were consistently Celsius & km. After tweeting, the units appear to be fixed. Coincidence?

My iOS "Language & Region" settings are correct, but your app chooses to ignore it.

Hey @bing is there an option the in iOS app to set the unit for temperature? I reside in the US and you correctly identify the city, but notifications display the units using Celsius & Kilometres. Where's the options for Fahrenheit & Miles?