skysight-inc/HackerNews huggingface dataset:
I don’t believe anybody on a paid plan has been suspended for using R2 behind the CDN? (I’ve seen the stories you’re alluding to. IIRC the cached files weren’t on R2)

In their docs they explicitly state it as an attractive feature to leverage, so that’d surprise me.

That being said, I’m not planning to serve particularly large files with any meaningful frequency, so in my particular case I’m not concerned about that possibility. (I’m distributing low bitrate audio, and small images, mostly).

If I were trying to build YouTube or whatever I’d be more concerned.

That being said, with their storage pricing and network set up as they are, I think they make plenty of money off of a hypothetical YouTube clone.

I do think they’ll raise prices eventually. But it’s a highly competitive space, so it feels like there’s a stable ceiling.
I’ve been on HN since the beginning. pg himself said that thank yous are fine. Empty but positive comments are not harmful.

I’ll leave my gratitude a mystery. They have my thanks, and my axe.
It's a very common term in British English (the Economist is a British magazine):

https://dictionary.cambridge.org/dictionary/english/piling
Oh wow, you're absolutely right. Somehow I missed that from the OP:

> The software company actively "polices" landlords to ensure that they comply with the rent cost it generates, the lawsuit alleges. Failure to impose the RealPage rents could lead to landlords being expelled from the organization, according to the suit.
> efficient way to discover true market rate and there is no damage by using it.

The algorithms are optimizing price instead of vacancy. I don't think we can assume these are one and the same (price and vacancy) because there are ongoing cost differences between vacant and occupied property.

As an extremely unlikely scenario, what if the algorithm determines it's optimal to rent only 20% of your listings to scarcity whales at 4 times the price leaving 80% vacant due to maintenance costs and other factors? From a market perspective, that's absolutely fine, but from a society perspective it's pretty horrible.
>But even from this remove it was possible to glean certain patterns, and one that recurred as regularly as an urban legend was the one about how someone would move into a commune populated by sandal-wearing, peace-sign flashing flower children, and eventually discover that, underneath this facade, the guys who ran it were actually control freaks; and that, as living in a commune, where much lip service was paid to ideals of peace, love and harmony, had deprived them of normal, socially approved outlets for their control-freakdom, it tended to come out in other, invariably more sinister, ways. Applying this to the case of Apple Computer will be left as an exercise for the reader, and not a very difficult exercise.

-Neal Stephenson, 1999, "In the Beginning was the Command Line"

The more things change, the more they stay the same, eh?
This is not a very good analogy. Bread is not a dual use technology like surveillance tech.

There are plenty of classes of goods that are heavily regulated. For example, explosives.
In my city for a national holiday we used to have an absolute massive unrestricted party everywhere uptown.

You'd wake up in a tree somewhere and everyone was friendly as hell. Volunteers would pick up afterwards.

Then a new mayor came in and ruined it all, locked it down, limited the area and basically killed the spirit of it.

I was younger sure but it was so much better. Applies to lots of things that get ruined.
For the sabbath issue, I'd say make the "extra" day an additional day of rest. That way you never go more than 6 days without one. It matches the spirit of the issue, no?

But you would certainly never convince everyone. :-)
Here people confidently keep repeating "streaming JSON". What do you mean by that? I'm genuinely curios.

Do you mean XML SAX-like interface? If so, how do you deal with repeated keys in "hash tables"? Do you first translate JSON into intermediate objects (i.e. arrays, hash-tables) and then transform them into application-specific structures, or do you try to skip the intermediate step?

