skysight-inc/HackerNews huggingface dataset:
This is the cause of a split in failure situations.

Failures fall into two often very distinct cases:

1. Failures the end-user is able to understand and in some circumstandes to fix themselves. Examples: (HTML) page not found, no connection, etc.

2. Failures the end-user is in no case able to fix; it's up to the programmer. Examples: Server misconfigured, missing media files on server, etc.

It never makes sense to display the full error messages in case 2. It suffices to hide the error and perhaps make it available in DevTools. Often a good way is: give a generic message, and because some failures are transient, tell the user to retry. Also it can make sense to add an error number so that the end-user can give support the error number.

So it is useful to let the browser be lenient with HTTP status codes except in some specific cases which the article does mention (HTTP status code 500 for JavaScript files, for example).
> What's wrong with patch email chains?

The fact that it's email. There are two categories of problems with it:

1. It's been extended unnecessarily and implemented poorly. The biggest one in this category is HTML email. It's really hard to write mails using common clients without messing up mailing lists. Another problem is how badly email threading is displayed in these clients. Email UI is still abysmal.

2. Many features of emails are an afterthought. Email obviously arose when E2EE, privacy features, attachments and spam prevention were not big concerns. When they got eventually added, they added too many moving parts, complexity and lack of enforcement. I wish there was a modern successor to emails (immutable federated messaging) with less components, standard and mandatory E2EE and signing, built-in list support and spam management features.

None of this is to say that git did it wrong. Even with all these problems, I still prefer the freedom offered by email to being tied-in to specific platforms.
Yeah, I may have sacrificed clarity for concision in this case.

To answer by way of example, if you are given "add R1, R2, R3" rotating to the right will result in "add R2, R3, R4". As another example, rotating "mov LR, R0" to the left will give "mov R12, SP".

In other words, rotating right changes every register RN in the instruction to be the register R(N + 1). Left changes RN to R(N - 1).

My hope was that if it was not clear from reading, it would be after testing things out. But hearing that this may not be the case is helpful feedback!
> Does Amazon have any policies against offering AGPv3 software as a service?

Each use of AGPLv3 licensed software has to be reviewed to ensure that the obligations of the license can be and will be met (and also screen for cases where it is known that the vendor of software does not prefer a company like Amazon import the software under a FOSS license). Today we use AGPLv3 licensed software internally, and include AGPLv3 licensed software in Amazon Linux (Ghostscript, in particular).

> Does Amazon contribute funding back to the software projects they offer as a service?

Yes, in varying ways. For example, it is not easy to provide "funding" for something like Apache Kafka. You need to have people working on the upstream.

> Does Amazon contribute code changes back to the software projects they modified when offering them as a service?

Yes, but not all changes are appropriate for upstream.
>The Hubitat hub has now almost entirely been replaced by a HomeAssistant virtual machine. The only reason it is here is to connect the Z-Wave and Zigbee devices I have. However, I replace those devices with WiFi versions wherever possible

There's cheap and reliable ZigBee/Z-Wave/433MHz USB dongled antennas you can replace the Hubitat with.
Just figured it out. If you select "Adjust Difficulty" and increase the max gadget size (number of instructions that can fall at once) you change their order with these keys.

P.S. thank you for nerd sniping me with this game, I love the idea and execution (pun slightly intended)!
Do you have a source for that (or are you affiliated)?
I have this "one weird trick" that I think is great, but somehow no-one else wants to use:

At one point I worked with a fellow dev where we did PR reviews just as commits on top of the branch. So you'd check out their feature branch, run the equivalent of 'compare working tree with <main>' for your editor and then look through the changes.

Because you're comparing the working tree you can leave comments... by typing source code comments (we used '// RVW(jauco)' to mark them). You can fix typo's just by, well, fixing the typo and you share the review by pushing to the branch.

I found it to have the following advantages

- PR comments usually break when you rebase or merge (because they reference a line number). These obviously won't, at worst there will be a merge conflict that you handle the obvious way.

- If your PR comment requests explanation then the answer needs to be moved from the PR to the codebase, for future use. Writing comments in code means that you just need to clean up the conversation into a comment (or you can just leave it)

- You can use a proper text editor for writing the comments

- You can use code navigation while reading the changes (like, go to definition etc)

- Because of these the review gets a more active feel. You're more inclined to engage with the code rather then just reading it while leaning back in your chair

