All API calls return "Your credentials are incorrect."
This seems to be a fairly regular issue for them, with intermittent errors such as this, but from my memory of using their services, this may be the longest event since a few years.
1,150 karma · joined March 4, 2017
This seems to be a fairly regular issue for them, with intermittent errors such as this, but from my memory of using their services, this may be the longest event since a few years.
It seems probable that this is one of the things that can be ruled out. I find it inconceivable that none of the thousands of brilliant heads in SpaceX never thought of this.
- They spoke, but were not heard
- They never felt like speaking
I think that advantage may have been real at one time, when FTP deploys were a thing. The myth loves on. Folks that chant this praise are often not be the same folks that have to maintain the webserver side of things, though.
Easy to deploy looks like this: ./foobar --port=80 > Listening on port 80, ready for traffic
That could be Go, could be Rust. But not PHP.
PHP webserver / application separation does bring some advantages - for example if you bring your application to a corrupted state or crash it, it will go and die. Recovery is, well "implied". But deployment wise, no.
It actually seems to be a LOT harder to run PHP that at first blush. Take this example: https://github.com/laravel/valet/issues/290
Turns out if you php-fpm app one Tuesday at 15:43 starts to write more than 4k to stderr (maybe it writes some nice verbose logs after being hit by some recoverable error), you will find yourself wondering what does "upstream sent too big header while reading response header from upstream" imply while your endpoint responds with 502. This is just one possible footgun .. ekhm .. tuning option.
This 3D scan though, is not a reproduction. It is a measurement.
If I run my tape measure around Nefertiti's head, I will obtain a measurement. If you repeat it, it will be the same, provided we both know how to use a tape measure, limited only by the fidelity of our tool.
In fact, any technician, given the tool and a manual, will create precisely the same 3D model.
Having seen Nefertiti with my own eyes, it was a transformative experience, for which I am thankful. But I could never shake the feeling that it should not be in Berlin. I was only able to justify my purchasing the ticket from the looters, since they can be considered to render a service by at the very least preserving it. Like a hostage should be grateful for receiving food. But they certainly do not own it, nor any rights derived from it.
WW2 was started by no less than 2 insane dictators, with the blueprint of the events to follow set in the secret pact of the MRP [1].
One of them ended up on the victors' side and the regime continuing to bring terror, misery and economic ruin to parts of Europe for a half century.
[1] https://en.wikipedia.org/wiki/Molotov%E2%80%93Ribbentrop_Pac...
Our teacher interpreted some of the material and she explained that while most households have this book and read from it on occasion, most young people are no longer able to enjoy it on their own.
- Logging. All messages pertaining to a request (or task) should have a unique ID across the entire fleet of services in order to follow the trail while debugging.
[1] http://aerossurance.com/wp-content/uploads/2015/03/737-contr...
- in 3 seconds when in cruise
- in 1 second when on approach
- when in the landing phase - immediately!
Such a system would be certifiable.
Most modern airliners have ~10 "memory items" that are procedures that are to be recalled and applied immediately without consulting any checklists. Runaway stabilizer is such a memory item. But first you need to recognize the issue as such..
It bears to mention that the 737 is riding on it's "grandfathered" certification status from the 60's, getting a free pass on many newer requirements that are subjected to airliners designed today. This is why it doubly makes sense for the bean counters to not design a new aircraft.
1. The confuser commands a nose down trim, this means that the leading edge of the tailplane is raised. In actuality, this represents a decreased angle of attack (think of tailplane as a upside-down wing).
2. Pilots haul back with all their might. This means that the elevators (the trailing control surfaces at the trailing end of the tailplane) deflect upwards in order to increase the angle of attack and create more "downforce" from the tail, raising the nose.
3. Think of the trimmable tailplane [1] as moving around a pivot. In reality it is a jackscrew/hinge combination.
4. The elevator deflections (the intuitive response) "creates a twisting force" the tailplane around the "pivot point" and against the desired direction that you want the trim to travel.
5. Unload the elevator pressure to make it easier to trim it. The key is that elevator deflections, despite intuitive are not sufficient. Luckily, it is a trained manoeuvre.
[1] https://i.stack.imgur.com/9RQY4.jpg
Note the UP and DOWN markings on the airplane's skin.
Of even more significance is that is currently unclear if it is even possible for a pilot, once it has disengaged the trim motors (following faulty commands from MCAS) to manually correct the trim as per Boeing procedure [1].
The problem lies in the fact that it makes a lot of sense to haul back on the yoke as hard as you can if the nose starts dropping. Elevator upwards deflection loads the tailplane aerodynamically in such a way that it becomes harder to trim the tailplane in the required direction. Called colloquially a yo-yo maneuver, you are then require to "offload" the tailplane (think - push yoke forward..) in order to be able to manually correct the runaway trim.
Plane going nose down, push yoke forward at 500ft? I do not envy the crews at the pointy end of those flights. My heart breaks just thinking about it.
The Lion Air pilots must have been pulling back on the sticks until their tendons break, to no effect. I hope there is a special place in hell for Boeing execs.
[1] 737 Flight Crew Training Manual, chapter Non-Normal Operations/Flight Controls, sub heading Manual Stabilizer trim:
"Excessive air loads on the stabilizer may require effort by both pilots to correct mis-trim. In extreme cases it may be necessary to aerodynamically relieve the air loads to allow manual trimming. Accelerate or decelerate towards the in-trim speed while attempting to trim manually."
This was recently brought to the attention of members of a certain pilots forum that does not welcome lurkers, hence not adding a link.
/safe/path/$hostname.key
$hostname = ../../etc/some/secret
/safe/path/../../etc/some/secret.key> You make a single API call with the name of the hostname you want a certificate issued for ... [magic TLS things happen]
This, precisely, is how the ALB _should_ work, without a silly 25-certificate limitation. Sounds like an excellent service.
I wonder what is the cost of issuance for a TLS certificate. There is minimal storage/network load, some computations (likely in hardware). Perhaps the main cost is the collection of sufficient entropy?
For example, Application Load Balancers (ALB) come with a limit of max 25 certificates, which is non-starter for us. So you cannot avoid terminating your TLS in nginx/caddy etc (it also needs to be HA of course) and then hit another LB that stands in front of the actual service. You end up with a 2-layer LB architecture that adds cost and complexity.
If you run a multi-tenant system that services N "vanity" domains (where N is around the same number as your users on a $5/month plan), there is still no service in AWS to do transparent TLS termination for a reasonable cost. Which is a pity, since it really costs almost nothing to generate these certificates.
I thought I am immune to this kind of exploit thanks to my technical knowledge. Not so, nearly. I once found a good price on skyscanner.com that directed me a site called BookingHouse, that in turn used a "man-in-the-middle as a service" company called mistertango.com that proceeded to ask me for ... my e-banking credentials. I had to slam the mental brakes hard to avoid typing out my credentials on this page, and realised how vulnerable you are when you are conditioned to following instructions as fast as you can (don't want to lose those sweet-priced tickets!).
This mistertango.com service even goes as far as "interactively" asking for your 2nd factor code! I thought it was surreal.
Notified BookingHouse, SkyScanner. No reaction.
But that is my point - if you force your customers to such a position, albeit for plausible security reasons, you better make sure your browser is top of the game.
I still very clearly remember when Jobs showed everyone that you can have a Real Browser in your palm (as opposed to WAP-somethings). You could hear jaws dropping around you. It was glorious! I do not think you get a proper browser with iOS these days. The world has started to be "optimised for Chrome" and this sucks.
[1] https://help.videolind.com/article/4-video-does-not-work
Firefox for iOS is a browser from Mozilla, for the Apple iPhone, iPad and iPod Touch mobile devices.[5] It is the first Firefox branded browser not to use the Gecko layout engine as is used in Firefox for desktop and mobile. Due to iOS security restrictions chosen by Apple (specifically the inability to set writable pages executable, which is essential for just-in-time compilation), Firefox has to use the built-in iOS WebKit-based rendering framework instead of Gecko.
In short - no Gecko.
Just yesterday I watched hilariously how a friend tried to do an online job interview on her iPad. But no MediaRecorder API support. Had to lend her my 200 euro Android burner to get it done. Pathetic.
Edit: To be fair, Edge would also have dropped the ball, but then again you probably have FF or Chrome also installed. In iOS you are SOL.
Wow, I wish I could get back those hours drawing complex tables and placing 1x1 pixel images in strategic places.
You must be from Estonia. Or on crack. I'm guessing Estonia.
A lifetime of experience has convinced me that we will have hoverboards, hell, self-flying hoverboards, before such a scheme becomes the universal norm.
The guy is absolutely right. Mutt is not a gimmick like ascii video on terminal.
It actually makes a lot of sense as an email client and is surprisingly ergonomic. I also enjoy the fact that my config is a normal dotfile that I can version control etc. Also, your passwords can be encrypted using the tools that you choose, as opposed to whatever home grown crypto (if any) the [insert random Electron email client] uses. Some ways are outlined here:
https://www.mail-archive.com/mutt-users@mutt.org/msg36375.ht...