I mean, streaming tokens is kind of worthless on its own. If you are going for SAX-like interface, you want to be able to go all the way with streaming (i.e. in no layer of the code that reads JSON you don't "accumulate" data (esp. not possibly indefinitely) until it can be sent to the layer above that).
Haven't had chance to watch the video yet, but this ~200 year old Japanese archer automata in really impressive:
https://www.youtube.com/watch?v=i5zYK9FxORI
Andy Grove moving Intel from memory to microprocessors was an excellent strategic move.

> "Business success contains the seeds of its own destruction. Success breeds complacency. Complacency breeds failure. Only the paranoid survive."

Something that Intel's leaders didn't pay attention to during the 2010s.
Execs do not permanently have jobs. Bankruptcy is a thing, and even without that, execs are fired all the time.
All Bitcoins are trackable on the blockchain, and these days you won't go far before transactions can be connected to an identifiable wallet.

If you've ever said anything like "Donations accepted at $ADDRESS", then everyone can see if anyone ever sent anything, and from there it doesn't take much work to see if you ever spent that money on anything and what else you do with it.

You can obscure things some, but the records are permanent and anything people can figure out stays known. If the authorities are after you, then they can get information from exchanges, which at this point require giving them personal information.

Cash is much more private. It takes much more effort to figure out who you gave your cash to.
Are you alive and breathing right now?

It’s arbitrary, so I say you aren’t.
There is no layered security approach that can fully mitigate malicious hardware. Even if you have a perfect cryptosystem where everything is running fully homomorphic encryption so that plaintext literally doesn't exist, you're still susceptible at the boundaries and to metadata leakages.

On real computers you're also susceptible to the hardware simply not executing your code properly and a hundred other things.

Since you can't fully mitigate malicious hardware, you have to state a more limited threat model for there to be any useful discussion.
If it helps, just think of corporations as legal fiction to help organize the business affairs of natural persons that ultimately own the profits and losses (the "beneficial owners"). So every natural human ends up paying taxes, regardless of how many layers of corporations were involved between the source of the money and their eventual spending.
Well, this kind of attitude is just sad.

Rather than imagining issues .NET has without verifying them first and then complaining, I'd like to suggest to spot check assumptions with Godbolt[0] which would be a good start (it can't show DynamicPGO, NativeAOT-specific and some other opts but is still fairly illustrative).

A more comprehensive view of produced asm can be acquired with [DisassemblyDiagnoser] attribute when running code with BenchmarkDotNet [1] (in the Java world a similar solution is called JMH).

[0] https://godbolt.org/

[1] https://benchmarkdotnet.org/articles/guides/getting-started....
We have an alternative path that works for us: get a terrible, ugly, but functional version of the feature up as quickly as possible. Preferably, the uglier the better. Skip the tests for now. Put it behind a feature flag or some other way to "get it into production" without any real users able to see it.

This lets you try the feature out end-to-end. Click buttons that call APIs and see if the right actions occur. Fix all the stuff that breaks when you first try this out.

Then show it to a friendly. Product manager maybe, engineering manager, another developer... whatever. Someone who understands you're just looking for someone to try out this feature with you.

It works now? Great. Put unit and integration tests around it. Make sure that this happy thing you have running won't accidentally break. Now make it pretty. Give it the design product actually asked for. They'll have feedback, which you can now incorporate safely because you have tests.
Or cholo house in Anaheim
Curtailment already happens routinely today for solar PV in some countries (eg Spain) - though it's due to running out of grid capacity in the right places, not oversupply on the grid as a whole. Economically for PV farms which are being curtailed building colocated hydrogen storage makes some sense.

If there's no curtailment (and if you have sites available in the country) then pumped storage makes a lot more sense.

But either way, building sufficient storage to do anything other than peak-shave is very, very, very expensive, so we'd be better off with nuclear even at a 2-3x cost overrun.
Paul Krugman, a Nobel Prize winner, does not talk well about Bitcoin:

https://www.investopedia.com/news/what-paul-krugmans-problem...

He also said: " the Internet's Effect on the World Economy Would Be 'No Greater Than the Fax Machines"

I consider Krugeman a clear contra indicator. Bitcon long... :-)
> When these males mate with females, the resulting eggs are infertile and so small that they don’t affect crops.
They should give a Russian developer like PIK or LSR a blanket licence to build scores after scores of 25 floor buildings with 20-30 sq.m. units until they plead for mercy.

