The security concerns here are really significant. In the section[1] on security, they write "we recommender you monitor Claude while using this feature." This borders on irresponsible IMO. Monitor what exactly? How should we monitor? What logs and metrics are exposed for security monitoring? How would a user recognize suspicious patterns...?
A massive effort is currently underway by undersea mining companies to dredge the life out of huge swaths of largely unexplored seabed, including Antarctic and Polar regions.
It's the same insanity that allows industrial fishing fleets to drag kilometers-long nets through the sea scooping up megatons of bycatch -- although, this time we are likely to obliterate seabed ecosystems before anyone even has a chance to see them.
Some brilliant reads on these and surrounding topics:
Yep, a DisplayLink hub is the way. I've also been using one for 6 months and while it is perfectly stable, there are annoyances. For example certain protected video streams won't decode, and F.lux doesn't quite work on all monitors the way it should. Overall though I've put up with it. It's really an outrage that Apple restricted this basic functionality just because it could.
> Just under a million of that was on storing 8 petabytes of files in S3, fully replicated across several regions
Hol' up. They're replicating data across regions -- across /several/ regions -- on top of a service (S3) which already has 99.999999999% data durability in a single region? ...Why?
HN readers love to opine on how "safe" nuclear is so I have my popcorn ready for this thread
> the lab was the location of one of the nation's largest — and least known — nuclear accidents that occurred 1959 when one of the facility's ten sodium nuclear reactors experienced a partial meltdown, releasing enormous amounts of radiation into the surrounding environment.
"On March 24th, 2022, I was riding my bike near the beach in San Francisco down a slight slope. My hands were on my brakes to make sure the bike was in control. About 150 feet ahead of me, a vehicle suddenly stopped in the middle of the road. To avoid oncoming traffic, I veered towards the vehicle's right, which suddenly moved directly in front of me.
At that point, I could not avoid impact and crashed through the vehicle's back window with my bike. As I lay on the road, I saw that the car that hit me did not have a driver."
I really like the idea of a book graph. Heck, if the platform suggested that I read the references for books I'm currently reading, that would be interesting.
Managers are supposed to weed out people that slack off enough to slow delivery and cause headaches for their peers.
I do know some engineers who seem to coast or just be unhappy 70% of the time, but the 30% where they show up is insanely valuable. Those people can stay in my org.
What I really hate is the guy doing what the OP is doing while his colleagues are working long days and weekends picking up the slack. That's just being an antisocial leech, and that person is toxic to a team and to morale.
Every damn Well-Architected Framework includes multi-AZ if not multi-region redundancy, and yet the single access point for their millions of customers is single-region. Facepalm in the form of $100Ms in service credits.