Hacker Newsnew | past | comments | ask | show | jobs | submit | dfe's commentslogin

It's the neutral return of split phase that is the problem.

In a modern system the hot, neutral, and ground are all running in the same jacket (like Romex) or conduit. Topology is consistent for all wires in the system.

In a knob and tube system, each wire is individually wired inside the wall cavities. So it's often the case that a neutral wire might feed one set of outlets on one leg of the split, then go on to feed another set of outlets on another leg of the split whose hot wire runs a different route. In fact, that's kind of the whole point of K&T: keep the neutral and the hot away from each other as much as possible because insulation (at the time) was unreliable and shorted wires cause fires. And definitely keep the two hot legs even further away from each other if you can.

Even with perfect topology of a modern system, consider what happens when you are running a 10A appliance on one leg. 10A is flowing through the hot, and another 10A through the neutral.

Now what happens if we turn on 10A on the other leg of the split? 10A flows through hot A, 10 amps flows through hot B, and ZERO amps flow through the neutral because the loads are balanced.

If you turn on a device that has high reactance, like a vacuum cleaner motor has a lot of inrush current, then it can cause lights on the other 120V leg to get an unstable current while the electricity finds its way through the new load instead of the neutral, but then not so much current is needed after the inrush, so it has to find its way back to the neutral.

Now, imagine the neutral topology isn't consistent with the hot, as in K&T wiring. It exacerbates the problem.

Plus, no matter what you do let's say your maximum service ampacity is 200A and you have a balanced 240V load like a permanent A/C. The inrush current can cause the entire rest of the house to brown out for that moment as the incoming service simply cannot deliver that many amps without a significant voltage drop.

That said, it's the unbalanced 120V loads like refrigerators, portable A/Cs, and vacuum cleaners that really cause the flicker, especially in a K&T wired home.


Read the Wikipedia article.

Lutnick visited Epstein by his own yacht. His own yacht has lots of staff and his family was with him so there was no opportunity for bad behavior. It sounds like Lutnick had to meet Epstein about something, so he set it up to be sure no misunderstanding could occur.

I have no other opinion on Lutnick, but having lunch with a powerful figure (Epstein) who is also a neighbor, and doing so in the presence of many, many witnesses isn’t evidence that Lutnick wanted to do anything untoward with Epstein.

There are many, many people who went to Epstein’s island solo or with a group of folks looking to “party”, and there is documented evidence of this. It doesn’t look like Lutnick was one of them.

This whole “oh my gosh, he talked to Epstein a couple of times” is such a distraction. One created by the very people who are actually guilty.


The point is not that he "he talked to Epstein a couple of times", its that he lied about it.

Regardless of having his staff and family there, taking his kids to meet a convicted sex offender is very peculiar behaviour. He could have Epstein alone if he really had to.

Did he also have to invite Epstein to a fundraiser? Did he have to contribute to Epstein's "philanthropic dinner".


Bill Clinton was also vacationing with family when he visited the island as president. This is the common cover tactic.

The fact that government employees are shocked that the political appointees want to perform an industry-standard penetration test on the systems they are responsible for tells me everything I need to know.

What is the reason for the shock? I’m afraid we can only speculate.

What an absolutely insane narrative framing by propublica.


To be fair, I was with you for a minute there, but we both missed it on first reading I think...

> "The agency had been directed not to alert the voting machine company if it uncovered flaws"

That lack of responsible disclosure is not industry standard, afaik. That is slightly suss.


I have a theory on this.

Yes, sugar breaks down to the same fructose and glucose proportion.

That takes months. Even longer in concentrated syrup form. Even longer in the one of two components that bottlers get to make the syrup.

A freshly bottled coke in a glass bottle still has the undivided sucrose and that is why it tastes more crisp. After a while, it separates and it doesn’t taste any better because it physically isn’t different.

A freshly bottled HFCS coke still tastes fresh in all other respects, but is essentially stale on day one as far as the sweetener goes.

But by far the best is a properly calibrated soda machine with fresh syrup— but it’s only really fresh if it is sucrose. Otherwise it’s basically stale before you even make it.


Chemistry doesn't support your hypothesis. Sucrose rapidly decomposes into glucose and fructose via acid-catalysis. Coke is very acidic.

The half-life of sucrose in coke under good storage conditions is ~2 weeks[0]. Modestly higher temperatures, such as during transport, reduces that to hours. The internet suggests that that coke is typically consumed 4-12 weeks after manufacturing, depending on the supply chain. Even in the most optimistic scenario, no more than 25% of the sucrose remains when you drink it. Realistically, it will round to 0%. Almost no one has drank a coke that still had sucrose in it.

The process is slower than enzymatic catalysis in the body (seconds to minutes) but still quite fast.

[0] I used an LLM to run the math but the result passes a cursory eyeball test.


