I think this is actually a great escape hatch. Supporting non-deterministic builds means more folks will be able to migrate their existing build to zb. Postel's law and all that.
8,442 karma · joined February 1, 2017
I think this is actually a great escape hatch. Supporting non-deterministic builds means more folks will be able to migrate their existing build to zb. Postel's law and all that.
Exactly, really what they are storing is electrons.
Rusting the iron directly releases heat, which limits your efficiency to the delta-T of the process. Reducing steam to hydrogen and then converting the hydrogen in a fuel cell allows higher efficiency to produce electricity.
Edit: wait I forgot that direct reduced iron powder exothermically reacts with oxygen and water in the air, that's how single-use instant hand warmers work. So yeah you gotta isolate the iron powder a bit more than stick it under a tarp.
I've been playing too much Factorio lately so of course my mind goes towards rail systems (could repurpose coal plants) in combination with pneumatics.
You still need a pretty beefy rig (array of multiple 4090 gpus) to do convincing video generation in a non-glacial amount of time but it's totally possible with readily available hardware.
The bigger problem is actually "cheapfakes", so many people are so confirmation-biased that they will readily amplify even poorly put-together disinformation.
"doom principle" isn't great either since the first hit points to TFA, second to this very thread, and that article doesn't really use the actual term of art.
My friends and I independently came up with this exact idea at the most recent regional burn event, specifically to better coordinate meeting back up after wandering, and then discovered this device, so it's very much a real problem in need of solving.
Concerts are usually pretty easy to find your friends after splitting up. They are usually at the bar, restrooms, or a handful of viewing spots or seats. Big raves, music festies, burns, and other large gatherings are spread over a much wider area.
Cheeky math aside, getting signalling logic to work with ternary, especially when clock rates go so high the signal starts to look less like square wave pulses and almost more like a modulated sine (due to slew), you now need much more sophisticated decoders.
Also the double entendre of "plug" in technology contexts, subtly brilliant.
The irony of TFA mentioning the midwit meme.
50 iq - just use python's stdlib logger
100 iq - use loguru or some other custom log lib with fancy colors and formatting
150 iq - just use python's stdlib logger (with your own formatter)
Loguru is great for user-facing applications (especially when that user is a developer), it's pretty, structured out of the box, nice to use API. It's also pretty bloated and adds hundreds of ms of startup latency. Terrible for lambda/Faas cold starts.
Lately I've taken to just making a dict of the various field names and format strings, and json.dumps it into logging.basicConfig, boom, instant json structured logs. Middleware takes care of the rest. It Just Works(tm) and one of the most frustrating things is buggy loggers. The less overhead between `python3 /app` and getting some indicator everything is norminal, the better.
> don’t be bringing your outdated Python 3.7 sand castle to my Python 3.12 cathedral.
This is hilariously pretentious. Yeah 3.7 is EoL and if you're running it you probably need a kick in the pants to update deps, but it's far from the worst python sin.
What's actually happened is de facto, not de jure, legalization (in effect, but not in law), because of the unpopularity of cannabis prohibition. It's just not worth it in most situations to go after these products at this point.
There's still a strong need for actual legalization at this point.
Multiprocess, OS threads, and asyncio all solve different problems. Threads are pretty heavyweight compared to async coroutines (aka green threads). The big win with coroutines is it is very cheap to put them to sleep waiting on io. So a web server on a 4 core vm might have 4 worker processes, several threads per process, and dozens/hundreds of coroutines.
> So perhaps you can use this for slurping other people's IP in parallel and train the "AIs" that are supposed to make us redundant.
This has absolutely nothing to do with the technical merits of async or threads. For one, the above two examples are taken directly from work I did to combat deep fakes by identifying various "tells" from the media. Some of us are in fact using machine learning for good.
https://github.com/mypyc/mypyc
You can compile python to c. Right now. Compatibility with extensions still needs a bit of work. But you can write extremely strict python.
That's without getting into things like cython.
There are also multiple compilers (mypyc, nuitka, others I forget) which take advantage of types to compile python to machine code.
> Python itself doesn't do that
The type syntax is python. MyPy is part of Python. It's maintained by the python foundation. Mypy is not part of CPython because modularity is good, the same way that ANSI C doesn't compile anything, that's what gcc, clang, etc are for.
Mojo is literally exactly the same way, the types are optional, and the tooling handles type checking and compilation.
That's the neat part, it's not! You can distribute basically any kind of data with pip, within reason. Iirc Cmake can be pip-installed.
I'm skeptical that for the vast majority of uses, have time data in the IDs (and also not leaking it from actual timestamp fields) is an issue, and for the cases where it does, just use random IDs.
Even theoretically, is there a way to translate timestamps into a German tank problem? If I give you a sampled set of timestamps (with no other node identifiers), can you estimate the cardinality of the greater dataset?
If the UI automatically transitions to a totally new screen after completion, I'm never going to see 100% anyways, unless the app does the exact infuriating thing in TFA, which is render 100% (at 99.whatever) and then do some fsync/cleanup and actually be frozen showing 100% which is the contrapositive of oddly satisfying, it's unsurprisingly unsatisfying.
Dig was an early and widespread DNS CLI tool. "dog" is a logical name for a next-gen dns cli, and of course that exists. "Doggo" is both a pretty standard linguistic drift pattern of English slang (random -> rando, weird -> weirdo), a common internet term of endearment for "dog", and a logical derivation of *-go for go-based tools and software.
Correct answers: 1.0, 0.0, 1.0
Confidence from algo: 1.0, 0.0, n/a
Confidence on the wire: 1.0, 0.0, 0.0
Score after bug: 66%
Score as it ought to be scored: 100%
It was enough to make several algorithms which were very selective in the data they would attempt to analyze (think jpg vs png images) went from "kinda crap" in the rankings to "really good"
https://www.ajaonline.org/article/3863
> In July 2014, we conducted a survey of Pompeii’s street network to document traces of iron that were observed on the stone-paved streets, which resulted in the identification of 434 instances of solid iron and iron staining among the paving stones. ... Pompeians were—in addition to using solid iron wedges—pouring molten iron and iron slag onto their streets as a method of emergency repair.
There's a huge gulf of difference between "a civilization is capable of melting iron" and "molten iron is so cheap and easy they used it to fill potholes".
Castable iron: Valuable, scarce, energy intensive, very hard to melt (comparatively), corrodes readily (especially on the coast)
Iron and other metal slag: Byproduct of iron smelting, basically waste, melts fairly easily, was used as ballast in ships, comparatively cheap, rusts superficially but is mostly a matrix of oxides which don't meaningfully react
I'm beyond skeptical that perfectly good cast iron was used to fill potholes. Using slag/dross/failed smelts/other byproducts of metallurgy makes far better sense.
It would be like far future archeologists unearthing rammed earth tire walls and concluding "the 20th century was so efficient at producing rubber they used excess tires as a building material" vs "they used a waste product which would have been landfill anyways".
It's just game theory. It's like asking how many metaphorical empty barrels do you want to add to your Russian roulette revolver before you are willing to risk it, the reward being basically "ordinary food". Oh and the risk can suddenly one day go from just causing hives to severe anaphylaxis at a much smaller dose.
Most people who learn of a sensitivity (I learned in elementary school after breaking out in hives from doing art involving peanut shells, the horror to think this is something schools just did!) just don't want to know that badly how dire their allergy is and assume it's life threatening, because it's not worth it to be cavalier.
We dealt with a bug that for weeks was silently corrupting the results of trials pitting the performance of various algos against each other. Because a valid response was "no reply/opt out", combined with a bug in processing the "opt out" enum, also combined with a bug in score aggregation, functions were treated like they replied "0.0" instead of "confidence = None".
It really should have defaulted NaN for missing floats.
Addiction is largely driven by neurodevelopmental disorders (ADHD, ASD, MDD, sleep disorders, and many more), psychological disorders (anxiety, OCD, and many more), or both in combination. Most folks don't want to be addicts. At the heart of addiction is executive dysfunction caused by the above conditions, exacerbated by stressors. You treat it like any other mental health problem: therapy, medication, support systems, and a society that cares for its populace.