> Am I supposed to be having issues with TCP connections right now? (I'm not.)
If my skim read of the slop post is correct, you'll only have issues on that machine if it hasn't spent any of that time asleep. (I have one Macbook that never sleeps, and I'm pretty sure it hit this bug a week or two back.)
> very few users are likely to be affected by this
I have a reasonably strong suspicion that I experienced this a week or two back, on a MacBook that doesn't go into sleep automatically and quite likely had 50-ish days of uptime.
It had all the symptoms described - tcp connections not working while I could still ping everywhere just fine, and all the other devices on the same network were fine. Switching WiFi networks and plugging in to ethernet didn't help. A reboot "fixed" it.
Yep, I concur: this explains a bizarre behavior I’ve noted in my Mac laptops for ages now. I have a tendency to just suspend them without rebooting for ages, especially the work one that doesn’t leave my office as frequently. Periodically, I’d come in to find the system bizarrely frozen just as they describe: TCP stack blocked up, but everything else on it behaving normally. (Well, mostly: some apps would block starting and bounce eternally, but I suspect that’s because they’re trying to make a network call while starting up and it’s blocking.) The only fix was a reboot.
It’s not a disaster, but very annoying. At least now I can just schedule a reboot every 30 days at minimum to keep things running.
> Still, I had assumed there might be some kind of master key that would handle this automatically during a password reset.
This assumption, by a clearly technical person, is a fundamental problem that keeps "the rest of the world" locked in to centralised services where that is true, and where that master key can be used against them by law enforcement, fascist regimes, and surveillance capitalists.
Author of the blogpost here:
Firstly didnt expect anyone would read my blog post (Atleast not this soon) let alone someone posting a link on hackernews.
Yeah I realized while i was writing that if somehow that (my assumption about master key) did happen then it would be bad press and completely destroy Apples reputation for a privacy first. At the same time for an usecase like mine where i want my work isolated from personal it is weird that without proper way to get the data back they would allow this to happen. I mean if i really didnt remember my password then my keychain data would have been gone without which lot of work related info would have been hard to recover.
> I mean if i really didnt remember my password then my keychain data would have been gone without which lot of work related info would have been hard to recover.
It is reasonable to expect that having a password it is used to protect the data. A passwordless account does not protect or encrypt data.
Windows by comparison does the same for credential storage. If you forget account password and go your way to reset password, you will lose access to existing encrypted credential store (a keychain).
It was sent to Mars with a plan for 5 flights and a total of 7 or 8 minutes flight time. It ended up flying for over 2 hours in 72 seperate flights before it damaged itself with a bad landing. Not quite the "this thing is still doing science almost 50 years later" that Voyager can claim, but impressively engineered so it lasted way beyond it's initial mission plan.
Note that it is wrong to think that David was at a disadvantage. I know that is not how the story is taught today, but slingshot troops of that age we the snipers of their age: very deadly (not at the range of a modern sniper, but...).
If the fight between them was started at some distance, the David should have been the expected winner by pretty much everyone on the field. Think "bright a club to a gun fight" sort of vibes.
David had a sling, not a slingshot. They are very different tools. slings need more skill, but are easy for a shepard to learn. (I suspect more powerful as well but I'm not an expert)
If you could get that 100,000Amps flowing through your speaker wire, the vaporised copper and the plasma channel would probably keep your 100MW flowing, at least until your building caught fire.
This would be the funniest thing to do. 100K Amps is doable, the question is for how long. That would be one very impressive bank of capacitors. And to turn a 00 into plasma would have some spectacular side effects, such as raining molten copper across a sizeable area. Just your reading glasses would indeed not be enough, there probably isn't any PPE that I would consider entirely safe other than sufficient distance from ground zero. But now I'm really curious. I have a spot welder that will do bursts of 5KA and that will happily throw the breaker every so many welds. 100KA sustained will be a fair engineering challenge.
Ah, that lego project... that was one I always wondered if I should have industrialized it but sourcing enough lego was a real problem.
Holy crap. That's a whole series of bad ideas extremely well executed. That guy probably has never seen what a lead acid battery can do when it explodes. He keeps hiding away from the hot metal but in the path of ~half of those batteries. Ignorance is bliss.
> I realized I may be talking to a serious audiophile, didn't mean to disrespect your Monster cables.
I am a recovering audiophool.
I do own a pair of 2m long Monster Cable speaker cables (with locking gold plated banana plugs). I am fairly certain I've used welders with smaller cables.
(In my defence, I bought those as a teenager in the late 80s. I am not so easily marketed to with snake oil these days. I hope.)
(On the other hand, I really like the idea of a reliably stable plus and minus 70V or maybe 100V DC power supply to my house. That'd make audio power amplifiers much easier and lighter...)
https://airguide.info/boeing-787s-must-be-turned-off-every-5...
reply