One meter is technically defined by the speed of light and a Cs-133 clock at 9.2 GHz, but it's not very practical. For real-world length measurement tasks you use light interferometry. But how do you obtain traceability from a microwave frequency to visible light?
Easy! Here how: Lock a hydrogen clock to the cesium clock first because for better short-term stability, then lock a 100 MHz crystal oscillator to the hydrogen clock to get started. Then, lock a 22.7 GHz Gunn oscillator to the 100 MHz crystal oscillator with a mixer and a PLL. Next, lock a 386.5 GHz Backward Wave Oscillator to the Gunn oscillator. Next, derive a 4251.76 GHz methanol laser from the BWO. Next, derive the 13C 16O2 laser at 29770.665 GHz from that with a mixer, a counter and a 8.99 GHz Gunn oscillator. Next, derive a 29477.165 GHz CO2 from that with a mixer, a PLL, and a 73.35 GHz Klystron oscillator. Next, derive a 28464.674 GHz laser, which derives a 28464.684 GHz then a 29477.165 GHz laser with a mixer, .... #electronics
In a summary of the paper on Cambridge's security research blog, the researchers explain that even if you start with unbiased - that is, broadly representative - data, the *order* in which you present that data to a machine-learning model can induce bias:
https://www.lightbluetouchpaper.org/2021/04/23/data-ordering-attacks/
That's because ML models are susceptible to "initialization bias" - whatever data they see first has a profound impact on the overall weighting of subsequent data. Here's an example from the researchers' blog:
9/
time capsule for digital data
Pick an encryption method that we know is vulnerable to quantum computers.
Encrypt a drive with it, and fill it up with a bunch of stuff currently important to you.
Conveniently forget the decryption key, put the drive in storage.
Perhaps one day you’ll be able to open this time capsule.
Pe Lang has a temporary exhibition in Paris (in https://www.deniserene.fr/) until ~first week of July: https://bibliogram.art/p/Cdf2MDjseRm
Pe Lang makes artifacts that, for me, show some nonobvious or obvious-but-often-overlooked physical property. https://www.pelang.ch/works.html has some examples (but even not the ones I liked most when I saw his exhibition in, sadly defunct, museum of digital art in Zürich).
@Seirdy We clearly need public ice creamportation.
TechPost, HTML and ARIA.
@emily (last reply in a row, I promise) So right now, HTML document authors need to understand four sets of rules:
Much of the HTML standard’s web developer edition
The WAI-ARIA specification’s roles, and how they map to/from HTML elements.
The DPUB-ARIA roles (recommended but not required)
Browser default stylesheets (not a set of rules in theory, but these outline conventions that users have come to understand and should be respected).
That’s…a lot. The authors of each of these don’t read the other three, and I can’t blame them. This results in disagreements and contradictions between all four. <summary> has a list-item default styling but has button semantics; <aside> can be used anywhere but its accessible role can’t; doc-example is meant to be used on role="figure" with or without a caption, except role="figure" forbids additional roles when it has a caption; etc.
Web developers violate all of these quite regularly. When non-standard behavior is normalized, implementations accomodate that non-standard behavior or ignore the broken part of the standard. Standards and “best practices” then change in response.
This creates a feedback loop, and there’s no source of truth. Nobody knows what to do.
This, I think, is what MDN’s focus should be. Taking all these separate sources of different truths and creating a unified set of instructions specifically for Web developers, filing + referencing bugs when disparities between the four sources are found. Tutorial-style documentation doesn’t have to be completely separate from reference-style documentation and software implementations; they should inform each other.
Thank you for coming to my TED talk.
@peterdrake Agh, I have seen soooo much code written by mathematicians and physicists that exemplifies the second option. Dx
@klaatu Ha, same, one of my earlier memories is asking "What are you doing dad?" and hearing "Compiling the kernel.".
@tomxcd@fedi.nullob.si
@mhoye You can still meet and talk with people who hold the non-fascist versions of these views -- you can actually sometimes discuss reasonably with them and they will be appropriately annoyed by hypocrisy. Speaking from experience. I'm trying to point out that you shouldn't immediately assume that a right-winger will treat hypocrisy the way you describe, although your original post is a good reminder that it is currently a frighteningly common option.
Especially strongly agree on the libertarian point, what happened to them in Poland makes it particularly obvious to me.
@lucifargundam Good luck!
@mhoye I would agree it's not a meaningful accusation to fascists, but not really all of the right. There are definitely conservatives and libertarians for whom these things are important as well. Although you clarified this was about USA politics below, it might be more broadly applicable there...
@rcz W obu wersjach dość konkretnie opisujesz wydarzenie pozytywne, a zamiast opisać negatywne podajesz ogólnikowe stwierdzenie że jest źle, które równie dobrze mogłoby się odnosić do Polski bez "stref", czy wręcz wielu zachodnich krajów. To faktycznie unika złych skojarzeń i hiperboli, ale za pewną cenę.
Ja tam wciąż nie widzę hiperboli, choć widzę przestrzeń na nieporozumienie -- "izolacja" może odnosić się do wielu rzeczy, od fizycznej, poprzez społeczną, aż po emocjonalną.
Programmer and researcher,. Ended up working with all the current buzzwords: #ai #aisafety #ml #deeplearning #cryptocurrency
Other interests include #sewing, being #lesswrong, reading #hardsf, playing #boardgames and omitting stuff on lists.
Oh, and trans rights, duh.
Header image by @WhiteShield@livellosegreto.it .
Heheh, gentoo, heh, nonbinary, heheheh... I'm so easily amused sometimes.