(You mean that it takes months in the bottle; it's pretty much instant in the gut.)


Under typical conditions the half-life of sucrose in coke is hours to a couple weeks via acid catalysis. In the body the half-life is seconds to minutes via enzymatic catalysis.

The half-life of sucrose is greatly reduced by acidity and to a lesser extent temperature. It is stable for centuries in a neutral pH when kept cool but that describes almost nothing we do with sugar in foods.


Never go full retard.



Both of these oddities were addressed over 25 years ago when Mac OS X 10.0.0 "Cheetah" was released.

Many of the innovations of Mac OS X have been lost in later macOS, but this one stuck. Instead of saying literally "Program" it is the bolded name of the application. This serves the dual purpose of also identifying which program's window is active. Inside the application menu, you'll find both Preferences (now Settings) and Quit.

I'm trying to figure out if you are a Mac user taking a swipe at Windows or if you are genuinely unaware that more or less exactly what you describe has been implemented in a shipping product for over 25 years.


For my own programs I also do it this way exactly, because I find that pretty dumb. Preference also gets put under Edit or Options or Somewhere else, which is really annoying. And then you get different settings, that are called differently and are in different places, great.


Are you sure IBM didn't care about 8080 compatibility? The PC was released in August 1981, a full 4 years before any of the other machines you speak of. That XT 5160-078 you speak of is a cost-reduced model with no hard drive from IBM, allowing dealers to install a compatible hard drive from a different supplier.

By 1985, the PC AT (286) had already been out since August 1984. And the original XT was October of 1983. And the XT itself is literally the same as a PC with more expandability: 8 slots instead of 5, beefier PSU, room for a hard drive.

It's unclear if IBM or for that matter anyone would have been able to start designing a 68000-based machine and bring it to market by the fall of 1981. Sun brought the Sun 1 to market in May 1982, so about 9 months later, and with a much higher price.

And what did the Sun run? UNIX. What did IBM run? Quick ports of the last several years of CP/M software made possible because DOS 1 was specifically designed to implement a CP/M-like API, and the 8086 was specifically designed to allow porting of 8080 assembler code directly to small model 8086 code.


I picked 1985 specifically because of the Amiga/Atari 68000 machines, to show that it's not about price. Had Sun wanted to target the games-machine market, they could've designed for, built and sold a $600 machine based on a 68000 in 1981. Their pricing was because they went for the UNIX workstation market; they also designed and produced their own custom MMU because Motorola's 68851 didn't work correctly for them

Motorola were selling 68000s for $125 each. Steve Jobs talked them down to around $15 each. (Macintosh launch price: $2,495 in 1984) Memory model did not dictate price. Target market and vendor management did.

IBM would have been entirely capable of launching a TMS9900-based PC or a 68000-based PC, had these chips been in full production in 1978. The software and OS for the IBM PC was an afterthought, IBM settled on the CPU first. Had they picked the 68000, they'd have been contracting out for 68000-based OSes.

https://spectrum.ieee.org/the-inside-story-of-texas-instrume...

> Selection of a 16-bit microprocessor by the IBM team couldn’t have been much of a debate. The Motorola 68K, as it was later known, was undoubtedly the hands-down winner. It had the largest logical address space, which was even more important than the minimum 16-bit internal architecture. It was also easily expandable to a full-fledged 32-bit architecture.

> So why aren’t we all using 68K-based computers today? The answer comes back to being first to market. Intel’s 8088 may have been imperfect but at least it was ready, whereas the Motorola 68K was not. And IBM’s thorough component qualification process required that a manufacturer offer up thousands of “production released” samples of any new part so that IBM could perform life tests and other characterizations. IBM had hundreds of engineers doing quality assurance, but component qualifications take time. In the first half of 1978, Intel already had production-released samples of the 8088. By the end of 1978, Motorola’s 68K was still not quite ready for production release.

So it wasn't about architecture, and it wasn't even about price. It was about time-to-market. The 8088 was in full production and the 68000 was not quite there, at precisely the time IBM wanted to create a PC. The 8088 might've been even quicker to market had they left out the memory segmentation, but Intel had their own business reasons (wanting to sell to existing 8080 customers) for adding it.


Bribes are a feature of politically-controlled economies, not a bug.

Thirty years ago when this was all going down, I believed the narratives of the time. Greedy Bill Gates and Steve Ballmer pushing IBM's OS/2 out of the consumer market with aggressive DOS and Windows OEM deals.

I mean, they absolutely did do that, but I think the motivation was competitive survival.

The Steve Ballmer interview really shed a lot of light on this, particularly the portion about the IBM and Microsoft OS/2 divorce: https://youtu.be/CYC49_aeop0?t=1476


It was drop DTR. Most current documentation tells you that dropping DTR means the modem should hang up. That was an option, maybe even the default. But you could AT&D1 to make dropping DTR return you from data mode to command mode. It's so important there's even a DIP switch on the USR Courier to enable this mode.

https://support.usr.com/support/3453b/3453b-crg/chap%208-con...

I almost can't believe the USR site is still up. This is something I remember doing to run a BBS over 30 years ago. I still have my Courier with the brass not for resale plate.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: