skysight-inc/HackerNews huggingface dataset:
I have plenty of wealth and no debt because I planned well over a long career. In general I get excellent value for my taxes, although I am constantly disappointed by their being funnelled into corporate welfare and subsidies for the rich. It's enough to make me cynical.
A service I run on Digital Ocean was affected by this early this morning. Looks like it was mitigated by DO - so I'm very grateful for that. Although, the service I run is time sensitive so failures like this are pretty unfortunate for me. Where would I get started with building in redundancy against these sort of outages?
ok i work 100% remote, can I claim my sisters address in Texas in texas for my payroll and actaully live in new york?

I am genuinely curious. This will save me tens and thousands of dollars every year if this isn't fraud.

why the downvotes, i don't get it.
Why would "every program" be the threshhold? There is no internal file format that every program understands, why should every program be able to deal with every filename? I could write my program to chunk filenames into words, and choke on any that it can't find in your local dictionary: "Spelling-sensitivity." It would be very bad to put that into the kernel.

It's easier to keep things simple, and rely on the program to discard things that it can't or doesn't want to use. If a program wants to insist that "Bob.txt" and Robert.txt" are the same file, that's its prerogative, although it's a dangerous assumption.
Scaling an SDR team leading to 600%+ growth and a $21M Series B
Google adds traffic light icons to U.S. maps
Three chain menus I hate:

Cheesecake Factory

Bonefish

Maggianos (really, a pocket pull out?)
Point is, you shouldn't have to "discover" anything about an interface. If it's hidden from the user, it's an easter-egg that should be nothing more than amusing, but useful functionality should never be deliberately kept from the user.

I use it all the time. I work off-shift so most of the messages I receive were sent quite a while ago, and pending when I wake up and grab my device. Knowing when they were sent is a very important bit of context.
I may be wrong, but I'm fairly sure you need to entangle the particles before they become a quantum state.
This is fantastic!!! Really well done.
Churn Analysis: How to Measure, Predict, and Prevent Customer Churn
Churn analysis is an important step in your app's growth, but how do you conduct one? And can you successfully predict user churn?
Résumé: "Achieved state-of-the-art classification accuracy on MNIST dataset by implementing a residual attention convolutional neural network with Keras and TensorFlow on Google Cloud Platform"

Reality: shift-entered my way through an interactive tutorial in Google Colab's free tier like I was button-mashing a videogame combo
Ding ding ding!

The physical size of the sensor is locked because it is tied to entire families of camera, lens, etc sizes that are very difficult to change. So that is the given constraint, and the other parameters flow from it.

It's not that they really want this size/node. It just is the optimization of what they are allowed to work within.
I disagree that they’re like exceptions. Sure they share state but that’s not a core characteristic of exceptions. Contexts leave it up the consumer to decide when to care about state changes, something exceptions definitely do not.

Contexts are complicated because concurrency is complicated. You can translate that complexity into other complexity like your Java example (to keep code idiomatic and unsurprising), but the intrinsic complexity doesn’t really go away. You can build higher level abstractions that add constraints on what you can do (eg structured concurrency) in order to hide the complexity, but that’s at a different abstraction layer than contexts.
I had a similar issue with my droplets as well. I thought I messed up something and then suddenly it worked again.
I wish that a significant portion of people today held the tech industry to such high standards.

Imagine the progress we would have made if our industry was forced into making sure that tech is extremely reliable and highly functional.

Instead, we get half baked broken things with all notions of quality and craftsmanship completely abandoned to make room for fast iterations.
I think it is! There is an incredible amount of restraint and tension in that movie. It's in my top 2.
It might have been PageSpeed that I used. I can't remember for sure. It was a long time ago, back when Google were first pushing their AMP stuff.

If it was that tool I used, maybe they've improved it since then, or maybe it works better on more complex sites. As I said, my site was very lean and dependency-free and the suggestions offered [at the time] would have made it more bloated, slower and relying on external dependencies.

EDIT: Dredging my memory, I think one of the 'problems' identified was the recommendation you've mentioned above to use more modern image formats.

Ironic because I'd only recently shaved quite a bit off the size of the imagery on the site by redesigning several of them [including the main banner] in svg format. I think Google also recommended I use image srcset [0] to optimise the images the site displayed, dependent on the end-user's screen size. That would have not only made the site bigger and arguably slightly slower but would also have required production of lots of extra image assets, whereas the svg approach I'd used actually made the site smaller and, being vector-based, svg can be served at any size required.

As I say, they may have improved the tool since then. But I got the impression at the time it was pretty crude. Seemed it just checked whether the site employed X and, if not, recommend that it should, regardless of the fact the site might actually implement Y instead, which was even more efficient.

