skysight-inc/HackerNews huggingface dataset:
>Especially if you have metrics/alerts that are tracking status codes.

This is the point though. As a client I don't want to throw 400 errors. As a server I don't want to throw 500 errors nor some 400 error.

As an example, if either client or server sees a spike of 404 errors they want to investigate. When the result of that investigation is "some crawler went haywire" or "a user is trying to access resources that don't exist" it's annoying. So the 200 OK with an error is an attempt to stop those sorts of scenarios. Of course like anything people take it too far but there's decent logic behind it.
TL:DR: On the Pro Plan, they are increasing the Price beginning Sep 1, 2022. Got this email below:

"Switch to a yearly plan to keep our current rate for a year
Your team’s current rate for the monthly Slack Pro plan is $8 USD/user/month.

Our current rate for the yearly Slack Pro plan is $6.67 USD/user/month, and we are offering monthly subscribers the opportunity to lock in that rate for 12 months by committing to a yearly Pro plan. To take advantage of this offer, switch to the yearly Pro plan before September 1.

If you take no action, your monthly Pro price will adjust to $8.75 USD/user/month and will be reflected in your account on September 9th, 2022."
> If the client knows nothing about the meaning of the responses, it cannot do anything with them but show them to a human for interpretation.

The client "knows nothing about the meaning of the responses" only inasmuch as it intentionally abstracts away from that meaning to the extent practicable for the intended application. Of course, the requirements of a human looking at some data are not the same as those of a machine using that same data in some automated workflow.

Linked Data standards (usable even within JSON via JSON-LD) have been developed to enable a "hyperlink"-focused approach to these concerns, so there's plenty of overlap with REST principles.
I think it's that it feels like a dead product, even though it's still running.

Not a lot of new features being developed, and some features getting turned off "to support the product's next chapter"[1].

