Yep, This is taken straight from Facebooks advertisements circa 2018, maybe still today.
RecallMadness
Put each character in a spans with random classes, intersperse other random characters all over the place also with random classes, then make the unwanted characters hidden.
Bonus points if you use css to shuffle the order of letters too.
Accessibility? Pffffft.
Could a hypothetical attacker not just get you to visit a webpage, or an image embedded in another, or even a speculatively loaded URL by your browser. Then from the v6 address of the connection, directly attack that address hoping for a misconfiguration of your router (which is probable, as most of them are in the dumbest ways)
Vs v4, where the attacker just sees either your routers IP address (and then has to hope the router has a vulnerability or a port forward) or increasingly gets the IP address of the CGNAT block which might have another 1000 routers behind it.
Unless you’re aggressively rotating through your v6 address space, you’ve now given advertisers and data brokers a pretty accurate unique identifier of you. A much more prevalent “attack” vector.
I was maybe a little inebriated, and he was very rude.
He had to wait for the next train, and I had a sore jaw for a week. Mild inconveniences al round. I think everyone got what they deserved.
Threw a man’s belongings off a train because he was listening to music without headphones.
Worth it.
CGNAT is good. One more layer of obfuscation between me and the internet.
Sucks for those wanting to run services from home I guess.
If you still do the sizing (it’s not entirely wasted as it’s a reasonably effective tool to gauge understanding across the team), This can still be done without the artificial time boxing.
“How much work have we done in the last two weeks?” Just look at all the stories closed in the last two weeks. Easy.
“When will X be delivered?” Look at X and all its dependencies, add up all the points, and guesstimate the time equivalence.
Kanban isn’t a free for all, you still need structure and some planning. But you take most of that away from the do-ers and let them do what they do best… do.
They were first to market with a decent GPGPU toolkit (CUDA) which built them a pretty sizeable userbase.
Then when competitors caught up, they made it as hard as possible to transition away from their ecosystem.
Like Apple, but worse.
I guess they learned from their Gaming heyday that not controlling the abstraction layer (eg OpenGL, DirectX, etc) means they can’t do lock in.
While suing everyone else that makes shovel handles that work with your shovel heads.
Problem then is, You Still gotta buy a truck to buy and haul your 2nd motorcycle, your 3rd motorcycle, your dirt bike, and your track bike.
Alternate headline:
Companies accept money for a thing that will happen anyway, and will be unable to prove if they say no.
GenAi is unfortunately here, and the technocracy wants you to want it so they can farm you for more and more intimate data to leverage and enforce their technocracy. And the only way they’re going to do it is by keeping the press positive, and feed it more and more data in the hopes it fixes things.
I used to love ‘the cloud’. Rather, a specific slice of it.
I worked almost exclusively on AppEngine, it was simple. You uploaded a zip of your code to appengine and it ran it at near infinite scale. They gave you a queue, a database, a volatile cache, and some other gizmos. It was so simple you’d struggle to fuck it up really.
It was easy, it was simple, and it worked for my clients who had 10 DAU, and my clients who had 5 million DAU. Costs scaled nearly linearly, and for my hobby projects that had 0 DAU, the costs were comparable.
Then something happened and it slowly became complicated. The rest of the GCP cloud crept in and after spending a term with a client who didn’t use “the cloud” I came back to it and had to relearn nearly everything.
Pretty much all of the companies I’ve worked for could be run on early AppEngine. Nobody has needed anything more than it, and I’m confident the only reason they had more was because tech is like water. You need to put it in a bucket or it goes everywhere.
Give me my AppEngine back. It allowed me to focus on my (or my clients) problems. Not the ones that come with the platform.