However, people tend to look at me like I'm crazy for suggesting something like this. OTOH tools like this look completely crazy to me. Why do all this work to get a worse version of something you already have?
But it now has a feature to integrate seamlessly with OneDrive, linking or replicating a folder on the user machine. Hence, I expect it has the same limitations in terms of naming.
I would love to see an analysis of the original source without the attempt to try and critique and ‘improve’ it
it's not quite just a "better vimscript" language it's an incompatible language, if it was just improvement on top of the existing vimscript it would have been fine i think but what people are complaining about is if you are going to break compatibility why not choose an existing language like lua
Google and Universal Discuss Making an AI Tool to Replicate Artists' Voices
Obl.ong, Free, quality domains for all
I skip the script and (if they bother asking) tell people I have a really good scanner, a really good pen and am incredibly consistent with my signature even when I sign totally different sizes.
Almost all ISPs use Serial and (optional) PLOAM to authenticate your ONU. Nokia GPON SFPs allow you to change almost everything that is exposed to the ISP for authentication. ITU standards mean that ISPs have to work according to the spec.

ISP ONUs are locked for easier management for them. They will give you 1/10th of the speed promised if it helps them deal with support calls remotely rather than visiting your place to fix it. Support calls where people complain for things like 'I forgot my wifi password' cost ISPs a lot of money. So they can basically just login to your ONU at any time remotely and change settings for you like your wifi password. They do remote firmware updates and what not remotely. This is the biggest reason why ISPs love such modem router combos. Support can be guaranteed with a phone call to fix your wifi for the average Joe.

You will not get ISP support if you use your own ONU but if you are using your own ONU then you are already at that point where you know what you are doing. As far as signal issues are concerned, like I said ITU specs mean they can see the signal strength remotely. Everything else they don't have access to but you don't need them to have that access. You can always swap out the ISP provided box to troubleshoot.

If you actually swap out the ONU to a better one, chances are you'll never need to call your ISP unless there is a fiber cut or some serious signal loss somewhere.
We’re working on this at https://radicle.xyz — a blockchain isn’t needed
Open Source and HashiCorp (2022)
> distros don’t follow upstream as fast as possible

Well yes, the testing is of course part of the 'as fast as possible' part. But I could've made that more clear indeed.

> many buggy patches or issues that never got a backported

I have yet to see those in CentOS. But I guess we won't be seeing a lot of CentOS at all in the foreseeable future :p

> many buggy patches or issues that never got a backported

I feel like thats mostly on them. There is a huge temporal overlap between LTS versions and you should have plenty of time to test. I think I'd rather dedicate one month every year to fully test and then roll out a new LTS version than be interupted by unexpected updates at random intervals.

That being said: What a boring job it must be to backport security patches all day.
https://archive.is/20230811032308/https://www.nytimes.com/20...
Texas Central and Amtrak to Explore High-Speed Rail Between Dallas and Houston
>It's popular to hate on Firefox,

I don't hate Firefox, I hate Mozilla.
How to make better use of Brainstorming
Too bad the metaverse is dead
Power cannot be generated without an environmental impact. Even solar panel and wind turbine generate a non negligible amount of pollution when produced, and a non negligible amount of waste when they have to be decommissioned.
Also, it is highly unlikely that he is using his own grid, he probably pulling most of his power from the U.S grid, which (like most grid to be fair) contains a fair amount of CO2 heavy sources.
And that is not even talking about the amount of pollution and waste used to produced all that hardware he is running.

I get it, it looks cool and damn fun. I dream of this kinds of setup. but brushing off the environmental impact is also wrong.

Now admittedly, he is but a drop in vast ocean when it come to pollution and waste, and there is definitely far worse offender. But keeping our environmental impact in mind should be a necessity in this era.
What's a bit sad is that now with Zig/Idris you can finally easily make a type checked printf but in the meantime Python use fstrings which are much more ergonomic than prinf and AFAIK you can't make statically checked fstring in Zig nor Idris..
I think Zambyte just wanted to let the GP know that the code for the original had already been released before this one. No need to be mean.
One China real-estate empire just weeks from $199B collapse dwarfing Evergrande
Lack of Windows support is also big no-no.
A slight difference though. If a newbie picks up grandpa's chisel, it doesn't get glued onto their hand until they google the three magic words they must shout to make the chisel come off.
Oh, my bad, I misread your question.

See a reply to your original comment: it changes the order for gadgets larger than one instruction. The default is one, but originally it was three, so the instructions stuck.

I will make those confusing instructions only show up when the gadget size is greater than one! This feels like a good change to make based on this feedback.
No-one forces you to use the license in the first place.
I'm not sure about the places per se, but I've learned to do my own homework on hours and closing times.
There's radicle.xyz, although it seems like they abandoned their old GUI and moved back to a CLI for now.
Declarative blocking is the weakest, it barely removes the simplest ads.

