skysight-inc/HackerNews huggingface dataset:
There’s a multitude of options here for various floor plans. One of the classic solutions is an external fire escape which is cheap per apartment and isn’t impacting floor space. People may dislike the aesthetics though.

Construction costs scale to the market segment you’re targeting. It’s common to aim up market with new housing but the cost of marble isn’t the same as the cost of housing. So be careful you’re looking at the minimums not what it takes to attract high end buyers.
> not only fire that’s a hazard, but a personal safety thing

Affordable housing. Every edge case preference accommodated. Pick one.
Obviously AWS knows how much it costs to run all of AWS. But that doesn't translate to accurately knowing the marginal costs of a gigabyte of outbound traffic. They probably do know, but it isn't necessary at all to determine their profit, or to set their prices. "Just" set prices to what the market is willing to pay, and determine profit as total income minus total expenses over the whole operation.
We (UK) had banned those materials too until the tories decided to unban them because many of them are also property developers.
> However, that may very well change with fair queueing.

It doesn't matter what kind of queueing system you put in place. No matter how fancy it is, and even if the queue adds negligible overhead, if your average request arrival rate is higher than the average handling rate, your queue will grow unbounded. Then, for some requests, the system will appear to grind to a halt.

There's no way around it. A priority queue just means that high-priority requests get processed faster. Low-priority requests might end up never getting handled.

Here's a concrete example. I've got a web service that requires a login. I'm using bcrypt to hash passwords with a sufficiently large work factor that I can only hash 5 passwords per second and have a queue for the password hashing. If 6 people are trying to login every second, then after 1 minute, I will have received 360 login requests. 300 of them will have completed, but the queue has grown to 60. Anybody trying to log in at that point will have to wait a minimum of 12 seconds to get their login processed.

But what if I also have users trying to sign up? I have to hash their password, so those get added to the queue as well. If I prioritize logins over signups, then under my scenario, a signup will never complete.

There's really nothing that can be done. An unbounded queue means unbounded latency. Eventually, a login request would have to get rejected just because the queue is full. Of course, in the real world, this creates frustration for the user. They'll either try to login again, or give up.
> Even an ultra-light HMD gives the Glasshole feeling, besides not being comfortable to wear.

Which have you had experience with? And, do you believe whatever you wore was as good as it gets?
I have dodged most problems with speculation by executing the branch early, before the next instruction can enter the execute stage.

That's one of the reasons why I have very simple branch conditions. E.g. I don't have the MIPS / RISC-V "branch if two registers are equal/not equal/...", only "branch if register is zero/negative/positive/..." - which saves gate delay (if ever so slightly), and makes it possible to invalidate all the following instructions in the pipeline without needing a branch delay slot or advanced speculation logic for instructions that have already entered the EX stages.

In the diagram, as much work as possible is done in "Branch 1" (before register content is available), e.g. calculate the branch target address. All that is done in "Branch 2" is to compare the register value to fixed values (zero and -1) and check the most significant bit (sign bit), and based on the branch condition (from the opcode) determine if the branch was taken or not.

(There is some extra trickery going on in order to handle branch prediction - mostly in parallel to evaluating the branch condition)

Thus, the branch misprediction penalty is three clock cycles.
Which in practice might mean "ask the lawyers."
You (Might) Only Need a Microcontroller (and a Server) for Computer Science
I feel this really underplays the proper way to purchase health care, the importance of relationships and the quality of having great providers.

I would compare this to my first dog vs my next dogs. The first dog I took him to the low cost clinic to get shots and did minimal cheap health care for him. But as he got older, it became clear that when you start having complications you need to see the same person and you can’t just skate by with different vendors and there is a lot of value to being seen repeatedly by the really highly qualified person as you get older or know where to go if you have an emergency.

It’s totally true that you can negotiate and find cheaper prices on things, but like the best veterinarians, the best doctors generally accept the top quality healthcare usually BCBS and aren’t going to discuss or negotiate price with you. They didn’t spend a decade in medical school to deliver transparent billing.

