dhsysusbsjsi

This is great and remarkably similar to my personal philosophies on spending and work. For example avoiding unproductive debt, spending below means, vocation you enjoy, etc.

I do disagree with the bit about accepting rude customers. I will happily forfeit business of a rude customer. This is especially true if your employees are high value and you don’t want them subject to abuse (feel valued), and I hypothesise that in fact genuinely rude customers aren’t as listened to by friends as they think in their own mind.

> Turns out there is a convenient setuid binary called “amossu” in the stock firmware

Understatement of the year!

Same I just checked and I have completely fake details and a throw away email. I love it when my past self does cool stuff !

Is this used on the VEMD in Heli’s, eg H130?

This is big - Jeppesen products are central to a lot of airline and flight ops.

I joined Twitter for the curated news feed.

You can still set your feed to timeline so you don’t get anything the algo feeds you.

I’m staying; my feed is a great source of news and opinions from various prominent scientific, tech and hacking people.

The more I learn, the more I find that “best practice” isn’t always best. It should be called good defaults.

For example “Disable ssh password auth and use keys”. It depends on your threat model. A good password can be secure and may in some cases be more secure than a stolen laptop containing id_rsa. SSH keys are more convenient but rely on physical security. It should be discussed as a trade off.

The way GPS was designed to work originally is two sets of codes. Course Acquisition (CA) code which repeats at 300ms intervals with a deliberate bias was designed to bootstrap the receiver into locating its position in a 1-week Precise (P) long code. This bias was selectively worse in different regions and I think still can be changed in war zones. Happy to be educated further here!

What the US government did was remove the bias from the CA code so it could be used for precise positioning. The military still uses P codes as well. I believe there is a small gain to be had but it’s due to frequencies.

Since then there have been several more advances, mostly to broadcast local augmentation signals. Wide Area (WAAS) and Ground Bases (GBAS) are common in receivers.

L5 is a new band to help solve multipath error in urban areas.

Most receivers also have remote autonomous integrity monitoring, where it can predict its own area of probability (by using groupings of 4 in 5 satellites), and if it’s too large for the intended use case, alert the user. Also with 6 satellites it can calculate combinations of 5 satellite groupings to work out (and exclude) faulty satellites. This is Fault Detection & Exclusion (FDE).

Mobile devices will also download their own separate high resolution almanac and ionospheric data over the internet which is superior to the low data rate GPS almanac. It can also use known cell locations to approximate its position. Combined, this enables rapid (hot) signal lock immediately onto the correct satellite code & Doppler shift frequency, which is why your mobile gets a fix in 3 seconds, versus your car which takes minutes.

This is a basic story of how some guy pumped a shitcoin in third party markets to make his 1e100 coins appear to be worth a lot, but lacked any exit liquidity to actually make any money.

I wonder if the tax office would allow people to value a security based on the order-book. Or does this reporter now owe a billion dollars tax! Clearly it's only "worth" $10 or something, once he drains all external markets with his first trade.

I set up an auto-correct for 'ducking' to replace it back to what you actually want to say.

Also whilst Apple is reading this, please stop changing "were" to "we're" out of context. Ugh.

If a phone can take down airline communications, there is something wrong with the aircraft. These should be properly shielded lines.

There are now millions of hours of airline ops with phones on. It doesn’t cause any problems.

Also hot tip: the pilots are using iPads the entire flight too. With Bluetooth and wifi often linked to other gadgets.

The summary should be to use a request which satisfies the long term minimum cpu required at any given time. Then if you’re happy to allow it to burst then don’t set a limit. If you want consistency and constant runtime, set a limit. If you find that your container only works when it uses the “free” burst time, and breaks when it goes back to the request cpu, then your request is too low.

Oh and make sure you raid the stationary cupboard. 8 years later and I still have a surplus supply of 4-pens!!

Don’t take more than an item a day though.

Stock up on printer paper and things like that.

I have experience at this. Don’t do any work. Research your own hobbies on work time. Look for new jobs. Browse Hacker News articles. Use work time to organise all your normal affairs such as tax, paying bills, being on-hold to companies sorting out things. All the time consuming activities that normally consume your life hours. Transfer these to work hours. Plan your dinner meals. Build new skills and learn a new tech stack. Don’t answer emails. People will call you if important. Don’t answer calls outside of work time. Especially unknown numbers. Arrive late, go do some exercise, show your face, have a long lunch, more afternoon fitness. Leave early.

I did this for 3 months whilst transitioning to a new job; my old boss was the biggest psychopath in the world. In three months I did absolutely nothing. They would send me to meetings and I’d just sit there! It can be done :)

The wallet address was a bunch of leading zero's, indicating it was probably generated from a vanity address - likely Profanity. Which was recently discovered to have a fault in the private key generation resulting in a 2^32 key space.

