https://esto.nasa.gov/first-di...

Yes, I know, since I was on the team for storage (Block, File, Object) at a large ISV with data centers around the world.

Again, yes, I'm aware of that. Typically, the data centers I was working with used multiple OC-192's. Telco class MAE routers are not cheap.

I think you meant egress. Which is common because Object Stores are non-atomic. If you want to change an object, your first step is to download what's there (if you didn't keep a local copy), change it, delete what you have in the store, then upload the changed dataset. Because it's non-atomic.
I did a quick squint at S3, looks like nine cents a gig egress up to 100 GiB, and then you go to a lower pricing tier. Ingress is also a change it looks like, for the API for sure, I didn't bother to identify transit as it's an object store.

Actually, the choice was made by a political appointee for policy reasons. Math had nothing to do with the outcome in that case.

Which is why SWIFT has API tiers, to limit the price of runaway programs with bugs, or unexpected traffic. So does S3, and you even have an exposed API to check your call statistics. Not sure with the S3 system has for a refresh cycle, what I worked with were contemporaneous. If I recall correctly, someone sells an API sifter for Amazon billing that will alert you to monitored issues. I'm a firm believer that "no news means you're ignorant, which is never good news."

I am comparing using an internal system versus a service.

The selection of a service over using internal mechanisms is when the service is either too lightly utilized to justify facilities, staffing, and capex,

or

outsourcing those functions is desirable from a operations stand point.

From that standpoint of facilities, staffing, and capex, it is unquestionable that the government fulfilling these will be less expensive in the long run than using a service. That leaves policy as a deciding factor going against it. The policy consideration wasn't articulated.

Wrong, it's 100% on the teen's parents. Blaming internet or some chatbot is being the typical modern snowflake trying to shift blame where it doesn't belong.

I found out and it's boring. Amazon has 60 crashes per million miles, half of USPS rate.

> It used to be my go-to site for all things computer related.

Me too.

They were slightly cheaper than Amazon for the same product, then I did a big project which got slightly downsized and I wound up with $400 in "restocking fees" for a couple of pieces of factory-hologram-tape sealed network gear, after I paid $100 in return shipping.

Learned my lesson real fast.

The workers tried overthrowing the government. Jewish Bolsheviks seized power and ruled the country. They then murdered ten million Christians in Ukraine.

This genocide was covered up by the New York Times, who won a Pulitzer Prize that they still proudly display today.

Why do you think Big H was so fixated on invading Russia and eliminating Jews?

The Bolsheviks openly declared their intention of conquering all of Europe. They tried, too, only to be stopped by the valiant Poles at the Vistula.

Everyone knows about H and the six million, but nobody has heard of Yagoda the Jew and the ten million. Make Yagoda famous!

Them: Why don't you act your age?
Me: Well, I've never been this age before.

Like buying booze, renting a car, purchasing a handgun, buying a lottery ticket, getting a tatoo?

(some of these vary by state)

I don't see how you're too immature to order a Chianti with your steak dinner but you're mature enough to go $200K in debt based on a sales pitch of returns after investment.

These aren't even reasonable equivalents from a neuroscience perspective.

A read is supposed to be fine. At read time the firmware *should* rewrite the cell if the read is weak.

The firmware also *should* go out and patrol the cells when idle and it has power.

you can dd if=/dev/sdX of=/dev/null bs=2M once a year if your firmware behaves.

If your drive is offline you could
dd if=/dev/sdX of=/dev/sdX bs=2M iflag=fullblock conv=sync,noerror status=progress

to be sure, though write endurance is finite.

If you're running zfs you can 'zpool scrub poolname' to force validation of all the written data. This is most helpful when you can't trust the firmware to not be buggy crap. Which only applies to 90% of drive firmware out there.

Well 0-clicks and OTA attacks but yeah, to your point, device compromise lets you use apps on the device.

News at 11!

> I have found that streaming directly to my Plex home server over TLS is generally smoother without going through Wireguard. Not quite sure why.

I recently had to solve this.

Wireguard should work with a regular 1500byte MTU connection at 1440 or 1420 bytes (the default) --- however --- if your ISP is routing your IPv4 using 4-in-6 internally (like my major cable company) everything goes to hell.

Try dropping your wg MTU to 1360, MSS at 1320, and set up a mangle table to clamp MSS to PMTU (e.g. iptables rule).

I got a 10x bump in TLS over wireguard throughput.

Total pain in the ass and lightly documented.

Robots will replace most of those and very soon, not Musk's but Chinese ones. Their construction robots are already doing amazing things with a single human supervisor

Road workers? Plenty of things are replaceable now. That flagmag? road painter? pouring concrete?

it's coming.

Deflation and slowing of economy wouldn't be allowed though, Fed would pump money. Your inner Jew needs to be channeled into bargain hunting and saving with investment to have peace.