I’m all for transparent billing and think it should exist, but my health is too important to try to fight some philosophical price battle and I want the best.
Is Elon specially promoting Mr Beast's recent video?
It's true, not everyone has the same priorities, and Rust may not provide the right set of tradeoffs when one is deciding which language to use. I don't believe that C is strictly inferior to Rust. There are cases where it's not worth trying to use Rust instead of C.

Unsafe Rust is more complex to use than C in some ways. For example, an iterator for a slice, which contains two raw pointers, relies on the lifetime of the array it refers to lasting longer than the slice, and to encode this you need to use PhantomData [1]. Things like this make it look more arcane than plain C, simply because in C, this is implicit, and on the programmer to enforce.

[1]: https://doc.rust-lang.org/nomicon/phantom-data.html
> By doing the tasks that don't require as much specialism, across more vendors.

At which point your analogy breaks down, because nobody was objecting to that. If you need to buy metric wrenches for iOS and imperial wrenches for Android, but you could buy either of them from whoever you want, nobody is paying a monopoly rent for wrenches. Or to drop the analogy, you have to write your app for two different system APIs if you want system-specific behavior, but c'est la vie.

The issue comes when someone both wants to charge for access to something like that and preclude anyone else from creating an alternative, which is the analogous thing to what creates the need for right to repair. It's not just that you need to learn how a BWM differs from a Ford or a Toyota, it's that they encrypt or otherwise purposely obfuscate the bus and then purposely charge a fee designed to drive independent mechanics out of the market and force customers into the dealership, or don't sell the tools necessary to do it at all.

If Apple was charging 30% but there were viable alternative means to install iOS apps without paying that, nobody would be objecting to it because they would just use the alternative means. But they do that and preclude alternatives, which is the problem.
Any chemotherapy that damages the immune system should be avoided.
The fact you asked that, that is. THAT is what I mean.
https://www.reddit.com/r/AskPhysics/comments/15o0fx7/i_just_...

To be fair, her criticism isn't that LIGO itself was fake, but it's really hard to tell, from the video and from https://backreaction.blogspot.com/2019/09/whats-up-with-ligo...
If you read that blog, you can see she is using a collection of rhetorical techniques to cast down on the LIGO results (for example, using the term retraction out of context).

But it's mainly her videos about health-related stuff that doesn't have good support. She approaches most of these things with a "assume a spherical cow" approach, common when physics folks try to do biology.
Definitely, and I hope for his sake that's the actual explanation, and that it's sincere.

That is, while we're talking about a specific person here, that person is someone I have zero connection with. I hope all the Hanses around the world are working on themselves with good intent. That's obviously untrue, but I can still wish it.
The distinction is really not queues or not but unbounded in theory or not. There are queues everywhere, connection pools, unparsed messages, packets in flight, memory for calls sent out and not yet replied or timed out, etc. but one unbounded (in theory; they are never unbounded in practice) queue can make your system go from robust to fragile.
Pinboard Bookmarklet – Use text selection for description
you don't know his emotional state, he could have very well passed that high bar internally.

From my recollection, his wife was sleeping with another man, or there was some conflict between the two that was related to another man who I _think_ was supposed to be a friend to them both.

it's been a while, but the point remains, he very well could have been in a state that allowed him to "pass that bar".
The surrounding text explains that several CAs didn’t like having to spend resources doing revocations and intentionally made the disclosure process more onerous.

Responsible disclosure is a courtesy that should not be extended to bad faith actors.
The way RSA key exchange has been implemented everywhere involves padding. RSA-KEM[1] has been available since forever and no padding is required, though no one uses it for some reason.

RSA-KEM is also trivial to implement as it's virtually identical to textbook RSA, with the sole restriction that m has to be randomly sampled from 1 .. n-1. The shared secret (technically, the encapsulated key) is the hash of the randomly sampled number.