[0] https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageEl...
My educated guess it that it is handled the same way as register renaming. Zen 2 has 180 GP registers.

For 64-bit platform, you would need some algorithm that needs more than 15 registers (so you need to spill to stack) that need to be execute faster than cache access latency. There might be some, but I doubt many would fall into this category.
You come up with a plausible story, possibly involving an automated password manager, and post it in a public forum where you mention that you have documented all the events and your honest behavior in the matter.
To be explicit here, it sounds like you're saying that you don't think you perform well on data structures questions in interviews, for example binary tree questions. Is that right?
A better name might be "Memory Operand Forwarding" since the data is probably coming from a write buffer.
Go's context package is great, but also hard to reason about. As developers, we often times like to think that just piping a context through a function chain will take care of all of your timeouts concerns for you.

Some fun context gotchas:

- Using `req, err := http.NewRequest(...)` to create an http request, and then calling `client.Do(req)` does not do anything with context, you need to use `http.NewRequestWithContext(...)`. [0]

- Creating a function that accepts a `ctx context.Context` and then making a blocking call that doesn't respect your context will still block for the entirety unless you instrument it yourself.

- If a parent context is canceled, all children (derived) contexts will also be canceled. However, only if they are explicitly checking `context.Done()`.

- And the worst of all is passing things that decide business logic in your context variables! First, you lose all benefits of go's static typing. Second, you will not realize all of the crazy places that a context scoped variable is coming from, have fun debugging that!

[0] https://golang.org/pkg/net/http/#NewRequest
I initially thought the use of circular irrigation devices would be when land is cheap, but after some research I think the main reason to use them is when water is far more expensive than land.

I zoomed in to various areas in the Midwest US, and I didn't see a single use of the circular devices, only square fields which are likely using the linear irrigation device you described.

However, in areas where water is more expensive such as Colorado, I see the opposite: Only circular irrigation devices.

I think what's happening here is that circular devices shoot the water down which causes all of it to land on the crops. The farms in my area generally use a firehose style sprinkler which shoots the water up. This causes a large chunk of water to get lost but it hits the corners of the land. Due to the cheaper water costs in the midwest, this is acceptable.
Is there perchance a text transcript of this?
Ask HN: What do you listen to when you want to be productive?
> Signal, of course if they get your keys by force, can do the same thing, just on a single client ... So there isn't any more security.

What? Keys "by force"? So if they come to my house and threaten me? I doubt that any security scheme holds up under that, yours nor theirs.

> Finally, if you have 3, 4, 5, horcruxes, then they would still all need to cooperate to get the messages in order to do this perfect XOR

I won't spend another 30 minutes making another POC but I'm fairly sure that this is not true.

Have you tried it?

If I'm not mistaken: the third, fourth, and fifth OTP are xored together with the first and second, and are therefore the same as xoring messages 2..5 together into one value and xoring that with the first message. The result of {plaintext} xor {any of them} will match the value of {xor the others together}. Therefore any of them can decide to do the attack and they don't even need to know how many other messages/channels/OTPs/horcruxes there are.
Yeah, I thought that. Though disliking Apple products isn't abnormal, making that part of your identity is sad.

Making your preference for "contrasting" Microsoft products (or whatever) part of your identity is even sadder.
CenturyLink routing issue led to outages on Hulu, Steam, Discord, more
If you enabled the posix subsystem NTFS became case sensitive as well, although most API passed a flag to disable that for Win32 file calls.

It’s interesting that Microsoft effectively added the reverse feature to NTFS [1] to support per-directory case sensitive files to be more compatible with Linux.

[1] https://www.tiraniddo.dev/2019/02/ntfs-case-sensitivity-on-w...
I didn't see it mentioned but this came up in an interview with a state head of firefightting in Australia after the most recent bushfires: he said that a big problem is there's less time of the year you can actually do controlled burns because of the warming climate.

So a warming climate is not only making the risk of fires starting higher but it's also shrinking the mitigation window.
How is this a new paradox? Isn't this paradox the whole reason for different interpretations of Quantum Mechanics?
There is no way it is true. Credit reporting agencies don’t consider your name when assessing your credit.

The only way it could be true is if it is such a peculiar name that he is constantly the victim of identity theft.
My father didnt want to have cable tv. On antenna we only got ORF (austrian television) and local one (which sucked). I needed almost 10 years to actually hear how Captain Kirk in Raumschiff Enterprise really sounds (everything is synchronized to german) like.

Side effect: I also fluently speak german.