There hasn't been a firm announcement about Feedburner being sunsetted, but given Google's history of killing things off (including Reader, apropos of this thread's topic), it does feel like the walking dead.

https://developers.google.com/search/blog/2021/04/changes-to...
I graduated with a BSEE and worked as an EE for 6~ yr in hardware design, mostly as a generalist before switching outright to embedded FW. I make more money and have greater autonomy. I like hardware but enjoy firmware an equal amount and would only switch back into a role that encompassed both (like engineering lead, etc)
The amount of people that think that insert musician here had this great original song is one of the most encountered fallacies in my daily life and online.

Not only that, people tend to compare in word and concept from the newer song to the older song! “Hey wow this song from 19xx sounds just like this new song I love”

No you fool, your new song sounds like the previous one :P. Causality matters!
I’m not really interested in the robot thing, I’m more interested if this is a thinly veiled attempt at transphobia, as it seems to be
Sixels are compatible with cursor positioning escape sequences, so I can position the image on the screen. I wasn't able to do this with term2. Very possible I just didn't see how to do it though. If you have a pointer to docs for making that work, I'd love to play around with it.
all clouds provide buggy over priced services. some clouds provide stable primitives.

judge clouds on the stability of their primitives, nothing else.
I’ve always thought it might be PHP legacy of returning 200 even on critical errors. AFAIK Slack and FB APIs work like that, and they are, or have been, PHP based…
We are having a combined issue very similar to this, and other comments in this thread.

We have been using Azure for 5+ years, we are quite heavily invested. Our payment card expired and so we decided (as good customers) to update our card, only Microsoft's billing will not accept it because it will not go over to the embedded payment gateway page.

We provided screen share sessions to their "manager", we provided HAR files from Edge to support "engineering" diagnose the problem, and we provided proof that it is their own servers responding with 500 Internal Server Error messages and 403 Forbidden errors.

The Microsoft support agent admitted that there is a fault with their system. They admitted that they need to fix it.

We keep asking for the issue to be escalated - it never is. We keep asking for the issue to be treated as a complaint - it never is. The agent simply will not do the things we ask.

Communication is like getting blood out of a stone. Once a week if we push out two or three reminders, always out of hours even though they repeatedly ask us what ours suit us. They even schedule calls and don't call.

2 months later, they tell us that 35% of Microsoft customers with our bank have this issue and they're not going to do anything about it, so uh, I guess we're up the creek with this? Thanks Microsoft, you're letting down our 70,000ish customers and we're not going to take the blame for it - we'll be honest with them.

And so we became AWS customers. Zero problems with payment. Zero problems with our Linux services migrating across. The only issue for us is a technical debt issue - migrating old .NET web apps.

The whole affair has really soured my personal and our customers opinion of Microsoft.
The Ghostwriter expansion pack was next fucking level. Clues hidden in documents to solve a mystery - one of my favorite early childhood software experiences.
https://news.ycombinator.com/item?id=32143386
> if you get any sort of incident they will ask you to rewrite your app to accommodate them, rather than fixing their own bugs/state.

As it happens I recently ran into this exact situation with AWS. My team hit a surprisingly low undocumented scale limitation with one of their services. The error message stated that the limit could be increased on request, so I did exactly that. Rather than simply increasing it, they delayed and kept asking to setup a call to talk about how my team could rearchitect our code to work around their limitation. I told them no thanks, finding a way around the limit was not the issue, having to burn time implementing it on our end was.

Overall though I do agree with your point. AWS is generally pretty good about handling scale and not breaking older APIs, but there are exceptions.
>The people I believe you're referencing are usually called "Young Earth Creationists".

That's who I and GP were referring to.
For all of its faults "GitHub markdown" works decently well for collaborative writing; the number of people who are willing to learn LaTeX just to work on a document is way too small compared to the number who would greatly have their life made easier by doing so.
I graduated in EE and this is no surprise- hardware is hard and Google will throw you $500k a year to tweak the font on their internal compiler. Optics, Power engineering, ASIC design, it’s all fascinating and * really hard * and * really underpaid *.

It’s worrying in the long term, the industry’s been built on underpaid geniuses. We need them, but you can’t begrudge them moving to the money.
Can you expand? I don't think I understand.
Take a job at a poultry processing factory for a month. That will heal your soul somewhat.
Has there been any progress in software to allow individual unaffiliated volunteers to help make decentralized third-party backups of the Internet Archive's WWW Wayback machine data?

My opinion is that it may be difficult to find enough volunteer storage to fit the entire Archive, but if we focus on prioritizing plaintext HTML, plus perhaps graphics included in web pages constrained to a size limit, we can do it.
i am confused by the prompt i am getting: "Write about a time in your life when you struggled with a choice and made the right one"

i understand journaling to be about today, not something eventful in the past. that prompt i'd be tempted to answer with a multi page essay.

the key for me for journaling is habit. the habit to do this every day, and not to skip. the prompt doesn't matter. i just write about anything noteworthy from that day.

with a plain text editor, into a file.

it's not ideal though. it's the last thing i do before going to sleep, and once in a while i miss an entry. and on some days, i feel there is nothing to write.
> While often you will get a 404, this is wrong: the http call is successful. The endpoint did not vanish

According to RFC 7231, status code 404 means that the specified resource wasn't found. Not that the endpoint wasn't fount.

"The 404 (Not Found) status code indicates that the origin server did not find a current representation for the target resource or is not willing to disclose that one exists. A 404 status code does not indicate whether this lack of representation is temporary or permanent; the 410 (Gone) status code is preferred over 404 if the origin server knows, presumably through some configurable means, that the condition is likely to be permanent."

So replying 404 is the correct response.

https://datatracker.ietf.org/doc/html/rfc7231#section-6.5.4
One of the reasons why they tried ternary was because the magnetic core memory in use at the time had three "natural" physical states: non-magnetized, magnetized clockwise, magnetized counter-clockwise. Binary computers usually used only the latter two, because neutral state was hard to write reliably.

In practice, it didn't work out for ternary, either; Setun would use pairs of cores to represent trits.
The major issues you'll see involve library version mismatches. It's a very good idea to use venv with these tools since there are often mismatches between projects.
> The term "unborn child" presupposes personhood.

Right, did you miss my disclaimer?: "recall that we're not debating point-of-life at this point in the thread" (based on upthread: "I'll just add that many people who are pro-choice believe that the issue of whether a fetus is a person is irrelevant.")

> "fault" is too strong a term even in quotes

Yeah, I put it in quotes because I wasn't sure what the analogous term is. "responsibility" is probably better.

> If a person poisons another person deliberately and causes their kidneys to fail, it is not an acceptable punishment to take their kidney and give it to their victim. This remains true even when the victim will die and has no other organ source available.

It's not about punishment, but about making the victim whole. But as discussed elsewhere, I think this analogy is broken for other reasons--specifically, an abortion is an active procedure to kill a dependent party who would most likely otherwise survive, while our analogy posits a dependent party who would die without active intervention. The analogy postulates the state requiring an intervention to preserve life, but an abortion ban is a prohibition on interventions which stop life.
If you're arguing from a purely utilitarian perspective, it seems you should argue to legalize not just abortion right up to birth, but also infanticide by parents. If either parent can kill an unwanted child, then by definition all surviving children will be wanted by both parents, which solves the problem of one parent potentially being a "deadbeat" and the state having to step in, etc.
If someone sells 100 billion USD of bitcoins, the rest won't be worth 900 billion USD any more. A market price does not work that way. The rest would probably be worth another 100 billion or nothing at all. The price would drop even while selling off the first 10%, so even getting 10% of the nominal value out could be impossible when owning every last one at the start.

Or to put it another way: No one, at any point, put that much money into the system.

Also, it costs our environment a lot. Soon I would join the ranks of luddites, if science and anything digital was not that much more interesting to me than plainly surviving.
> How to know if there is no malevolent CAs

CT logs make issuance of certificates very public, that allows the community to react to mis-issued certificates very quickly, this however doesn't stop a CA from just not submitting the cert to CT logs.

Browsers like Google Chrome check the certificate in CT logs, and would refuse to work otherwise.
For reference for other readers, the situation that happened in Texas to cause the power grid to fall over was widely forcasted as a "once in every ten years" event. It was not an unimaginable extreme. Most other states plan or require planning for such events, either out of caution, or from direct harm caused by similar events
I still have a reference manual for XyWrite on my shelf. Cool people used XyWrite. WP won.
https://news.ycombinator.com/item?id=32143256
It seems like the simplest way is to put a link at the end of the post that goes to a regular web page that has the comments.

At that point, you need to decide if users need to log in or not. Often, requiring a login of some sort is a good anti-spam measure, but it also excludes some people.

Still, if requiring a login is good enough for Hacker News, it's probably good enough for your blog. Why do you want to hear from anonymous posters anyway?
Not knowing anything about you, I’m going to assume you mean code that you created and chose to release as OSS. That’s your choice, and publishers have the same right to release their works under different terms (through agreements with the authors they have signed, etc). You don’t have any say over what other creators choose to do with their works, and if they choose terms you don’t like, you can’t just ignore them.

Without strong copyright laws, the choice you make is just as enforceable as the choice they make.
What does "navigating the offer" mean?
Because HATEOAS is stupid for client-server communication.

It mandates discoverability of resources, but no sane client will go around and request random server-provided urls to discover what is available.

On the other hand, it does not provide means to describe semantics of the resource properties, nor its data type or structure. So the client must have knowledge on the resources structure beforehand.

Under HATEOAS the client would need to associate the knowledge of resource structure with a particular resource received. A promising identifier for this association would be the resource collection path, i.e. the URL.

If the client needs to know the URLs, why have them in the response?

Other problems include creating new resource - how the client is supposed to know the structure of to-be created resource, if there is none yet? The client has nothing to request to discover the resource structure and associations.

Also hypertext does not map well to JSON. In JSON you can not differenciate between data and metadata (i.e. links to other resources). To accomodate, you need to wrap or nest the real data to make side-room for metadata. Then you get ugly and hard to work with JSON responses.
It maps pretty good to XML (i.e. metadata attributes or metadata namespace), but understandably nobody wants to work with XML.

And the list goes on and on.
> consensual sex constitutes a waiver of the right to forego birth

This is the part I'm most interested in exploring. Absent a debate about "life", under what pretext does this construction arise? It's hard not to view it as a post hoc rationalization of a just world fallacy. Are there any other ways to construct the consequence of a waiver of the right to forego birth that stems directly from the act of sex? Some sort of sex teleology? Something else?
"After-birth abortions" just sounds like hospice issues. Are you obligated to leave a person plugged into a life support machine if they have no reasonable hope of recovery and can not survive without the machine? Trying to bring it into the abortion debate is just muddying the waters.
The centralization of the IA should've got more attention sooner. I've worried that the Wayback Machine will only remain up for another couple of years as a result of the IA's actions. It has saved me countless times in the past, but it's sadly a one-of-a-kind, fragile trove of data in the hands of an organization that didn't keep their ideals separate from reality.

I feel they should be taking steps immediately to ensure that at least the data of the Wayback Archive will outlive the whims of IA-the-organization in the coming decades/centuries, before it's too late. There's probably a lot of people willing to help out with such a replication task.
Intel cancelled their sponsorship of Intel Science Talent Search. That was a relatively cheap way to build goodwill and cultivate the talent pipeline.
HN has been around for a while now, there are always reposts. When I notice one (like this) that also catches my attention I like to track down the prior discussions. And once I've done that, I may as well link to them here.
Are you familiar with "Last Thursdayism"?
Rent is the basis for all forms of savings through investment. It allows people to work hard for a time and then take some time off. Yes, some will be rent seeking while drinking rum at the beach bar, but so will the sick people and the retired people. Rent makes it possible for society to offer disability insurance and retirement savings.
I think they mean lots of people are copying the mentioned author.
I can see the middle motor problem (though the company here claims to have solved it by using a front motor instead) - but there is a signal available to the bike; the brakes themselves.

I'm not sure that cars even begin regenerative braking until you actually hit the brakes as opposed to just letting off the accelerator.
I find an uncanny correspondence between the recommendation given here, following as it does from an interpretation of the Agile manifesto, and Brian Will's procedural programming recommendation contra OOP in his classic 'Object-Oriented Programming is Bad'[1]

[0]https://www.youtube.com/watch?v=QM1iUe6IofM
I think the "gradient around the edges" of the tiles might work better with hexagons than triangles
I'm always terrified that corporate will eventually decide to cut slack from the budget and stick with Teams.
You were too pessimistic! Automatic programming, a.k.a. program synthesis, has been a thing since the early days of AI and computer science, for example the idea of deductive program synthesis, where a program is generated wholesale from a complete specification in a formal language that is not a computer language goes at least as back as Alonzo Church himself, in 1957:

https://en.wikipedia.org/wiki/Program_synthesis#Origin

Much work has been done since then and inductive program synthesis from incomplete specifications consisting of input/output examples (a form of machine learning) has been possible for quite some time. This is the second time this week I point to the report by Gulwani et al for a modern overview (of both kinds):

Program Synthesis

https://www.semanticscholar.org/paper/Program-Synthesis-Gulw...

Rather than Copilot being the "tip of the spear", it is really a step back, a system that can only generate code but not check its correctness, unlike pretty much every program synthesis system since forever. Although this may actually be an advantage for its commercial application (since it makes it easier to match expectations of the system's performance) it is not really any indication of progress, in any way, shape or form. In truth, Copilot is famous today because it is supported by a large company like Microsoft and because earlier work is not well-known by most people who get their AI knews from blogs and podcasts, who are also not very well aware of the history of the field. But, "tip of the spear"? Oh, no. Unless it's a very blunt, toy spear, more like a tech demo of a spear.

And this is by no means restricted to program synthesis, and Copilot. For example, the first self-driving car to drive on a stretch of real road, with real traffic, without human intervention, was Ernst Dickmann's 1995 robot car:

https://people.idsia.ch/~juergen/robotcars.html

Again: 1995. And yet, fully autonomous self-driving cars are still not here. The revolution hasn't happened and progress has only crawled marginally forward.
Rather than reiterating arguments, I'll just link people to the thread where you and I debated this: https://news.ycombinator.com/item?id=32142968
How is this better than downgrading the error into a warning? You'd be able to build but would still know something was wrong-ish. Certainly a warning would be sufficient to chase down any bugs, and is very freeing compared to an error.
No, I take short working breaks from my naps
but surely there must be a difference between babies dying due to factors out of your control, vs you terminating it? Back in the middle ages the infant mortality rate was apparently 20-30% in the first year[1], but I doubt that would be a valid justification to kill babies after they're born.

[1] https://www.economist.com/special-report/2019/01/03/in-the-m...
Me too. In 2021 it got so egregious that I finally jumped ship. Pip or bust.

Since you specifically mentioned 2021 instead of 2022, I half suspect you had the same experience.
I had similar experiences around a similar time frame.

I had no idea how lucky I was.

As an adult I moved to another city - what I found after moving is that there are no sidewalks, lots of hills, and virtually no where is safe to bike. (sadly this is still pretty much the case 20 years later around here, although they have added some 'bike lanes' and laws.. you couldn't pay me to bike around here.

Arcades have closed, no skateboarding and similar trespass rules are common now to deter hanging out at strip malls and such.

I keep recalling the news story some years back where a mom was arrested for allowing her kids to go to the park without a parent (maybe it was chicago or similar?)

Friend's houses have become a worry about all the stories you see in the news / social feeds about drugging / raping / guns / unfiltered porn / hidden cams etc..

I too have pity for today's youth with heads in phones - however seeing what some of the other hoodlums are doing with idle hands these days, on top of the rampant dangers outside the homes, I'm glad there are all these screen options today.
I've seen on many other sites (especially on Mac sites) that people really don't like the idea and rather install an outdated macOS. They call ChromeOS spyware too.
>(JSONs fine, it's fine)

I read this like you're convincing yourself vs the reader.
the URL should have been https://iquilezles.org/articles/texturerepetition but this is indeed a great resource
I am the author and I agree with most of what you are saying here, REST and HATEOAS are for humans:

https://intercoolerjs.org/2016/05/08/hatoeas-is-for-humans.h...

I disagree that it isn't an API, but that's a definition quibble. It is probably more profitable to talk about RESTful systems rather than RESTful APIs, since people think API == machines talking.
If a person "believes" something, but there is zero effect of that belief on any meaningful aspect of their or anyone else's lives, then what relevance does it have? If I "believe" the Earth is flat, but still fly on airplanes, and use a cell phone empowered by satellites, etc. then who really cares what I say I "believe"?
Get a commercial dehydrator. You can make dehydrated fruit and veg, trail food, jerky, dried herbs, tea and lots of other things.

You can grow gourmet or medicinal mushrooms with a handmade flow hood, a pressure cooker and two grow tents.
Is a 2016 National Geo docu.

Features Stamatis Moraitis. Dead.

Features Dr. Ellsworth Wareham. Dead.

Features Marge Jetton. Dead.

Features....oh well I don't want to spoil your day. They are all dead.

https://abcnews.go.com/Health/photos/photos-greek-isle-resid...

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

https://adventist.news/news/blue-zones-icon-jetton-dies-at-1...