And just like that, no padding oracles or the headache of implementing padding in the first place.

[1] <https://en.wikipedia.org/wiki/Key_encapsulation_mechanism> , <https://datatracker.ietf.org/doc/html/rfc5990>
I'd agree with the sibling comments that physical keys are probably still the best option, along maybe with the realisation that without some sort of trust root based on human contact, things don't work.

Case in point: we actually have an extremely widely used 2factor system which appears to be working reasonably well for several decades now, despite constant attacks and strong incentives to crack it: Debit cards, PINs and ATMs. Even with the constant threat of skimmers, there hasn't been any mass events of emptied bank accounts so far.

Why does it work? My hunch is that two factors play a role: 1) it's based on a physical token, so any attack is necessarily local and needs "people on the ground". 2) there is actually a robust system for recovery and revocation in the shape of bank branches that you can visit, which involve human staff who can apply common sense judgement. Those make the event of a lost card into a nuisance rather than catastrophe.

And maybe the second lesson we can learn from the breach: Entrusting the entire collection of passwords of your digital life to a single 3rd party and then allowing that party to upload the passwords to the cloud, in plaintext, does not just superficially appear to be a bad idea that is actually genius because of crypto magic, it is, in fact, a really bad idea.
Quest 3 is $500, not $1000 and needs no external PC. Your choice of game is equally bizzare.
I don't think customization is a chief selling point, not for 99% of people. It's only a selling point for the types of people who talk about the selling points of operating systems.
It can be preferable to having your body slowly town apart by its own immune system.
Agreed and to clarify:

> everything in inches, foot pounds, and what not doesn't translate very well internationally when you start outsourcing

It translates pretty well for the last 90 years:

In 1930, the British Standards Institution adopted an inch of exactly 25.4 mm. The American Standards Association followed suit in 1933. By 1935, industry in 16 countries had adopted the "industrial inch" as it came to be known, effectively endorsing Johansson's pragmatic choice of conversion ratio.

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

See also the paragraph above referencing the precision tools enabled by Swede Carl Johansson's "Jo Blocks." For a nice video/contextual storytelling, see Machine Learning channel's Origins of Precision: https://www.youtube.com/watch?v=gNRnrn5DE58
Do lathes actually wear out? Machine tools are built like tanks and could probably last until the end of time, you just need to replace the bearings and motors occasionally.
Fossil fuel plant leaves families with 'barely enough water for your toothbrush'
> There has been a monumental growth in traffic on X despite all the exodus.

I need you to back that up, because everything points towards the exact opposite of what you're claiming.

https://techcrunch.com/2023/10/17/one-year-post-acquisition-...

Either you're using some alternative version of Twitter, or you're making stuff up.
I've always loved this idea since hearing the Swift Navigation founders talk about it in their Kickstarter video: https://www.kickstarter.com/projects/swiftnav/piksi-the-rtk-...

Glad to hear there are people still working on it.
I'm glad we'll be saved from bullshit facts with bullshit citations to bullshit articles.

This isn't hypothetical. We already have bullshit citations and bullshit articles today. The only thing remaining is to stick the two together.
> I'm imagining a backend database of creator-submitted content. The LLM runs RAG on it, pays the creators it relied on to synthesize answers a microtransaction.

That sounds like you're describing Mechanical Turk? (And also "let's train an LLM on Reddit/StackOverflow). Problem is, the humans in Mechanical Turk loop were economically motivated to outsource to AI even before LLMs.
Why do I feel there is a parallel here to Boeing? (Maybe that was the motivation for the submission)
Teach your clients to handle 429 with gradual back off/retries and it works well. Even teach your web UI to degrade under partial failure of widget loads.
The Maverick has about 1/3 the engine/motor power and towing capacity of the cybertruck. I mean, it's a successful vehicle, and much more affordable. And there are very legitimate concerns with EV range when towing. But a lot of your intuition about "power", "durability", "towing anything heavy", etc... seem pretty misinformed. On paper the Cybertruck is a monster. It may fail for other reasons, but certainly not checkbox capabilities.
> However, several CAs disliked having to revoke all those certificates, because it cost them staff time (and hence money) to do so. They went so far as to change their procedures from the standard way of accepting problem reports (emailing a generic attestation of compromise), and instead required CA-specific hoop-jumping to notify them of compromised keys.