And banning social networks is positive for your kids. Also ads.
I've recently started doing interviews for my company, and while there are definitely candidates that we have been on the fence about accepting that would probably have been a great fit, in the end, the false positive rate is more important to us than the false negative rate. Maybe we missed out on some great candidates but the criteria we used to evaluate them also allowed us to avoid a lot of very bad candidates. The perfect interview process doesn't exist, we have to make do with the fact that whatever the interview process is, we will miss out on great candidates and end up making an offer to candidates that will not work out. But indeed: for candidates, this means that you shouldn't take rejections to heart too much: you might have been a great fit for the role and a bad fit for the interview process. If you're consistently getting rejected for positions for which you believe you are qualified, maybe you need to get better at interviews, or maybe you're not as qualified as you may think.
Why no consoles?
A Crypto Megazord! Or is that too dated? :D
This is awesome. While listening to The History of Rome podcast, I went to Wikipedia to see whatever type of media there’s to see how the people looked like. For the old times, it’s of course statues, and sometimes only coins. For the late emperors there are paintings too, but fairly unrealistic.
"Hyperbolic claims aside†, I think this is a practical way to dramatically increase the security of OTP key transmission over networked communication."

I get you, you're thinking, it's safe as long as one of the channels is not tapped by the same entity. But the problem is this: You're relying on the assumption at least one of the channels is safe. The point of public key cryptography is to protect communication even if none of them are safe. The best the adversary can do in those scenarios is MITM attack, which can be detected over an authenticated channel.

"It's not perfect, but it would make any attacker's job harder, right?"

It's much easier and cheaper to hack WeChat's non-E2EE messaging app service to steal the OTP keys that decrypt the messages, than it is to break e.g. Curve25519.

"That's a chicken and egg problem for the attacker."

It's not. All the attacker needs to do is look at the metadata like TCP headers, to see what servers the device talks to. Also note that the author does not propose any remedy to this problem, especially not a single mention of Tor.

"The information on exactly where and what the other horcruxes are could be residing entirely elsewhere in a very encrypted way, or even discussed in person."

It's a bit much to assume peers are willing to play secret agent, perform periodic rendezvous to exchange OTP material etc. Also, the problem with SSS is, pieces are created on demand, in that sense using multiple OTPs is better.

"Aren't the mechanisms to transmit OTP keys -- prone to weaker security than the OTP mechanism itself?"

Yes, practically always. The only way to do it more securely is in via sneakernet, in person. This would apply even if you'd do quantum key distribution (e.g. the BB84 requires the Carter-Wegman MAC's key to be pre-shared to authenticate transmission's basis and thus that no OTP interception took place). And that's not something you want to keep doing, thus PSKs are much more usable and thus more secure a choice.
Thanks, it's interesting you see it that way - but I've never seen that view common among 'hackers'.

So, I doubt that's the factor why the symbol hasn't been more widely-used, emblematically. I instead suspect mixed-feelings about anything ESR proposes, or just more generally the fact that hackers are so varied in interests/behavior that there's little need for a shared emblem. (Though, the glider appeals to a certain mindset, who have & will use it as a symbol, as when it appeared in many remembrances after John Conway's passing.)
The code using Stripe is very minimal so you can do it yourself but if you are absolutely against it, then you can consider services like paddle or more established subscription/billing services like recurly, chargebee etc.
What’s the use case for this? I wanna be excited but I think I’m missing something
After reading this article I take away the opposite conclusion: with controlled burning these communities could dramatically reduce their risk. What would be helpful is a law requiring controlled burning for human habitation.
In Agner's forum post linked a few days ago[1], it sounded like it was quite limited. I mean, super impressive, but as far as I understood, it didn't handle nesting (just the single pointer/memory access + offset)[2]. I'm not very well versed on this stuff though, so maybe I misunderstood.

[1] https://news.ycombinator.com/item?id=24302057

[2] > The mechanism works only under certain conditions. It must use general purpose registers, and the operand size must be 32 or 64 bits. The memory operand must use a pointer and optionally an index. It does not work with absolute or rip-relative addresses.

> It seems that the CPU makes assumptions about whether memory operands have the same address before the addresses have been calculated. This may cause problems in case of pointer aliasing.

Or from the PDF:

•The instructions must use general purpose registers.

•The memory operands must have the same address.

•The operand size must be 32 or 64 bits.

•You may have a32 bit read after a 64 bit write to the same address, but not vice versa.

•The memory address must have a base pointer, no absolute address, and no rip-relative address. The memory address may have an index register,a scale factor, and an offset no bigger than 8 bits.

•The memory operand must be specified in exactly the same way with the same unmodified pointer and index registers in all the instructions involved.

•The memory address cannot cross a cache line boundary.

•The instructions can be simple MOV instructions, read-modify instructions,or read-modify-write instructions.It also works with PUSH and POP instructions.

