Some examples of coded fields that may be known to be ascii: order name, department code, business title, cost center, location id, preferred language, account type…
Disk hardware may be faster relative to RAM, but if you're using typical serverless PaaS offerings to run a hosted application at modest operational scale, it's a heck of a lot cheaper to get a node with "normal" RAM and CPU, than it is to get decent IOPS. If you're a big iron company with big iron problems, you may need to think in different scaling terms, but for the SaaS hoi polloi the economics of hosting have somewhat preserved traditional notions of performance.
I think it's worth differentiating between personal projects done to learn or just for interest, and those that are trying to accomplish something. If I do a project for myself to try things out and learn something I don't feel any pressure to finish the project. Once I've learned something or had some fun, who cares if it's "finished" or if anyone else will use it. On the other hand, sometimes I'll pick up something interesting that helps a friend or family member, or just that I need for myself, and there I'm pretty careful about scope. If I can't finish it in a couple weekends I'll look for the closest commercial solution unless it's a major once-in-a-decade passion project.
Definitely agree with this. Most of my personal projects are just to prove that something can be done. Once I know it's possible then the fun and interest is no longer there. I'm not trying to product a "finished" product or something that is polished enough for someone else to use.
I think this is an excellent point. For those projects that are needed by myself or others I prefer to look at the closest commercial solution first rather than last too see if I might spend more time than it's worth. Or to see if I might be able to sell my own solution to more than the target client (myself or others).
As someone with an English "bottom" as in bottom-lands surname, I appreciate the deliberate silliness of "Longbottom" while leaning into a very traditional British sounding name.
FIDO2 wouldn't have helped the customers' accounts since valid session tokens were obtained. However, hardware tokens for the Okta customer service accounts may have blocked the threat actor's access depending on the (undisclosed) method of attack.
But it also seems likely that companies will decide to take advantage of the reduced liability (especially now it's confirmed and not just theorized) and investors will just price in the risk difference.
In such a situation, honest companies will get hurt and dishonest companies will get helped. How is this good for the ecosystem? Reminds me of crypto ICOs.
One benefit of regex that isn't mentioned in the article is that you can expect it to be available, at least the basics, in pretty much any programming, scripting, or even querying environment.
Snowman didn't work for me, but the other characters I tried did. I had some trouble with "therefore" because there were a lot of virtually identical symbols, but I can't blame it for that.
It mentions not all characters are in the the database.
Thanks for sharing from a recent IRA pilot! I'm surprised they didn't do this as a CAT III ILS. A DA of 250' with Rudolph leaves a lot of margin for Santa to get snowed in.