uBlock doesn't exist for iOS because it is made impossible by apple, their extension API is not a "full" API.
If you leave the comments, doesn't the code get cluttered?
If you remove the comments, don't you lose information?

I could see this being useful if there was a script, that moved the comments out into either the commit message or a separate file.
This is kind of the point, in that tying art to the need to make a living used to severely limit the production of art. As we saw this difficulty being overcome, we saw an explosion in artists, and a whole lot of those unable to get paid for their art turned out to produce amazing things. Van Gogh being one of the obvious examples coming out of that.

But even before that I'm not convinced that about your claim. I'll concede that most artists whose works have survived for a period will have done so for patronage, because others will have faced severe limits on production. E.g. Haydn being able to be a court musician for the Esterhazy's ensured his work was played in front of an audience and associated with status, and so secured it distribution that someone composing and playing in less privileged positions did not enjoy (and indeed that Haydn himself did not enjoy at the start of his attempts to make a living as a musician after he could no longer sing in a choir).

For large parts of time we can expect most art to have gotten lost because it was not written down and recorded, or because it was produced or kept in ways that hampered its longevity.

E.g. already under the Chinese Tang dynasty we know that art was seen as an acceptable pastime and that while patronage happened, it was not a particularly desirable job, to the point that one of the earliest known Chinese painter was by a man - Yan Liben - who apparently became ashamed when he was referred to as "the imperial painter" and warned his son not learn to paint to avoid his fate of being known for it, because it was lower status than his actual paying job in the imperial administration, and his painting was something he at one point was ridiculed for.

People draw or make music or create stories whether or not we get paid for it, and even in situations where it's seen in a negative light, and we've done so for tens of thousands of years.
This is a very interesting and important question. I think that until we answer your question rigorously, the best bet right now is to start with the expensive powerful LLM, and then after your system is prototyped and working, piecewise move prompts in your prompt network over to other systems as it proves feasible.

If you try to start with the multiple cheap LLMs approach, it is almost certainly going to be more difficult to get the prompting right, and if you don't already know what you are trying to accomplish is feasible, you're adding a lot of work that might add up to nothing (even if it would actually work if you used the more powerful model).
Uh wait a sec, this is a microcode update? that will just install without any notice?
So the question is whether those bugs are in the framework part provided by Apple, or the application specific code handing the individual messages.
The quality of this "press release" is really impressive. It is very well written, with clear and easy to understand explanations - no over emphasis on any specific stuff, clean page and wording.

I enjoyed reading through it, this is something I miss more and more with most of the press release made to grab the 5-second-attention of people scrolling through their feed in whatever media app they are using.
Deny, deflect. Someone would have to be utterly blind to tone to publish a document like that. Working late, fuelled by stimulants? Undermanaged? Narcissist? Who knows, but I'd prefer not to get medical care there.
I think, this is a general design feature. The specs explicitly allow a possible document body. If the status doesn't affect the process of retrieving the requested document (like a redirect), a client is free and even expected to display the document body.

Having said that, if the status code is in the 4xx client error range, I'd wish that any document.title would be strictly ignored and browsers would always display the status code (together with the human readable error title) as the page title.
That garbage code brought about the speed run culture, highlighted by charity events like Awesome Games Done Quick. The speed runner and their crew on stage will explain the latest level skips, wall clipping to avoid tedious areas, enemy weaknesses and exploits, and frame perfect input strings needed to accomplish those. And some will perform speed runs blindfolded with only the audio cues to work with.
The primary reason populations are getting older is due to lower fertility rates. A fertility rate of "N" results in a generational ratio of 1 person of the current (older) generation to (N/2) of the next (younger) generation. So a fertility rate of 2 means the current (older) generation will be exactly the same size as the subsequent (younger) generation.

But if we assume a fertility rate of 1, which is the direction most developed countries are headed, then each successive (younger) generation will be half as large as the (older) one before. This means society will be disproportionately composed of the ever-more elderly, with socioeconomic chaos, or Logan's Run, soon to follow. This would, counterintuitively, be true even if life expectancy was low. If we all died at 50 you'd just end up with a society with a larger and larger chunk of your population around 50 years old, until eventually there was no population left at all.

And, vice versa, a fertility rate of e.g. 6 (as is the case in some places in Africa), means that each successive (younger) generation will be 3x as large as the previous (older) one. So you will always have extremely low mean and median ages in this context, again regardless of whether life expectancy was high or low.
I love them even though I don't use them myself. They let less technical members of my teams like content and interaction designers run apps in two clicks. Often they don't have admin rights on their computers to install the necessary tools so it eliminates that problem too.
It's pretty close to free because they already pay for the infrastructure for the current content. The marginal cost is very low.
The article is exaggerating to make a point. It is usually, or almost always, true that people around you know more about what you should do in such situations than you do.
> And any custom protocol parser will be riddled with errors, because they always expect values to be in range.