•Complex instructions with multiple μops cannot be used.
An interesting idea, I was thinking why not use public key encryption instead of transmitting keys in plain text, but it doesn’t really make sense to do so. Breaking the public key encryption only requires the plain text or the public key (assuming it can be cracked) so horcrux would not help.

However, using a symmetric algorithm like AES could give you better performance since that would reduce the bandwidth overhead from O(h * n) where n is the size of the message and h is the number of horcruxes to O(n + k * h) where k is the size of the key.
A human insisted to his face that he provide a high school degree. As part of the hiring process. It must have been a hard requirement. Yeah, pretty strange. My Dad eventually got a copy of his diploma from the 70s and got the job.
My second thought was that go will pass the struct by value, so even if it didn’t crash that member would not have been set in the parent function.
It's a different threat model. All on one device would not gain any more security on 0-days over Signal. But it would avoid dragnets on your raw messages on the wire or in messengers that have cloud backups.
A bodybuilder like Charles Atlas or Arnold Schwarzenegger would not have been caught dead drinking protein shakes in the glory days of bodybuilding (i.e., the 1970s/1980s); they preferred real foods, and Atlas was a strong proponent of a milk-heavy diet (and even advocated for a milk-only diet during bulking phases). https://physicalculturestudy.com/2014/12/08/charles-atlass-s...

Thus, 40 years ago (i.e., 1980), using protein powder for weight loss/body composition wasn't a big market. Herbalife created that market. GNC and others started selling protein powders for weight loss and bodybuilding after Herbalife proved the viability of the niche. (Note: protein powder is the cheapest form of protein...today. It wasn't back then. It was comparatively quite expensive. In the 80s, beef and chicken were far cheaper than protein powder.)

If you want to debate exercise history you will want to pick a fight with someone who doesn't have GNC and other health companies as clients...
Entanglement means that there are systems with highly (more-than-classically) correlated state - that the combined state is something that can’t be represented by considering the systems independently - not that the states are the same. The no-cloning theorem prohibits a process that takes the state of a system and replicates it on another system. It’s certainly possible to have or to generate entangled sets of systems that have identical separable state, but not to copy an arbitrary state.
If you went to higher-class restaurants, small menus are the norm. I'm no expert, and my wife only has a culinary degree from 10 years ago gathering dust, but some possible reasons:

- A smaller menu lets the chefs focus on learning to make those dishes at the expected level of quality. These items also usually require more skill and knowledge to just be passable.

- It's not so much that fancy places have small menus, as it is that non-fancy restaurants can have bigger menus. Their kitchens can have an assembly-line style that optimizes simplicity and time, letting them hire cheap cooks. When every dish is "throw each part in the oven/fryer/pot, wait 10 minutes, put on plate," adding 50 dishes doesn't put as much strain on the cooks.
> Heh, that's funny, the documented threat model was looking at observing text, not changing it.

It doesn't really matter what your threat model is if people see "encrypted messaging" and think it's to secure chat messages....

Putting an asterisk somewhere that indicates you exclude the single biggest source of issues for an encryption scheme is like throwing a brick through Sony's window with the text on it "BY ACCEPTING THIS BRICK THROUGH YOUR WINDOW, YOU ACCEPT IT AS IS AND AGREE TO MY DISCLAIMER OF ALL WARRANTIES, EXPRESS OR IMPLIED, AS WELL AS DISCLAIMERS OF ALL LIABILITY, DIRECT, INDIRECT, CONSEQUENTIAL OR INCIDENTAL, THAT MAY ARISE FROM THE INSTALLATION OF THIS BRICK INTO YOUR BUILDING." (http://bash.org/?577451)

Anyhow, defending a broken scheme rather than just honestly saying "I had not considered that; I'll introduce X to fix this issue." also kind of breaks any credibility down for me.
Why should you pay attention to gather feedback
> I would appreciate it if companies finally acknowledged that interviewing is a two-way street.

you wanting the company to acknowledge that its a two-way street is evidence that it's not. It's very rare.

> I have cancelled way more interviews due to red flags happily waved by companies than companies have rejected me

You can boycott a business too if you don't like it, but that doesn't make it a two-way street. You have very little leverage over the business.
You should be building packages for the software, of course. If it’s some random internal app you’re chucking into a container it’s one thing, but if you’re deploying it across VMs or physical hosts you probably should put the effort into writing a rpmspec or whatever the hell Debian does (this is a large reason why I don’t do Debian-based systems, I have never been able to properly wrap my head around dpkg builds - there’s too much magic in debhelper and not enough documentation).
Not to mention the number of advertisements that take up the whole screen in the middle of the text. That plus the video killed my motivation to continue reading the story.
The list was going very well until the last bit about “No Consoles”. Now the rest of its credibility is shot.