These will also fly the workforce in from Central Asia.
I think that is a good question. I am not 100% but I do think you could take the algorithm to extremes and it does matter.

Algorithm A - professionally_evaluated_price + inflation

Algorithm B - average_price_of_cohort_you_agreed_to_join + 0.01

The first algorithm is super simple and is conceivably how many landlords might do it anyway and is based on value of your goods. Everyone using it wouldn't raise prices or hurt consumers. The second algorithm is basically agreeing with a cohort that you will never undercut each other and slowly raise prices. This obviously hurts renters and raises prices.
Have you considered adding a section to the readme comparing Sshx to these well-known alternatives?
Crypto has been a scam from the beginning, the only thing that's changed is the public perception after NFTs bombed massively and crypto was once again left without any use case.
The instructions are fifteen thousands words, and don't even answer all of those questions. That's worse than no instructions at all, if you ask me.

You'd be hard-pressed to call me "lazy", to be honest. I'm more than happy to dig into the kernel source to determine the cause of such a regression because I actually like doing that kind of thing. I've submitted several single-digit-line patches to large projects to solve exactly this kind of issue.

Spending a Saturday morning trying to figure out a kernel bug is quite enjoyable. Spending a Saturday afternoon trying to figure out how to submit a bug report or patch is not - especially when it is literally a 5-minute process for the vast majority of other software projects. If I have to deal with that much bureaucracy, I'll just keep my patch to myself.
Yes, it’s a very different paradigm than typical programming. By default, everything in hardware happens at all at once, unless you add what’a called sequential logic, which is clocked and holds state.
> importantly the US should switch to the metric system

Why switch to a system that is widely agreed to be worse for normal human communication than the one we have.

Fahrenheit is far superior of a system, where 0 to 100 roughly reflects the range of temperatures one might expect in the lower 48. When you are outside that range, you know you’re in for very uncomfortable weather. Celsius doesn’t give much benefit beyond the vague water will freeze around 0.

And then we get to distance. The US has a system where a foot is divisible by 2, 3, 4, and 6. Metric is only divisible by 5 or 2. It is horrid if you need to divide things in thirds.
Well that calendar has a new year's day, it's 01.1.

The problem is mapping it to your legacy calendar holiday, which like everything else is going to vary somewhat year by year.
Tmate is amazing, highly recommended. It's my favorite way to do pair programming.
I agree but if you have 3 under 5 one of them is bound to get tired and spontaneously turn to jello
Sorry for the confusion. The term Bitcoin can be used to refer to the code that runs the Bitcoin network upon which the Bitcoin currency/token moves around and is stored. The inventors could probably have come up with different names for each of those things, but what can you do?

Cryptocurrency folks do sometimes take the open source Bitcoin code and make small (or large) changes to it in order to do their work. When they do this they create a separate codebase, separate network, and a separate currency. Almost inevitably they do so in such a way as to greatly benefit themselves and to fool you.
Then argue that. I can't even begin to catalog the things that shouldn't be, that are, even tho they aren't 'the standard'.
Wants to run the full grid on intermittent energy and only one sentence on what happens if there is no wind (on top of typically no sun in the UK).

Using nuclear to compensate doesn’t make any sense. If you need to replicate your wind production capacity with nuclear (keep in mind wind, even offshore, can go to zero) and given that nuclear costs the same thing whether you switch it on or not, you might as well spare the construction of wind farms and go full nuclear.

As the author points, energy storage is uneconomical.

I am also surprised with the idea that electricity consumption will go down. With heating going electric, cars going electric, and mass immigration (hence population growth), that seems counter intuitive to me.
I've learnt that (initial) success of a sequel is 95% because of its prequel. True performance may be seen if it has another sequel, or DLC, or heck, another 3 months.
This doesn’t appear to be a response to or at all related to ISPs either owning the infrastructure or selling the service. What exactly is your point about ISPs here?
> Silicon Valley has a fascism problem.