I hope you're not working on any products I rely on.
I think it is time to reconsider these guidelines. I believe that this community should stand for freely accessible information on the Internet. As it is, we are being gamed: we are used to upvote and popularize content behind paywalls. The owners do not make it freely available, but still get the benefits of the community.

I have nothing against paywalls and paid content (in fact, I subscribe to news publications myself), but I believe they have no place on HN. Either it's on the Internet, or it isn't.
And this is why I think people who love Software Freedom should think twice about signing a CLA for their copyleft licensed contributions. [1]

inbound=outbound license terms is a good norm for FOSS. Why should a software vendor play by different rules than everyone else when it comes to things like copyleft compliance?

[1] https://meshedinsights.com/2021/06/14/legally-ignoring-the-l...
34kwh!? That’s a pretty beefy setup.
What's the rush for this?
As 80's coding kid, I am quite confident that kids would be able to master coding Arduinos, ESP32, BBC Micro and Raspberry PIs.

As to be effective in today's world, already knowing that is more than many teenagers know beyond doing likes in social media.
What did you do with all the comments at the end of the review?
> It's not a fallacy.

I feel it is, because it implies it just some statistical trick that's being performed, which is not true at all, imho.

I don't know enough about language models, my machine learning knowledge stops to around 2018, but I know from image recognition/style transfer that there's a lot of high-level self-organization/abstraction in those neural nets, and from the results I get from Chat GPT there's no doubt in my mind it's very well capable of reasoning and generalization.
Firefox defeated IE which was bundled with Windows at the time.

Chrome continues to defeat everyone, including Edge which is bundled with Windows.

Firefox's reason for irrelevance today has nothing to do with whether its competitors are bundled with operating systems.
Honestly speaking, I'm not surprised, not because it's HashiCorp, because they are moving away from BSD/MIT style license to a much more restrictive source-available style license.

"Open Source" software always have been loved by companies because it provided extreme flexibility (closed forks, forks for customers, secret sauce addition, etc.), plus announced the message that their code is free for all, given there's no warranties.

These companies have skipped more nuanced licenses such as Apache, MPL, EPL even GPL in some cases, trusting that every actor in the software landscape is rational and ethical.

The idea was nice, but it involved humans.

After a couple high caliber forks, HashiCorp indeed felt the pain, and reflexively they moved to BSL.

What they forgot is their initial license has been designed to allow this in the first place. MIT/BSD/Expat is not suitable for monolithic code bases of this size, but people won't listen.

On the other hand, the code is HashiCorp's. They can do whatever they want with the code they write and put out there. They decided to change the terms they share their license, and nobody can say anything about it.

Is it ethical? No. Were the forks were ethical? Depends on motivation.

These things happen when you choose a license without much consideration for the future.

Maybe we shouldn't abuse Open Source software this much and embrace "Free Software" more, but this is just me.

So, at the end, "market forces" abused HashiCorp and, HashiCorp reacted. This is a normal impact/response event. Nothing extraordinary.

Edit: While one may argue that this is also similar with RedHat/IBM, The impact of the change, the number of broken promises, ecosystem dynamics and the motivation behind it make it different, yet I don't want to double the size of this comment.
100%. WipeOut was my first clear memory of "experiencing" design. The branding was so different and futuristic, the ships, the music, even the console itself.
It might be a helpful framing to think of handling emotions and dealing with adversity as life skills, like cooking.

There isn't one single "correct" way to cook. Most people pick up some cooking skills naturally as they grow up - from family, from friends, through reading books or TV shows. But some people grow up with parents who are bad at cooking, in an environment where most people don't cook, and they will themselves be bad at cooking as adults. If they realize that later, "How come all my friends talk about cooking rice like it's no big deal", they might benefit from taking a cooking class, or sitting down and reading a basic cookbook. It could be a "food science" book that tells you the chemistry of Maillard reaction, but it doesn't have to be. The important thing is to try out different ways to cook than what you're used to, guided by someone who is good at cooking. That will be more effective that sitting down and trying to rediscover how to make an omelette from scratch.

Most people are getting by with their normal cooking skills, but everyone who could probably discover some ways to improve by watching a cooking show, or taking a cooking class. We could consider teaching more cooking in school to make sure everyone knows some minimum amount of cooking to get by in life.