kloch

> During this process, scientists will use a Sun-like star named HD84406 to focus the mirrors

Here is a 1 degree wide view of the neighborhood around HD84406 rendered from Gaia EDR3 data:

https://bsrender.io/sample_renderings/hd84406-1deg-m18-ax100...

Not too many other stars around, and none that are brighter than it within almost a half degree radius. If I zoomed in to the 0.0367 degree FOV of Webb's NirCam instrument, we would only see one other very faint ~21 mag star. However, Webb (and Hubble) can see much fainter stars than Gaia.

Just about every electronic circuit I designed and built as a teenager used one or more 555's. The most practical was a repeater controller for ham radio. The most interesting was probably a pulse width modulator a/d converter.

There was almost nothing you couldn't use a 555 for, and there was almost nothing you should use a 555 for. I remember those circuits not being very stable but then again I am not great at analog circuit design.

Interesting... this implies 64 bits per pixel. What format would that be, 16 bits per color RGBA?

Is the viewer open source? I saw links to give credit to various open source libraries/utils but I didn't see a link to the actual system.

It works really well. I'd love to use this for one of my projects.

Uncompressed 717 gigapixels x 24 bits / 8 = 2.151TB

I wish this were being turned into a museum ship like the USS Midway. It's unique since it's the only surviving member of it's class. I guess it wasn't notable enough. Hopefully the Nimitz will become a museum when it is retired.

List of US Navy aircraft carriers:

https://en.wikipedia.org/wiki/List_of_aircraft_carriers_of_t...

Titles are cheap.

Better questions:

  Do you have the knowledge and experience to do your job well?
  Is your brain naturally wired for the type of work you do?

I wrote my first web app in 2000 using C/mysql. It was Insanely fast but very awkward to implement. I used C because it was (and still is) the only language I knew well.

At least if you are going to use C, you (should) know to be extremely paranoid about how you process anything received from the user. That doesn't remove the risk but at least you are focused on it.