I can imagine that if you see authoritarianism through the lens of the "constrained versus unconstrained" views of human nature a la Sowell, then it makes sense that Silicon Valley, ever so optimistic about the perfectibility of mankind, would tend towards that direction.
Will Chase cancel my mortgage, too?
Julian Assange Stop the War Interview 8 October 2011
I don't understand how Unity burns through up to a billion in revenue every single year, yet their engine still feels so half-baked and unpolished. Where's all that money going?
That… seems objectively like a bad situation for the world. It would be way, way harder to make software if you had to pay people that much.
“And we will enforce that by secret shopping you and dropping you from the service if you do not”.
Unless you've worked in games, it's really hard to understand just how massively tied to the engine a game is.

Imagine you have a web app written in Ruby using Rails with data stored in Postgres. You have a few hundred tables, millions of rows. Millions of lines of Ruby, CSS, and HTML. Thousands of images carefully exported as JPEG, GIF, or PNG depending on what they contain.

Now imagine being told you need to simultaneously port that to:

- Not run on the web. Instead be a native application using the OS's rendering.

- Not be written in Ruby. Instead using a different language.

- Not use Rails. Instead, use a different application framework.

- Not use Postgres. In fact, don't use a relational database at all. Use an entirely different paradigm for storing data.

- Not use CSS, HTML, and raster images. Instead, everything needs to be, I don't know, vector images and Processing code.

That's about the scale of what moving from one game engine to another can be like. Depending on the game, it's isn't always that Herculean of a task, but if often is. A mature game engine like Unity is a programming language, build system, database, asset pipeline, application framework, IDE, debugger, and set of core libraries all rolled into one. Once you've picked one, moving to another may as well just be creating a whole new game from scratch.
The Greek word for Monday literally means "second day". Tuesday is "third day", up to Thursday, "fifth day".
I have hated SUVs for decades, and have denigrated their owners for all that time. I prefer light, small, nippy, manoeuvrable cars with small turning circles. (Like my Leyland Mini, or my Mazda Rotary R100 of days gone by.)

So here I am, the unproud owner of an SUV, myself. I was forced to give up a nice sedan/saloon that was only two and a bit years old, with less than 10,000 of my driving kilometres on it.

The reason for that was to store the components of my wifes mobility scooter. The nicer, smaller car just couldn't hack it. The scooter-storage necessity had turned a normal 4-door 5-passenger car with boot into basically a 2-seater car with practically no luggage space.

On the few occasions when I don't have to carry the scooter in the cargo-space of the SUV, I am still gob-smacked at the amount of empty space in that damned thing. And it's only a mid-sized SUV too.

So please don't vandalise those SUVs. You'd probably find that we're in complete agreement with you if we spent a few minutes over a beer or two.
The difference is that government money is recession proof
I've never been to KitKat, though I've been past it a few times. Given the reputation, I'd be surprised if they ever allowed cameras or devices with them.
You're the one not realizing, it's that final belief that makes it a religion, that other shit you mention isn't religion, it's just world view and lifestyle neither of which are traits unique to religion. "How to live life" is not religion.
That’s still not a sufficient condition for success. Longer term the studio brand will be hurt, not least.
Doubling down on becoming a competitive foundry and becoming the western equivalent to TSMC. If their 18A process ships on time (2025), there's a chance that they could regain process leadership.
The values of SV have changed. I imagine that The Economist are
thinking of figures like Steve Jobs who once typified the Valley.
Jobs was once a highly regarded influential figure who described
computers as "like a bicycle for the mind". Later, such thinkers gave
way to a new generation of people like Mark Zuckerberg, for whom users
are "dumb fucks".

For those absorbed in the other hair-splitting/derailing thread, the
word "piling" generally means to rush in foolishly with zealous
enthusiasm (or worse, to do so without control), so the Economist
headline contains a note of subtle judgement.
It is, and that's what it's intended as. Some shows in the US do it too. e.g. Lane 8's This Never Happened shows in Oakland. But the most recent version of that had a lot of people complaining that there were lots of phone camera usage, so the sticker thing might not work in some venues.
Unity's killer feature is its C# support. It's enabled small teams to do far more in less time that they could ever hope to do using C++, and avoiding some of the nastier types of bugs that C++ game developers have to deal with.

