wongarsu

Have on-call sysadmins or have them work in a three-shift schedule. That way there's always someone there to fix stuff as it happens, including deploying security patches or worst case taking affected systems offline until they can be patched

This used to be common before devops and cloud took over. Looks like it might make a comeback. Maybe with a new fancier job title

The argument for bitcoin being secure is more along the lines of "if you store your own bitcoins securely nobody can take them from you". Storing them securely is easy in principle (just keep them on an airgapped computer, or write the key down on paper, then "just" do physical security well) but hard in practice (major security-convenience tradeoffs). However, storing your bitcoins with a major provider like binance has a terrible track record and not something the hardcore bitcoin advocates actually recommend

As someone who was a beginner once, I found nano leaps and bounds more intuitive than vim. You can quite easily stumble your way through nano with minimal exerimentation, and once you figured out that ^ stands for control you can just use the handy always-visible command reference at the bottom

Sure, GUI software is much more intuitive. But if you start with the constraint of being a TUI editor with no mouse support, nano does extremely well

The intention of bitcoin was to have a digital medium with similar properties as cash: no need to trust anyone else, and you can exchange it with whoever you want. Cash can also be stolen if someone takes your wallet, leaving you no recourse except the law

Imho Bitcoins being stolen is not at all Bitcoin being "bent, broken, or subverted", it's just a natural consequence of the design goals. If an unrelated third party could block my bitcoins by accusing me of terrorism that would be subverting the system, and such things have not happened to bitcoin-core (but have happened in other parts of the bitcoin ecosystem)

The real punishment arguably already happened. This could have been a feel-good project with lots of positive PR: a datacenter built far from major population centers, in a place with lots of available water that isn't used for anything else, in a country with relatively cheap electricity that is overwhelmingly produced from nuclear, hydro and wind. Amid all the negative datacenter PR it could have been a project Google could point to where every single objection has been addressed. Instead it has become a PR disaster that has been dragged through the news cycle and social media's outrage cycle.

Moving time "east" of our actual timezone is pretty appealing to me because of how evening-heavy standard schedules have gotten. The sun might behave symmetrically around 12:00, but most people don't get up at 4:00 and go to bed at 20:00. Most people's days are shifted 2-4 hours to the evening compared to that symmetric schedule, which makes sunlight in the evening more useful than it is in the morning

I can get the idea that for some cases it can be in the public's interest if specific court hearings are closed, or if it's secret that certain court hearings or entire cases even exist. There is a lot of potential of abuse (and a documented history of abuse), but at least the idea makes sense

But I can't see a public benefit to keeping the principles such a court uses secret

If we showed the EV cert DN in the the address bar next to the domain instead of hiding it in a place that takes two mouse clicks to reach we could expect at least a portion of victims to notice. I vaguely recall some browsers might have even been doing that once upon a time?

Additionally, the browser could show a warning if a ccTLD is served with an EV cert of an entity outside that country. Doesn't help the US because of the obscurity of .us, but useful for the rest of the world

Obviously this prioritizes quality over speed, but how far are we from real time? Hooking something of this quality up to a live webcam would be a dream

... you use Actually Indians?

Jupiter's atmosphere is about 25% helium. And then there's the other gas giants, and the sun itself (also about a quarter helium)

We risk running out of cheap helium. But if you are willing to pay infinite money there is near-infinite helium

Pogo pins are expensive. Somewhere around $0.15-$1 per pin. This design has four pairs of two pins. So just the connectors are over a dollar per key, possibly multiple dollars

In most office jobs, at western salaries, you don't need much productivity improvement to offset $100/mo

Though I would expect the majority to do fine with $20/mo. That's the same effective cost as replacing a $500 computer every two years, which is the sort of expense most companies are comfortable doing without much second thought

For first-level support that's just regurgitating documentation and debug procedures I agree. But when it comes to actually executing actions (resetting 2FA, issuing refunds, handling payment glitches, etc) you need humans.

Social engineering is an issue with regular support, with agents it's a lot worse. And with agents it's repeatable: if I find one conversation flow to get it to give me money I can instantly repeat that with a thousand fresh accounts, and then share the same "exploit" on reddit for everyone else

It includes compute and infrastructure for R&D. Then you have to add just over a third of their compute spend for personnel, another expense of that size for sales and marketing, and half that for other admin/ops costs, for an operating loss of 693M. Then a bunch of accounting stuff to end up losing 80B

I'm not sure I'd call it a great result, but it's a promising one. If they can increase demand without significant changes in margin or R&D spending, they are on the path to becoming very profitable