685 karma · joined September 19, 2013
A consultant is someone who borrows your watch, tells you the time, and keeps the watch.
Worse, I'm still using LastPass -- but migrating over to Chrome password storage as it syncs between phone and laptop. LastPass doesn't give you the option to not use it for passkeys. It might be the thing that causes me to finish the migration away from it.
Still, it is amazing that it works at all!
(a) The location of the user who uses this IP at the moment?
(b) The location of the device that is assigned this global IP?
(c) The location of the switch/router at the ISP that is directly connected to the device with the IP?
(d) The headquarters location of the organization that registered the IP block.
(e) Some other location we can't describe.
(f) One of the other answers, but at some time in the past.
These are not all the same location, and not necessarily the same country. Think about people using phones, on airplanes, at sea, in the desert using starlink, corporations using internal networks to get to an ISP POP in another country.
I believe that the Slack API (if your company uses Slack) can be persuaded to give you the list of deactivated accounts. Then you just check this into git (on a daily basis), and you are done.
And, of course, in this AI Agentic world, you can probably ask your HR bot about the recent layoffs and get the information even more easily!
Costco (https://www.costco.com/p/-/kirkland-signature-extra-strength...) sells Vitamin D at less than half that price. On Amazon, the two pack of those is even cheaper.
Just an observation.
The moral of the story is to find someone who works at Comcast who has Engineer in their job title and reach out directly. Linkedin is your friend here.
In the case of 63, reading out value at offset 1, requires two reads as it need 1 bit from the first byte, then 56 bits from the next 7 bytes and finally 6 bits from the 9th byte. Nine bytes cannot be loaded in a single u64 load.
I did find an email from Cloudflare in April 2011 (seven months after CF started to offer services) which was a response to a support request. I guess that things have changed in the intervening years so that the original link to keep track of my support request no longer works!!
I'll give them a break on this!
Have other free users also received this email?
Good job on this and pretty cool.
This was probably at the end of the 70s while I was a Maths undergrad at Cambridge.
If this really was the first api request made by the app, and it has a serious vulnerability, then the omens are not great for the rest of the api calls either.
It was never clear to me (at least I don't recall it being clear) why the heating elements failed. It could be from someone sticking a hard tool into the toaster when trying to remove a small item (and breaking the element). It might be that a piece of bread gets stuck to a portion of the element and catches fire at that point -- maybe that weakens the element at that point. This was, of course, long before toasters got electronics in them!
This is the driver for the Lua Nodemcu for the ESP8266: https://nodemcu.readthedocs.io/en/dev/modules/switec/
Traceroute to news.ycombinator.com:
3 96.108.68.141 (po-200-xar01.maynard.ma.boston.comcast.net) 12.105ms 11.724ms 11.931ms
4 96.108.68.141 (po-200-xar01.maynard.ma.boston.comcast.net) 13.011ms 10.727ms 19.861ms
5 162.151.52.34 (be-501-ar01.needham.ma.boston.comcast.net) 13.988ms 14.721ms 12.921ms
6 162.151.52.34 (be-501-ar01.needham.ma.boston.comcast.net) 14.999ms 16.688ms 12.997ms
7 4.69.146.65 (ae0.11.bar1.SanDiego1.net.lumen.tech) 76.044ms 79.624ms 78.017ms
8 4.69.146.65 (ae0.11.bar1.SanDiego1.net.lumen.tech) 83.962ms 108.675ms 78.987ms
9 \* \* \*
I can conclude that the server is probably on the west coast -- maybe San Diego.I recall using this during a sales pitch by some IP Geolocation company that were very proud of their technology. The example that they used, they claimed was in Morristown, NJ. A quick traceroute (from Massachusetts) revealed that the IP was somewhere in the UK as the last hop was close to Heathrow Airport. We did not purchase their solution!
More likely is that whenever they print OCR'able numbers / barcode/ whatever, they assume that a person is going to return it -- and the special case of 'we only get returned letters when the delivery has failed and nobody has opened the envelope' escaped the testing.
My solution was to use a filtering DNS that always returns no AAAA records for domains ending in google.com. This works great and essentially solves the problems. I have to do the same for various netflix domains as well.
I'm dreading having to switch over to native IPv6 -- I don't even know how many /64s will be allocated to me (and how stable they will be).
I'm going to succeed in having my entire 40+ year career in software without ever having had to manage another person. I'm fortunate enough to have had a number of managers who can recognize my strong (and weak) points and then use me in the most effective manner.
I've made changes on personal projects that I thought were simple, and yet broke stuff. But CrowdStrike is a multi-billion dollar company -- how can it be possible to have such a broken process. Their RCA document was interesting, but didn't cover any of the interesting issues. It seems that they don't know about the 5 Whys process (https://en.wikipedia.org/wiki/Five_whys) or decided that those answers were so embarrassing that they had to omit them.