skysight-inc/HackerNews huggingface dataset:
The UK is currently not exporting vaccines and there are no countries which are receiving vaccines from the UK.

This is what OP claimed and there is only one argument that can be made against that: a list of countries where the UK or the US is exporting vaccines. By now it should be clear to anyone reading this far that you can't provide that.
Only A and AAAA records take an IP. Everything else is a hostname. This simplifies administration, as there's only one hostname->IP config point, so you have the flexibility to resolve the rest dynamically.
If this is true then the higher you go, the more lonely it becomes.
Well, it does according to a leaked preprint someone posted on twitter that did not receive any peer review, was not published, and for which primary data is very well hidden.

For a critique of a lesser number from yet another leaked preprint with the same status that only concluded 89.4%, see https://twitter.com/ZoeMcLaren/status/1363582050775744515

The bottom line is: results are positive, but every single one reported in headlines is likely overstating.

70% RRR (relative risk reduction) efficacy is supported by data, if I understand it. >80% or <50% is not - at least not with publicly available data.
I don’t know if it’s helping but I’ve started to blend in the term safety to try to bridge that cognitive rut of security = hack avoidance.
I use it in a network video recorder. https://github.com/scottlamb/moonfire-nvr/blob/master/design...

Data in a flat file would be much less efficient, and a SQL server (eg PostgreSQL) would be more for the administrator to deal with. SQLite's a nice sweet spot.

I've thought about using a key/value database (either a BTree one like SQLite uses under the hood or a LSM one like RocksDB). It'd be faster and less total code. But SQLite's too convenient to give up. The SQL interface is nice for debugging in particular. And it's already plenty fast enough, so my time's better spent adding some glaring missing features and better UI.
I think the point here is that the "lenient" behaviour actually is a lot more complex than one would expect - a compliant mail server would need some special logic to detect hostnames that kinda look like IP addresses and handle them in a special way - without this behaviour being in any way standardized.

E.g., the lenient server would have to treat the value "10.0.0.254" like an IP address but "10.0.0.256" like a hostname that requires DNS resolution.
Thank you! Def. room for improvement there. Still wish there was a way out that could work for all sides if for whatever reasons things weren't working out ( ;
Back in the day they would prioritize high karma HN users for YC startup school invites. That’s how I first met pg.
Agreed, those are reasonable additional features. And critically, they aren't necessary for the car to function (so they could, and should, be optional).
I strongly disagree. The dominant failure modes of electronics these days are:

A) solder joint failure (thermal cycling)
B) capacitor failure (sustained heat).

Electromigration is a distant, end-of-life condition-- representing only a tiny fraction of failures of non-overvolted devices in a normal use period.

As your link itself says, in the top answer:

"But then there is an important question: How much does this decrease the lifespan? Knowing this, should you make sure that your graphics card stays cool all the time? My guess is no, unless an error was made at the design stage. Circuits are designed with these worst-case situations in mind, and made such that they will survive if they are pushed to the limits for the rated lifetime of the manufacturer. "
The problem is that you see it as one or the other as opposed to investing in BOTH solutions and trying to adopt both technologies for the better.

It seems like we should put all our eggs into one basket but why? If people realised how 'anti-nuclear' they actually were, things would move along faster.
> Lack of proper releases, testing, and versioning results in unending checkout-fu to figure out what commits for each of 20 libraries will work for each other.

Admittedly I'm basing this on my experience in a very large monorepo environment, but there's no figuring out which commits will work with each other. Every commit with every library will work, otherwise it doesn't get committed.
Yes, this involves massive CI infra and tooling to aid in refactoring.

You want to make a breaking change to a lib? Great, it's on you to update every piece of code that calls it.

It's great when you can control every piece of your infra, but I totally get how it's unfeasible (and maintainer hell) for the distro community.
Sounds like you've accepted the vendors do really need to run a service, and it can't be local, and now you're just debating how big that service needs to be.
Note that the difference shrinks to a factor 2 if you consider per capita values.

That's still bad, no argument: France splits atoms, while Germany burns lignite, and peat aside, that's as bad as it gets as far as CO2 goes.

However, that's beside the point: The fact remains that Germany did move a significant amount of electricity generation from fossil fuels to renewables.
From the abstract it sounds like the author here is drawing a false equivalence between consciousness and intelligence. Reading more into the article, it really sounds like this is the case. More specifically, it sounds like the only connection between intelligence and consciousness comes out of some pretty strained definition usage.

Digging deeper, the issue I see with this essay is that to accept the end conclusion, you have to say "I'll allow it" to a lot of tenuous conjectures.