Maybe the baseline requirements need to be updated to require an automated mechanism for reporting key compromises. CAs have to revoke certs with compromised keys, but by going out of their way to increase the barrier to doing so, they're clearly not complying in good faith.

The ACME protocol (Let's Encrypt) makes this simple - just sign a request to the revocation API with the cert's private key.
Querying BigQuery from Postgres with extensive push-down
But how do you sync on Obsidian? Obsidian Sync?
I noticed a potential licensing issue Home Assistant may have when it comes to relying only on an external package source host like pypi and complying with a plugin takedown request.

If home-assistant receives a GPL source code request(for example due to many of the python libraries in the home-assistant docker images being GPL licensed) wouldn’t the source code to all library dependencies(including the source for historical dependencies like any plugin taken down after a release) need to be provided for 3 years(due to the combined home-assistant application effectively falling under GPL requirements) from the date of last distribution of the home-assistant docker image?
More has come out since the trial (and mostly on account of Reiser himself making very hard to walk back claims on the record in another court case).
Infrastructure engineer here, but have worn many hats so far. Started using Vim writing web SPA applications, still using it as my main driver for all writing; which is mostly go, shell and terraform.
Ok. I missed that there’s a filter step that compounds the problem. The more I read the less this sounds like a bug and more like application code is missing a shrink_to_fit and was relying on a pessimization.

That being said, it’s also not an unreasonable expectation on the user’s behalf that the size and capacity don’t get crazy different in code as innocuous and idiomatic as this.

I wonder how the open bug will end up training itself.
> customers would switch

Would they though? Side loading exists on Android, but good luck foregoing the Play Store for some third party store or even marketing yourself. It exists, sure, but it does not eliminate Googles similar (but weaker) value proposition.

Would the possibility of side loading put pressure on Apple to be more competitive in terms of fees? Possibly, but Apple users tend to be less adventurous.

For Apple, there are various other reasons not to open up, like the brand image. It is really hard to make a naive user (like a child) completely screw their iPhone. Also, remember when porn videos were all Flash, and the iPhone could not display them? Steve Jobs literally told people to buy an Android phone.
Value blindness is the bane of my existence. Thin walled plastic everywhere. Things are difficult to clean because they are filled with grooves, because you need grooves and bends to make thin walled plastic stiffer. A very good criteria for quality and value is: how easy is it to clean? If it is hard then you probably are dealing with a low value disposable product. Consider porcelain, lasts forever, cleans beautifully and does not stain. Or spoons made with solid stainless steel. Spoons made with thin sheet steel often have bends and corners as to make the thin sheet stiffer. But then dirt accumulates on these corners.
How about: Don't harvest and sell my data, and don't show me a bunch of popups about exactly what data you can collect on me?
Those look a little like the Mansion Blocks we have in London - https://welcomehome-london.com/architecture/mansion-blocks/
I just tried the demo, and it looks great! Congrats on the launch!

I have a couple of questions:

1) How often do you find that the LLM fails to generate the correct question-answer pairs? The biggest challenge I'm facing with LLM-based evaluation is the variability in LLM performance. I've found that the same prompt results in different LLM responses over multiple runs. Do you have any insights on this issue and how to address it?

2) Sometimes, the domain expert generating the test set might not be well-equipped to grade the answers. Consider a customer-facing chatbot application. The RAG app might be focused on very specific user information that might be hard to verify or attest by the test set creator. Do you think there are ways to make this grading process easier?
Scientists created a 'giant quantum vortex' to mimic a black hole
ClickTeam Fusion 2.5 (the Five Nights at Freddy engine) is a "no code" game engine where you define interactions between the different game parts with essentially a big spreadsheet - your son may be able to tinker with it and realize his ideas in it easily.
At AOL there was a weekly queue depth review meeting that led to hardware ordering requests. Worked great till the business stopped growing.
Reproduction is not the goal! Making papers is not the goal! Making useful models is the goal. And having open source models is by an enormous degree more useful thing.