The way profanity works is from its (very small) private keyspace, it chooses a key at random. It generates a public key using secp256k1.

Then it repeatedly (embarrassingly parallel) adds the point 'P' (as defined in the spec) to the public key coordinate, and hashing to check the address is a desirable vanity address. Repeat. Once a desirable vanity address is found, the private key for the vanity address is the original private key plus the number of 'P' additions required.

So to crack these, all the attacker needs to do is find a target address (eg Wintermute), a transaction it has done before exposing its public key.

Using a previously generated dictionary of private:public key pairs for the 2^32 compromised address space (only a few hundred gb), it repeatedly subtracts 'P' from the publicKey and checks if it's a known pubkey in the dict. Repeat until you find a known Private:Public keypair. The private key of the target address is this private key plus the number of subtractions required. Trivial to brute force an 8 digit vanity address.

I remember reading an article once where they said SIP sends the hash of the application in the clear. This allows your ISP to track known application hashes you have installed. Unsure if this is still accurate.

Yeah but to be fair, aviation statistics would also be 10% as bad if they excluded people who didn’t fly into bad weather, took off overweight, didn’t have enough fuel in the tanks, ran out of light or were too fatigued, or couldn’t say ‘no’ to tasking or an unserviceable aircraft.

I’m not familiar with the US system but stall recovery training is mandatory in Australia. Seems to be in FAA syllabus too:

https://www.faa.gov/sites/faa.gov/files/training_testing/tra...

Spin recovery different issue.

It’s 500ft in the flight manual

It’s all about weight. These aircraft are optimising to the last kilogram. If you add 10kg more, that may be 1 less pax, or 15 minutes (34 NM) range.

A wise man once told me: there are three things: Altitude, airspeed and brains. You need two of those things!

I know of 7 engine failures with people I know and they all walked away safely after landing in a field. It’s rare it ends up in a fatality, even without a parachute. Most are in fact twin engines that suffer an engine failure and mishandling results in Vmca (too slow for rudder to keep it straight), and they depart controlled flight and crash. 2 engines is not safer.

What you’re after is a piper cub. Incredible short field takeoff and landing performance. You can land from an engine failure in a tiny amount of space, quite safely.

The comments so far seem to presume the parachute is the only thing required to keep you safe. Statistically there’s two engine failures every 100,000 hours in single engine pistons. That’s incredibly low. Most pilots are lucky to make 1000 hours in a lifetime.

The thing that is actually going to kill most people is flying a perfectly serviceable aircraft into the side of a hill in bad weather, hitting wires, or mishandling on base turn and stalling.

The previous comments about the parachute being ineffective for takeoff and landing are partially correct. The minimum altitude for successful CAPS (parachute) deployment is 500ft AGL, but it has been used much lower successfully (sorry don’t have the figures but I think 200-300ft).

They market the CAPS like it’s the only thing required to make flying safe but in reality you are more likely to kill yourself than the airplane killing you; and a parachute won’t stop that.

I learned that in SwiftUI if you don’t want a view to re-render when one of its properties changes, but you need it to have that property/state because it needs passing to children, you can just make it a regular variable without the @PropertyWrapper.

Seems pretty obvious in hindsight!!

The problem with Cirrus is the parachute. Insurance companies don’t like it because instead of half or more of aircraft landing safely on a road or in a field, they are now all write offs. This then adds insurance premiums. We are also now in the position of having to do extra annual training (irrespective of experience) to get insurance because so many amateur pilots are flying Cirrus (I think it’s the new V tail doctor killer, minus the killing). You have been warned: there are better aircraft out there imho. And I haven’t even started on the flight controls (spring feedback is terrible), unstable yaw stability without yaw dampener (pax vomit profusely), and single power lever which decreases rpm with power resulting in an aircraft unable to (easily) slow down (without idle) which is normally done with prop braking. This results in energy problems similar to airlines where rookie pilots who cannot think ahead end up with too much energy. Also these modern long thin glider wing designs trying to get +5kts more can go to hell - they are getting so large it makes ground handling difficult; often longer than the airborne saving. If you want to get there faster, you save time on the ground. A decked out RV-10 is a good alternative.

Heroes wear many capes - don’t forget about the person that just spent 4000 hours creating an application with complex menu’s and logic for a specific domain.

The right person can be extremely productive and generate incredible value anywhere, but often it just isn’t as sexy as compression algorithms.

A tip of my hat to all you hard working talented people out there.

Have you considered that the underlying map may be out? I remember (non-academic) researching this and looking through past Google Earth imagery and its about a 2 metre error.

Also the challenge of old receivers was which Doppler shift frequency to listen on depending on if the target satellite is going towards or away. By knowing the rough location (from cell towers, known wifi AP’s etc), they can get an instant lock.

This explains it the best:

https://brrr.money/

Yes ^^