I think it's totally fine to say that the USA may have some form of emergent intelligence, however to make it out to be an organism is strained. This essay would have been a lot stronger if the author had tried to argue that the USA has emergent intelligence.
maybe a vertical version with a support that you can have on the desk like a picture frame, with a less wide wood frame,
maybe the display can alternate showing the calendar for a few minutes and your favourite newspaper frontpage or something else for a few minutes
Yeah, I also like the ability of third parties like Teslabout to provide dashboards of your car usage. Personally, I want "personal telemetry" in all my devices: if protocols like Solid ( https://solidproject.org ) were more well-established, they'd be a great way to have this sort of functionality without relying on the vendor to store/process all the data.
> It would be nice if there was a “.example” TLD;

I don't understand what you want here. RFC 2606 reserves .example for the purpose of examples. I use it all the time for this purpose.

If you want to really register names under that TLD now it isn't an example any more and ceases to serve its purpose.
That's not the problem. (*) The actual problem is that the distro maintainers want split packages (for security and so on), not vendored, and this requirement was already burdensome for many languages other than C/C++. If vendored packages were acceptable I believe people would have of course contributed them. Maintainers made this obstacle themselves (for a good cause, arguably) and it seems farfetched for them to then complain other languages are uncooperative.

* Was "isn't that a problem?", which was not I meant to say.
Most of a wind turbine is concrete and fiberglass, which doesn’t recycle very well.
Germany, once a model, is swamped like everyone else by pandemic's second wave
Why would I need to control my car from more than 50m away? That seems like a luxury, at best. It’s being pitched in comments on this article as a necessity when it absolutely isn’t. It definitely isn’t worth also giving up control to everyone else in the world.
The successful micro-service architectures I've seen have a remarkable level of uniformity. Many such environments have standards down to the level of use this particular http lib +internal wrapper.

At the end of the day there are not large enough differences between say ruby and python to justify different teams choosing ruby or python at the same (medium-sized) company. If you have this level of difference, you've effectively permanently engrained conway's law into your organization.
Are you actually talking about static linking here, or just venting your spleen about sloppiness in software engineering practice more generally?

Because tracking dependencies in source control (specifically, checking in lock files) is tremendous for reproducibility. It means that when bisecting through the commit history to find when a problem began is not just bisecting through the local source code, but also the specific versions of every dependency.

So regardless of whether the issue you're investigating is in the package, a dependency, or an unexpected interaction between the two, you're able to find the first commit that introduced the issue in O(log(commits)) time, rather than needing O(commits * (num dependencies * dependency versions)) time.
Sounds like the plot to Metal Gear Solid 2
Honest feedback: from the photos, it looks very gray. The appeal of e-paper to me is the contrast. So having a background so gray kind of defeats the purpose for me. Maybe it's just the photo you took or the lighting though.
Yeah. Fuck scores. Downvote to oblivion baby!
All of that is traceable too. And, no. Some chinese millionaire is not going to wire you cash in return for a private key. What if you vanish? What's he going to do - sue you? This stuff only happens when they know where you live and your kids go to school.

Money laundering IRL is hard - and compared to cold cash, bitcoin is accepted in very few places so it cannot be easily off ramped

So I am going to guess bitcoin in crime is mostly like stolen artworks. Someone steals the painting and a newspaper says "20 million dollar painting stolen" and they can use it as a deposit on a drug deal (maybe at 200k worth).

At a guess bitcoins are passed around from phone to phone, part-cash part-BTC (like part cash part shares buyouts). Just the ten minutes wait for the transaction to clear probably involves people nervously fingering guns.

Of course, signal analysis helps here too. If I am right then there is a ring of transactions all of which are dirty, and if you break one through poor ops sec (same phone used for drug deal and for day trading) then you get a ton of good info. If someone used a burner phone for that one transaction then it's hard - but how many ur ed phones were turned on just once in a given city at a specific ten minute window. And now how many phones were on that same cell tower when that came online .

Yeah these things are traceable.
> surely it must be damaging to the kidneys.

Alcohol is processed in the liver, not the kidneys, and excessive chronic drinking does have long term effects.
We try to make up for it in the extreme narrowness of what we produce.
I blame companies for not doing what I want all the time. If you don't complain, you have no right to complain.
If we get better search systems I would be totally on board. But most knowledge base systems have a hard time finding similes for words let alone sorting articles containing multiple keywords in a useful order.

Having the information written down is important if nothing else than a source of reasoning going forward (people tend to remember do X but rarely why in my experience). However saying that asking a coworker is a bad thing is giving way too much credit to the documentation.

Additionally if you are talking about anything but the most basic associations talking with people is a good thing anyway as you can discuss your idea and see if there are problems the documentation couldn't tell you about because said problem would be listed in a different place.
Reading the website, it seems this product is tied to Google. Instead of using a proprietary cloud service, you should work with CalDAV instead and make it accessible to everyone.
Okay, "decentralized hypertext", not distributed. Same problem still exists: servers that run an HTTP service would need to accept and track backlink pings. This was done a decade and change ago with Movable Type's trackbacks feature and that was, as you guessed, a massive spam vector.

You can, of course, construct a backlink system by indexing pages. That's basically how Google works and is probably the only use case I can think of where backlinks help more than they hurt. In fact, your distributed link database is basically half of what you'd need to build a search engine. The other half being, of course, an oppressive antispam system. The only reason Google works at all is because they frequently adjust their ranking algorithms or shove them into piles of linear algebra nobody can comprehend. No clue how you do that in a distributed manner, though.
Yes, and they are built at absolutely ruinous costs.
Hm. So it's a build system intended for TeX files? What does it gain you over using a Makefile or similar build system?
Just stop the anti-nuclear argument please. Cost shouldn't be a thing if it means we can avoid a climate disaster.

The whole, 'nuclear is too expensive' argument was had 10 years ago with electric vehicles and look where we are now.

If cost is your main motivation to be anti-nuclear, you're hiding a bias whether you're aware of it or not.

We need a replacement for base load power and nuclear can fill that capacity.
yeah i think we are in agreement about current methods.

i guess my real hypothesis is that there are more people than ever looking at AI. we don't have the right algorithm or framework yet, and currently models probably wont iterate to it. but a hard takeoff when we do find it is practically inevitable, in my opinion. i think AI experts are limited to thinking in terms of the field as it is, or where it will be in less than five years, not what will happen when somebody stumbles on the right model.
Will CMP versions really be so single use as to be only good for mining?

I want to know if I could use one as a second card for 3D rendering. Although I guess the render farm people will know about that and suck those all up...
Nothing wrong with having good intentions but if you fixing a bug breaks someone else's software then they still have to fix their software no matter who's fault it is. Repeat for all their other dependencies and they have an endless stream of annoying little new bugs to fix.

I work on software that has dependencies probably over a decade old. They have that long history of proving themselves to be perfectly good so there's no upside to updating them and only a tedious bug-hunting downside. One of them was already abandoned when I started using it but it still had an active community of users who agreed that it was perfectly usable without any more updates despite having the odd minor bug or limitation.

That's where I hope software can end up - "finished" then sit around being stable and useful until it becomes obsolete. Other than security, I think people have a psychological problem with knowing there won't be any more updates. They always hope the next update might fix the bug that bothers them or add the feature they want. But often that never happens and they're just being strung along on hope and dripfed a few treats every now and then.
> Anecdotally, they often don't end up studying STEM subjects because they're encouraged to focus on other subjects in high school.

Definitely citation needed, there are countless "Women in STEM" initiatives, almost begging girls to go into STEM fields.
hello llimos, thanks for that
But, humans can currently learn to teleoperate robots (e.g., surgical robots) much better than AI. So, they are dealing with the same hardware, and it is hardware a priori unfamiliar to the human. Thus, at least in these cases, the difference must be in the learning algorithm.
The “s” in IoT stands for security
Home Assistant really is amazing. It has integrations [1] for anything you'd want and works on tons of devices. Hosting it locally on an old raspberry pi 3, has been controlling thermostat, lights, and (as of 2 weeks ago) sprinklers.

https://www.home-assistant.io/integrations/
yup I started my career and felt this way pretty quickly, I'm now trying to get a PhD instead, I love solving problems, so this seems like a good idea.

I'm sure there are some great companies out there, but they seem to be rare. I just see don't see work in this industry to be sustainable and I cant see myself working as a Software Engineer when I'm 30+ or with a family.
Huh. Alright then. Either way, I'd recommend leaning toward a less textured, richer/darker color and species of wood. If you go lighter, it's going to look a little washed out IMO.

Also, in your quality control for the wood bits, make sure that those mitered corners all line up evenly across the entire joint (examples of what I'm talking about highlighted here: https://monosnap.com/file/MkTzAjJhx7v7DkL5kOKypQNFKVyrNU). People who have purchased any kind of fine woodworking will see this and see something somewhat poorly made, even if the actual electronic hardware and software parts of the product are rock solid. The presence of those gaps means that one or more of the following things are true: 1) the miters weren't cut at a perfect 45, 2) the wood wasn't dried long enough, 3) the pieces were cut too short, 4) the wood was moved from a high humidity environment to a low humidity one (causing it to dry out and shrink slightly). 1 and 3 can be solved by closer inspection/better processes for the people/machines cutting the wood. 2 and 4 are harder to remedy if it's possible at all. I'd guess it would mean a new supplier + factory doing the wood bits.

Not necessarily saying that layout options would be _necessary_. Just pointing out that something more focused on showing immediately relevant information (i.e. scoped to _today_, rather than this entire week) might help to more clearly define the value of the product to a prospective buyer.
That's simply not true. Nuclear has always and is still receiving significant indirect subsidies. A huge subsidy that nuclear power gets is that plants are not insured against incidents (because essentially nobody is willing to sell them insurance), so it's essentially the state that does it. Also many argue that the nuclear waste storage costs are significantly underestimated, I mean I understand estimating cost for safe storage for thousands of years is difficult.

Interesting you mentioned France, the only project they are building is Flammanville 3 which started in 2007 with an estimated cost of ~3 billion euros, it is now estimated to go online in 2022 with an estimated cost of 19 billion euros. That's just construction cost.

Regarding the cost for decommissioning, the European commission has actually called out France for currently significantly underfunding the cost by a factor of 3 or 4.
Another option is Lingon X. It provides a GUI for launchd and includes a notification setting under Preferences > Notifications for items being added/removed.

https://www.peterborgapps.com/lingon/

https://www.peterborgapps.com/lingon/#preferencesnotificatio...
> because they're either dissuaded in high school

Any evidence for this claim? There are a lot of efforts to increase the number of women studying science and technology.
Poker is always zero sum, for me to win you must lose. That is never not true. But in Diplomacy you cannot win without successfully cooperating with other players. Yes there can only be one ultimate winner, but at any given moment in the game you need to successfully collaborate to make progress, so betrayals are much more painful. A poker bluff isn’t a betrayal because it’s not offering you anything you need or making any commitments to you.
I don't have much use for gold, either.
Considering the magnitude of the damage as well as how rare it is, is a very valid point.

And it's sometimes forgotten that 10s of thousands of people had to leave their homes.

Though some googling reveals that the main contaminant is Cesium-137, which has a 30 year half life. That will fade into background radiation long before that, even ignoring cleanup operations.

They've already reopened parts of the closed area.
Maybe she did similar things for some of her male reports?
I found this video shocking at first and then incredibly reassuring. Stable flight with an engine on fire really hit home how well designed these planes are
The author is trying to fight human nature.

Deprecating scores via cold turkey won’t work. You have to iteratively create newer scoring systems until we finally end up with a scoring system we all agree is trivial and ridiculous (e.g HS Diploma). That’s if you really want to break systems.

So take Leetcode - I’d like to see a new system that cuts it down to about 500 questions across 8 classes (maybe we can live without topological sort questions). As it stands now, Leetcode is adding more and more questions and more and more topics, so the machine gets stronger. Breaking the system requires an iterative approach in the opposite direction.

That’s if anyone’s serious about it. But alas, what is the motivation to be serious about it?

People gain their status by passing LC, or having high HN karma, so what incentive do the winners, ergo gate-keepers, have in wanting to break the system? It would take sheer principle, which brings me back to my initial point. You are fighting human nature.

We are not enlightened, competition is a breeding ground for all things reptilian that are left over from evolution.

Gets back on high horse, rides away (flings cape back so the wind glamorously catches it).
if prison is the other option, cane me silly
Well not pinning does not lead to everything that uses the vulnerable dependency to magically rebuild, just to make the builds less deterministic. The solution is not to blame pinning but to use tooling that informs about the vulnerable dependencies.
Great article, one quibble: there isn’t really a clear dividing line between batch and streaming. If you process data one row at a time, that is clearly a streaming pipeline, but most systems that call themselves streaming actually process data in small batches. From a user perspective, it’s an implementational detail, the only thing you care about is the latency target.

Nearly all data sources, including the changelogs of databases, are polling-based APIs, so you’re getting data from the source in (small) batches. If your goal is to put this data into a data warehouse like Snowflake, or a system like Materialize, the lowest latency thing you can do is just immediately put that data into the destination. I sometimes see people put a message broker like Kafka in the middle of this process, thinking it’s going to imbue the system with some quality of streamyness, but this can only add latency. People are often surprised that we don’t use a message broker at Fivetran, but when you stop and think about it there’s just no benefit in this context.
I was not on the plane so I don't know but if I was sitting on a plane and there was odd turbulence and then people at the window in front started exclaiming that the plane was on fire then I would be worried.

In addition disintegrating jet engines sometimes cause problems by shooting fragments of turbine into the body of the plane. There are very valid reasons to be worried even if you know you have one working engine.

You have contradicted yourself by saying, "someone with very little knowledge about planes (such as myself)" and also saying, "It's a failure that happens all the time." Knowing that the engine failures happen all the time is not something that someone with very little knowledge would know.

In short your comment was not well thought out.