The last time I looked at c++ (mid-1990's) it generated hugely bloated binaries and was generally slower at runtime than plain C. Is that still true today?

Is there any language (other than assembly) that is faster at runtime than C today?

It does seem like an overreaction to me but there is a big difference in cell towers and satellite uplinks/downlinks

Radio towers (sites) have widely varying quality control of their tenant's installations. Other transmitters can mix and amplify signals from other carriers without well designed and maintained RF filtering on each and every antenna. The more transmitters at a site the more carrier frequencies that can contribute to the mixing, and the more opportunities for poor or broken RF filters. At some busy sites there is almost nothing you can do to prevent this. Anything on the tower that acts like a diode can cause mixing, even without being amplified by another transmitter.

This usually just harms other receivers at the site however. But an airplane flying close by could theoretically be affected depending on how close it is.

The general concept is correct but there are a few issues with the article:

- Specific RGB values always depend on a selected white balance temperature. If the WB temp is the same as the object's temp it would be white, not blue. If the WB temp were higher than the object's temp it would appear red.

EDIT: the article does say sRGB which implies a 6500K wb.

- "infinitely hot" is not physically possible. The Neutron star example is fine, that temp would be around 10^12 K

At that temperature virtually all of the emission would be in gamma rays, but emission in the visible spectrum would not be zero. Blue wavelengths would be stronger than green, which would be stronger than red so the color would appear Blue for any "normal" white balance temp (like 5500 K).

This is one reason why I am a big proponent of network engineers physically visiting their equipment periodically. In large networks that may never happen, data center techs (often not even your own employees) are the only ones who ever see the racks in person.

Even if the 3rd party tech notices something unusual about the optic the certainly aren't going to touch it without a ticket and will probably not even mention it.

Counterpoint: Bridgerton. What amazing eye candy that is, not just because of the Victorian sets and costumes but the rich vibrant colors.

There are two main uses for this kind of thing.

- Legit: debugging/monitoring. Other legit uses are theoretically possible but the device has severe limitations that likely make them impractical or unwise.

- Surreptitious: This is clearly where the value proposition of this device lies. An optic could be "unknowingly" swapped out on an interesting link to snoop on or infiltrate a network.

Swapping out optics in a large network is not uncommon as they do fail. More often they are swapped out as a troubleshooting step where the original optic may not even be bad. This way log messages indicating link flap and replacement of an optic could likely go unnoticed.

> sans the NORAD visits, of course

You didn't prank call NORAD?

I've had several different cars flash the "Do you need a break?" (with coffee cup logo) on the dash when driving through work zones where you are redirected and over various lane lines at odd angles. It would be really bad if the car automatically shut off in those situations.

They are probably told how to query the internal parts DB which is enough of a challenge just when searching by shape/color/version.

I doubt anyone at LEGO fully understands all of the naming/numbering convention decisions that have evolved over 70+ years.

Why would they even both to encrypt the firmware? Is that a regulatory requirement somewhere?

The case for crypto in one chart:

https://fred.stlouisfed.org/series/WM2NS

Nothing can grow exponentially forever. Any guesses as to when this chart goes to singularity?

It turns out humans are just not good at running their own money supply. This has been true throughout history, even with a gold standard as coins were frequently debased. In current times, this chart of federal reserve assets is illustrative of the current environment:

https://fred.stlouisfed.org/series/RESPPANWW

The growth in that chart since 2008 is new money that was created not by banks making temporary loans but by the central bank outright printing new money and injecting it into the economy (QE). If the FED balance sheet shrinks the stock market will crash and there will be irresistible political pressure to do more QE.

That is specific to the DMCA, not AUP violations in general.

DMCA notices typically go to the owner of the IP addresses and ISP's have wide latitude on how they enforce their AUP.

What a loss for Football, what a loss for Broadcasting.

I'm pretty sure I saw him coach in the 70's but my fondest memories of him are as a broadcaster in the 80's and 90's.

No matter how trivial the thing he said was you felt like you had just received critical knowledge directly from the football Gods. (Because you did!)

In a residential setting there could be capacity limitations/oversubscription that needs to be protected by "DDoS" mitigation at each customer edge. It could do dumb rate limiting which would affect youtube uploads etc., or it could look at flows and try to nuke "obvious" outbound DDoS attacks.

The author's problem is their access media. Get a [1g|10g|100g] [wave|dark fiber] to Lumen and all of those problems go away.

As for AUP violations, they have every right to complain if you are using THEIR IP's in a way they don't like. However, you would likely have to be a real and persistent problem to actually get cut off. If you use your own IP's/ASN like all the big networks listed in the article your risk of getting cut off for AUP violations is practically zero. You would have to be so notorious as to affect their reputation anyway.

From the picture in the article each hole seems to have rings of different widths and possibly counts.

Can boiling sulfuric acid like you used to dissolve the epoxy package be used to successfully de-bayer a CMOS camera sensor?

> Red is not “more blue” than blue is. Red is not “more spectrum” than blue is.

I get what they are saying re: autism but this is an incorrect analogy. If you measure wavelength then red is quantitatively more than blue. If you measure frequency then red is less than blue.

Where does this response put me on the spectrum?

They have the same precision but float has vastly larger dynamic range due to the 8-bit exponent. When normalized and quantized for output this does result in roughly the same effective dynamic range (depending on how much of the integer range was originally used).

The issue is audio is typically mixed close to maximum so any processing steps can easily lead to clipping. One solution is to use float or larger integers internally during each processing step and normalize/convert back to 24-bit integer to write to disk. Another (better imo) option would be to do all intermediate steps and disk saves in a floating point format and only normalize/quantize for output once.

I haven't worked with professional audio in over 25 years (before everything went fully digital) but I would be surprised if floating point formats were not an option for encoding and intermediate workflows. Many quantization steps seems like a bad idea.

If it’s anything like space telescopes there are more than 3 spectral filters that can be selected which rules out a static Bayer-type filter system.

This is a rare case where “many orders of magnitude” is underselling how unlikely something is.

It is estimated there are 10^80 atoms in the observable universe.

I love this. It takes us back to a time when administering a Unix system was a Big Deal. Partly because they were rare and expensive. But also they were truly multi-user with dozens of people logged in at any given time.