Why on earth would Amazon allow whole-seller accounts to edit other peoples listings?
That just seems like a recipe for disaster, as seen here...
440 karma · joined March 28, 2017
That just seems like a recipe for disaster, as seen here...
> to make sure we could connect successfully
So the 'solution' to the problem is to create more problems, in node of all things. 'Use the right tool for the job.' Node is not that tool.
Further, how would you know you connected successfully if you made the server?
I'd trust the actual honest to god FTP servers out there (vsftp for example) over a not-built-specifically language module. vsftp has seen some shady stuff and is actually updated; that node module... not so much.
If you really want to test a connection thing, then this is the wrong way to do it; what about network failures, no host connection, endpoint server not responding, firewall rejects? Making a 'test' like this is not only a bad thing, but it's misdirecting from the real problem of 'write good tests.'
Step use SWF under the hood. When step was released, it still peeves me that you couldn't edit a function without deleting and recreating; even then, deleting took hours...
The browser is now overriding the OS level resolver, and pointing to the Cloudflare stuff.
This feels like Microsoft telemetry; I have no choice but to just shut it down and not use it.
In another life I did PHP shells. PHP (which has a weird relationship with JIT) had so many ways to use eval, without actually typing eval. One of the weird ways that was only removed in PHP 7 was the preg_replace function, with the e flag; which evals any php expression, outside the scope of the function.
My point is that if there is eval used in code; it either is meant for temporary use (because devs are lazy,) or the code needs to be done differently to support the desired outcome.
Why? Because each time they introduce something, they end up at the controls.
What if, if, their internal network is breached; or an unhappy employee is at the wheel? Not only would it be possible for them to use everything at their disposal, but they can start to sell user data; internal ports exposed.
Considering bugs are a fact of life for developers; how long will it be until there is a big hole? Heartbleed was one; what's the next?
Once a measurement is used for success, it stops being a good measurement.
Javascript, namely node, has a metric ton of libraries, and you think, iseven/isodd/... so god knows how many libraries are out there, not actual projects.
I will say, that their metric about growth of the number of contributors is a much better metric for 'best language.'
Those who actually make their own encryption libraries know their stuff, and have been in the space for years.
You should never, ever, roll your own encryption.
If it's a requirement, then change your damn requirements, because just like consensus; it is not easy to get right, and the pros make mistakes.
I'd bet that the same thing would happen if Microsoft, Apple, Google, or any other number of big tech firms decided to 'branch out.'
For starters; he had to call a general, city line, to get the public (non-local, 10 digit) line for the dispatchers, so he could actually call the '911' (three digit) line.
From what I gather, The area code itself is a give-away.
If you say 'what about people who just moved, but haven't changed their number yet,' then I'd say that the dispatchers (should) be able to see if it was a honest 911 (three digit), or the public line (10 digit.)
That they are, but only to say 'I created 50k jobs; re-elect me.'
To me, that's not much as an incentive but a plea for holding power. At the end of the day the public servants have limited time to make things happen. Companies don't.
If you go buy a new car, you haggle with the dealer. That's just something you do. You have total control to walk out (you have more power,) and you wanted the new car (initiated.)
Yes the dealer will be upset that you haggled, but they still get paid commission, even at a reduced rate. You go home happy, because you got what you wanted, the dealer is happy to have gotten something over their competitor (and the money doesn't hurt); win-win.
That doesn't sound like what they were getting at.
Sounded to me like they were attacking Amazon because they were playing the field.
Rather than punish Amazon, punish the public servants who thought a large tax break for years, or real estate deals, would really be big enough to draw the company in.
What Amazon did was playing the field; why not get a bonus for letting others compete; rather than taking nothing because it was already decided?
A lot of malicious links are just base64'ed to another redirect service; to another base64'ed address (continue as long as your head can keep up.)
As a system admin myself; if user applications started overriding the DHCP DNS that I give them, not only could intranet sites be broken, but I'd start having fights with users about it.
Edit: Rather, not overriding but querying the DoH instead of the provisioned DHCP DNS. I'm no expert in DoH, or how any of that works under the hood.
Further, when/if browsers turn on DoH by default, then I can't really fight users, because they did nothing wrong but use a browser. Suddenly, I can't support a browser or two because of it.
DNS caching by the application is fine, because they made the request to the OS, and got the response. That being said, TTL might be violated by that, since the record has a TTL, and whatever the application cache TTL is.
If a browser starts (purposefully) subverting the hosts file or not adhering to resolv addresses, then we've got a bigger problem.
Think, a fat client resolving an address differently than a browser; then that's all sort of Pandora's Box.
> If they’re willing to convert all their customers to ESNI at once
Why does it seem like this is over-engineering at it's finest? Not only are CDNs now part of the problem/solution space, but they are now dictating.
It is now that much harder to diagnose issues when they do crop up, instead of checking ping or nslookup. Now, you've got to see if the DNS-over-HTTPS/The DNS record itself/Host/client/any number of other steps is broken.
We've completely removed the ability for a poweruser to diagnose before calling their resident IT professional.
Executives say what they need to, to make the shareholders happy; and the marketers need to clean up the mess, after the shareholders stopped paying attention.
On bitly, you can add a + to the end, to get to the stats page for that link; it also gives the destination.
On the goo.gl links, add .info to the end.
Except what part is that? Having to download 4 or 5 projects to build, compile, and run 'basic' pages is too much bloat; not to mention the dependency hell.
It more and more seems to me like node was made 'because we can' instead of providing something. This can be seen with all of the cruft required; a lot made as an after-thought.
Package manager, npm; which itself has proven that... it wasn't designed too well. The reliance of it creates the cruft. Add in the fact that a web server shouldn't be event driven. I (personally) haven't seen any other language do an event-driven web; and I'd say, for good reason (callback hell.)
Javascript itself is okay because it's a requirement today for web pages to the average joe. However, if the Javascript foundation is merging; it'll their motto to use it (Node.)
They faked the data on what it could handle; and with things such as aircraft, lives depend on that data.
This can't end well anyway; javascript itself is a client side language, and node, using the same language, made it server side.
That's been my whole gripe with Node in the first place, because you're taking a tool (square,) and force-fitting it into a round hole.
On top of that, they record the logins from deleted accounts... still adding to the metadata they have on you, even after you delete.
My point was that working anywhere, even one that is on the level of 'my first job,' is better than ranting on the internet.
If something breaks, I know its my fault, and using the knowledge gained by setting it up, I should have a pretty good idea where to start.
Never stop learning.