And if you've got a team of experienced Unity developers, some who've been working with C#/Unity for their entire game dev career, switching to C++/Unity isn't the most practical option. While many concepts are similar between engines, you're going to be back at the bottom of the learning cliff for a while.

It sounds like Unity isn't really the problem in this case, it's more about too many polygons, poor use of LOD, and sub-optimal batching (too many draw calls). It was probably more of a time pressure issue than a tech issue, as game development is usually a race against the clock.
It usually isn't. Jevons Paradox.
The large documents are often fixed by using mmap/virtualalloc of the file, but Boost.JSON has a streaming mode and is reasonably fast and the license is good for pulling into anything. It's not the fastest, but faster than rapid with the interface of nlohmann JSON. For most tasks, it does seem that most of hte libraries taking a JSON document approach are wasting a lot of time/memory to get to the point that we want normal data structures, not a JSON document tree. If we pull that out and parse straight to the data structures there is a lot of win in performance and memory with less/no code, just mappings. That's how I approached it at least.
Kant famously "derived from basic moral principles" that it's acceptable to kill unwanted newborns provided they are born out of wedlock. Make of that what you will...

Edit: Polemics aside, I looked it up and of course people don't agree if Kant really meant it that way. https://doi.org/10.1515/agph-2021-0034
It doesn’t take the maximum. It says I have 14.53 bits of identifying information, however the max listed is my time zone offset providing 8.24 Bits of identifying information.
Can someone give some background on what these things are, for those of us new to this?
Heating can be quite significant. I guess whether or not it’s economically significant depends on your cost of generation. There was a mega-outage which cut off Italy when overheated, sagging cables, struck the treetops in the middle of either another random outage or some scheduled maintenance. It’s been many years since I read the full report on the incident (which was excellent) but there was some great data in there about degrees of heating vs degree of sagging.
> Chase monitors your political activity

This is a big claim. It should have big evidence to back it up.
I think my next pass at it will be to merge the MD5 and SHA-1 steps so that we get two outputs at the end, this way I would save on the file-reading.

But after that, I think one percent of the end of the file. Then ten percent of the start of the file, then ten percent of the end of the file ...

Given that metadata is typically at the end or beginning of a file, those seem like the best place to look for differences.

I would be open to other hashes so long as they were drop-in easy. I'm not concerned about malicious, forced collisions because they would have to overcome two different kinds of hashing, and the most it would earn is a delay, since there's always a byte-by-byte comparison at the very end.

I suspect I would similarly want to use multiple fingerprinting methods for the visual characteristics of an image file.
There's no real reason for that. It just happened like that. These aren't the only bad decisions made by JSON author, and not the worst either.

What you can do is: write comments using pound sign, and rename your files to YAML. You will also get a benefit of a million ways of writing multiline strings -- very confusing, but sometimes useful.
Note that this attack only works if you don’t enroll an additional password to unlock the TPM (see 5.3 of your linked paper).
Handing someone cash does not create a public ledger entry
This is also transitive: if I get bitcoin from you and two weeks from now the cops show up at my door asking to know why I had a funds related to some crime, I have to convince them that I had no knowledge of the transaction a couple of steps back and even if I do I might find that vendors stop accepting anything in that chain or start buying insurance to protect them. That’s going to sour people on the experience real quickly.

Variations of that show up everywhere: your employer can review your political donations or decide you spend too much money at the local bar, casino, or anywhere else they don’t approve of.
Yes. Or at least not past the next ad. No problem buffering up to the following ad.
Lawnmowers also kill people outright, about 90 people a year which is way more than bears: https://www.newsweek.com/lawnmowers-kill-more-people-bears-s...

I actually went to school with a kid who was run over by a lawn mower. He survived but it chewed up the side of his leg and left him with a limp. I think he was lucky he could still walk at all.