I see you’re someone else, so I’ll ask you too. Do you actually have any experience doing this? Have you ever fine tuned models or tried to change architecture or put a piece of one model into another?
From a naive perspective, it seems that true research/advances in AI (methods of training, etc) aren't necessarily related to model size. It seems that the goal of "building a big model that everyone else converges to because the training data is the same" doesn't have all that much value, especially since you could wait a couple years, do it all for a fraction of the price, and catch up immediately. Meta doesn't have an AI product yet, so it's not like they would be loosing money.

I suspect this is more about talent attraction/retention.
It's not really any more funny than suggesting that Meta and Microsoft manipulate teenagers with dark patterns. But with Apple it's different, so I guess we won't be ready for that discussion until next time.
AI for Economists
Apparently he went to North Africa and Italy. Plus he was what would be called a rapist today.

Mind you, I don't know if this is a reliable source.

https://thefederalist.com/2018/09/18/time-left-stop-idolizin...

I'm not really a fan of applying modern standards in historical contexts. Times change, but even today the age of consent is 16 in the UK. Condemning him for being 30+ and having sex with 15-16 year old boys just doesn't make sense to me. It seems people try to apply American puritanical standards to a historical person from Europe, who lived in the 1800s Victorian era.

If we were to apply modern standards, you should be condemning over 1B people around the planet for following the teachings of a 30yo+ guy who married a six year old girl.
This is the best article on the problems of airborne wind energy. It is 10 years old but I think
Michael Barnard did a great job explaining all the variants and why it is hard
https://czmphorfqgktmzxu.quora.com/Airborne-wind-energy-a-co...
synology has this with their NASes. Makes spinning up your own private cloud simple.
That is of course the ideal, but what, you're just gonna trust them?
Yeah, you and me both. I acknowledge it's a lot easier for me to wax philosophical about some person I don't know, safely far away in prison, and with almost zero chance our lives will ever cross. If he were my son-in-law, or dad, or neighbor, the issues would be way more complicated.
Indeed. My old Intel Atom netbook just doesn't handle modern web at all. Even sites with just text such as Medium are unusable. I guess all this at least makes modern web developer experience great since as an user I don't get any benefits?
There's something really cool about adding servers to a borg by tossing them into the ocean. Imagine a solar powered buoy with some compute and storage, with full connectivity to the internet, just floating around in the ocean. And then imagine millions of them all collectively forming a decentralized cluster.

Maybe it's just me, but I think that'd be awesome! The limiting factor is power efficiency and battery tech. Of course maintenance would be a problem, but not with fault tolerant clustering designs. And there's the ecological issues of tossing hardware into the ocean, but at least there's no need for a cooling system...
I don't think anyone should have to estimate damages for DMCA. Damages are not an issue, it's still your copyright.

Instead, this seems like a completely bullshit copyright claim. That's what the ideal fix should be.

There's zero incentive to not do DMCA takedown notices, what are the consequences of getting it wrong? It's a great tool to intimidate anyone doing something you don't like. Haier has a legal team, this developer has nobody.
What's somewhat interesting is that at both very low and very high income levels, the % of stay-at-home parent is higher. So for people near poverty, or people making top 1%-ish income, it's less than a 2:1 ratio, more like 35-40%. For middle income like $40k-$100k, it's more like 3:1 or 4:1.

At no income level is it lower than 20% stay at home parent though, so not too much of an outlier in any case.
As I sit here getting chemo for B-Cell ALL, most of us don’t have any other option, it’s chemo or death.
https://hypermedia.systems/client-side-scripting/