skysight-inc/HackerNews huggingface dataset:
> REST in practice just means following HTTP semantics.

If that were true, it would be awesome. Because full HTTP semanics are quite intricate, and cover a lot

- HTTP decision diagram: https://github.com/for-GET/http-decision-diagram (full docs: https://github.com/for-GET/http-decision-diagram/blob/master..., just the PNG: https://camo.githubusercontent.com/c26df6d372790e9f24d7e16d2...)

- Know your HTTP well: https://github.com/for-GET/know-your-http-well
From a napkin idea in Australia to an $11B tool used by 1B people
> There are easier ways.

Such as?..

If you're from a capped country, your options are limited. For EB-2/EB-3 the wait time for Indian nationals is around 12 years.
This is DRM all over again.
In other words, wait until E becomes 1.
>I would much rather have to spend a few days to relearn a tool every few years and to get the benefit of that tool, than accept a lower quality tool just to avoid a few days work.

Vim police has issued your red warrants. Justice will be served.

Jokes aside, I'd say yes. I have worked with Eclipse, NetBeans, JB and nowadays I'm happy with VS Code. For a polyglot, it's the best out their at price point $0.0 and tooling is pretty good for me.

I'm doing Python, Go, Typescript and occasional Rust without missing anything.

Few keystrokes faster with command kata would not going to save years of labor. Actuall effort in software engineering is not in typing text or in text editing. Not at all. The battle is far far beyond that and bigger than that.

EDIT: Typos
A lot of this is induced by US regulations also. If you don't comply with these regulations, then you can't interact with the US banking system, even if you do not have any presence in the USA. If you're a bank of almost any size, your going to need US banking access.

It's not personal, it's algorithmic. Switching banks is not going to solve this for you, since every bank that interacts with the economy you live in will have to interact with these laws.

Some are more of a pain about it than others although. Like venmo in the USA temp freezes your account if you put "iranian food" and insists you put descriptions for your transactions, while other p2p cash transfer services in the usa do not insist on transaction descriptions for example.

AML is the least effective policy out there, costing more than it recovers by a large amount and causing a lot of collateral damage to the poor, but there is an entire industry funded by it so thus it continues. https://www.tandfonline.com/doi/full/10.1080/25741292.2020.1...
Most buildings in OSM aren't actually tagged with numbers. (A lot of houses aren't even marked as existing buildings in my experience.) It should be have their street at least, but adding building numbers is just too time-consuming for outside of cities it seems.
> common sense gets people killed.

That isn't a policy proposal.

If you're in a cornfield next to a farm road that only sees one truck every six months, common sense says you're not at a busy intersection, but if you step into the road without looking and there is a truck, that's not the truck's fault. You can be cautious all the time or you can take a risk once in a while; it's your choice because it's your life.

It's also not clear how it applies to the topic. If you went to the store and asked for some MDMA and they gave you some MDMA, you are not going to be surprised that the contents is MDMA. That's not why it's banned.
It's not that simple. Likely the root of this is that alpine uses musl which by default ships an allocator that is extremely slow in multithreaded code. I've seen Go programs be much much slower under alpine for this reason as well.

Given how often this comes up, I think it's high time that alpine replaced the default allocator with something more modern.
I went into this article strongly disagreeing but I think the alternative presented at the end are valid ways to structure an API and for those who very loosely follow REST structuring would probably consider the alternatives "REST" too.

REST seems to have different definitions depending who you talk to. Some define it very strictly (as the opening of the article seems to do) and others define it very loosely (as a JSON interface with GET/POST/etc commands). For those who implement REST loosely, the suggested alternatives fit right in.
This is helpful.

An updating list of IPs for these agents wouldn't go amiss. I might have access to some site logs I could mine for that.
I bet he knows fuck all about drum brakes lol. That has zero relevance to his profession. Boomers who have never been within half a mile of a race car know all about drum brakes.
China has four major launch sites. Wenchang, the one on Hainan, is used for human spaceflight. Larger cargo rockets use Jiuquan in the middle of the Gobi Desert. It's the other two, Taiyuan and Xichang (this one), that are relatively close to rural villages, although both are still very remote by Chinese standards.
> 230GW of solar and wind in 2023

Nameplate capacity. For actual average output, divide by 6.

And it doesn't even deliver that 1/6th consistently, so you unless you want blackouts you also need an alternative that delivers power reliably.
Crashes in HTTP server used in routers found with simple fuzzing
As luck would have it, I do have pictures of myself in a car. However, for privacy reasons I would rather not upload pictures of my face on the internet. I'd be happy to provide the picture to a trusted third party auditor of your choosing (eg. Deloitte, E&Y, KPMG, PWC) for verification, provided that you pay the fees :^)

Now, I don't imagine that there would be any privacy related issues related to providing evidence regarding whether a Chevrolet Impala was considered a compact car or not, so I look forward to receiving correspondence from your auditor and whatever evidence you have that Chevrolet Impala was considered a compact car.
I don't wonder. Fakes and knock-offs were rampant on Amazon -- for a long time, more common than genuine product. People tested them. That's especially true for brand names like 3M.

I only bought through trusted supply chains. My masks were made in South Korea, and I bought directly from the manufacturer's US-based distributor.
Discovered some bugs in an HTTP library used in upnp software found in Zyxel and some other brands routers. Unfortunately no code execution but did get reliable crashes!

All it took was honggfuzz and ~30 lines of code:

#include <string.h>
#include <unistd.h>
#include <mupnp/http/http.h>

#define MUPNP_TESTCASE_HTTP_PORT 8080
#define MUPNP_TESTCASE_HTTP_PAGE "<HTML><BODY>Hello World</BODY></HTML>"
#define MUPNP_TESTCASE_HTTP_URL "/index.html"

void ClinkTestcaseHttpRequestRecieved(mUpnpHttpRequest* httpReq) {
mUpnpHttpResponse* httpRes;

httpRes = mupnp_http_response_new();
mupnp_http_response_setstatuscode(httpRes, MUPNP_HTTP_STATUS_OK);
mupnp_http_response_setcontent(httpRes, MUPNP_TESTCASE_HTTP_PAGE);
mupnp_http_response_setcontenttype(httpRes, "text/html");
mupnp_http_response_setcontentlength(httpRes, strlen(MUPNP_TESTCASE_HTTP_PAGE));
mupnp_http_request_postresponse(httpReq, httpRes);
mupnp_http_response_delete(httpRes);
}

HFND_FUZZING_ENTRY_FUNCTION(int argc, const char *const argv[]) {
mUpnpHttpServer* httpServer = mupnp_http_server_new();
mupnp_http_server_open(httpServer, MUPNP_TESTCASE_HTTP_PORT, NULL);
mupnp_http_server_setlistener(httpServer, ClinkTestcaseHttpRequestRecieved);
mupnp_http_server_start(httpServer);

while (1) {
sleep(1);
};

mupnp_http_server_stop(httpServer);
return EXIT_SUCCESS;
}
Epic 2014 (2004) [video]
> accurately labeled product with a risk-benefit trade off, the customer knows what the product is and is exercising informed consent, and the government says they can't have it anyway.

The FDA's regulatory purview is to limit the collateral damage (negative externalities) of even accurately labeled products.

Informed consent from the customer is one side of the equation. Unfortunately they cannot consent to conditions like "Don't burden the hospital system if you take the wrong dosage".
https://archive.ph/2023.12.28-151825/https://www.sacbee.com/...
Use your own powers of discernment to look up the measurements of various vehicles over the years.
It is a bit shorter and a bit taller than a Prius, which is why I reacted with surprise above (this does not seem "small" to me).
1. URLs doesn’t matter in REST because interactions are hypertext-driven.

2. The method to use is implied by the relationship of a link.
A thing not being mentioned is caching.

Now I'm not a web dev, I've played around way back in the CGI era and since then moved on to other things. But my impression was that part of the point of REST was making it fit in a bit better in how the protocol is supposed to behave.

Early on there was a lot of stuff that did nothing but GET for everything. Done that way any layer in the middle can't make any sensible caching decisions, and even the logs are annoying to look at when you can't quickly tell apart what's retrieving data and what's changing it.

So my impression was that part of the point of REST is to shoehorn an API into something that makes sense in the way HTTP is supposed to work, and you're less likely to have something go dramatically go wrong because some cheap ISP is running a transparent proxy and deciding that the GET that's supposed to save something doesn't actually need to happen, because look, this user already made a GET to the same URL 5 seconds ago.

Now of course today everything uses SSL, but early on it wasn't that weird to run into some awful ISP that would do some sort of aggressive caching to save on upstream bandwidth, if not to actually try to recompress stuff in flight.
where do the rules come from? Is it randomness all the way down? how come they run at all? how can a lifeform in a dynamic mess of jiggling things have a claim to understanding?
Other person is white text on black background. Yours is white text on green background. The app's background is also black.
well then however they are affording a mobile phone and the monthly service, they can probably figure out how to pay $5/month for email if they don't want to use one of the free options.
It's roughly the same size as a Gremlin at this point. And you misread what I wrote.
The trading example is bad, since we do talk about posting limit orders even outside of a REST context -- though it refers to it staying in the book and not matching immediately.
I would like to see analysis of microplastics from water filters.

Water filters frequently use a very fine plastic mesh as their filter medium (eg. 'melt blown 5um polypropylene sediment filter'). I would expect that to give off a rather large number of particles the first time water is passed through it, and perhaps a good amount on an ongoing basis too since the mesh will flex with varying water flow.

Since people wanting to avoid pollution are likely to have water filters installed, it seems important to know how much pollution they are adding to the water they are trying to clean.
I would document my case well, then go to the CEO or to the board and present it. Easy to say now though.
The marketing works. As one of the people who has done outdoors stuff for 40+ years, there has been a clear increase in participants. It has not necessarily been for the better
No, it's not.

But in short, articles arguing thst the most popular api format needs to be put to rest can't be anything else but highly opinionated clickbait
Brilliant and probably building a skill that's actually useful (if a little esoteric).
FreeBSD and REST should organize the Is It Dead Yet? conference.
This looks remarkably similar to the one Tech Tangents (twitch/youtube) has hooked up to GPIB with Python tooling for automating cap reforming. Pretty sure he has VGA type capture working too, so he can hook it in to OBS for his streams (and overlays the Python automation via a web page).
"Beg", and "passive aggressive" from TFA, is an unnecessarily emotional interpretation of that sentence. It's perfectly neutral. When they imported `cargo-vendor` into cargo they removed a feature that was not trivial to reimplement, so they asked for an issue to be opened so that they can see if people want it and so that someone can decide to implement it.

That message *could* be updated to point to https://github.com/rust-lang/cargo/issues/10310 instead of asking for new issues to be created or suggesting the old `cargo-vendor`. (The author of TFA already knows about that issue, since they commented on it before they published their article.)

(You might say it would've been better to let cargo-vendor remain separate instead of merging it into cargo, but the reason that was done was to ensure it would continue to work with changes to cargo. Indeed that is why the original cargo-vendor does *not* work properly any more.)
It is also far safer to have a big car since there are so many other big cars on the road.
If you're going to update a blog post to mention that it's inaccurate, it would seem preferable to put that at the top (so people don't skim it and walk away misinformed) or edit the document in place (which in this case would result in a very short page, since the meat of the post is the part that's wrong now).
Stairway stopwatch tracks climb time
Perhaps, but... they are very ugly.
> propelling the car to a stated top speed of 100 km/h (62 mph)

Yeah, definitely not many American markets. Several highways around me have posted speed limits of 75MPH, traffic often flows even faster than that. Driving in a car that can barely reach 60mph would often result in a speed differential of like 15+mph with the rest of traffic. I'd feel extremely unsafe going almost 20mph slower than the surrounding traffic while in a subcompact car.
The article is good, and I get the point. However, from experience, this:

> POST on /queries/enlisted-students-on-joining-date/version/1 { "date": "2023-09-22" } to retrieve all students that joined on a given date.

always ends up in a complete and absolute mess, where every possible query gets it's own random name, different parameters, ending up with duplicates all over the place. Also, while it can be possible to cache these POST requests (responses), it's additional work and more friction compared to REST. I'm not convinced the tradeoff is worth it in this particular case.

All in all, I don't know if the current proposal can be an alternative either but the idea of a "REST-lite" goes in the right direction and it's a great start.

However this is a complete no for me:

> When a requested student is nonexistent, your API can return 200 OK HTTP status code with a { "user": null, "message": "No user exists with the specified ID" } response body.

If nothing is found, I want a 404! :D
You're the person making the claim. Why don't you "Use your own powers of discernment to look up the measurements of various vehicles over the years"?
I thought a practical benefit of REST (probably the only one I really care about) is that it makes APIs more scalable by allowing caching proxies to safely cache responses to GET requests? At least I thought that was a big part of the original pitch, but I don't see it mentioned here.
> I keep hearing this, but in years of shipping Alpine based images into prod the problems never materialized.

DNS was the big one; for many years musl's implementation of DNS was both divergent from glibc, and in some cases, broken due to lack of TCP support. This only got fixed earlier this year: https://gitlab.alpinelinux.org/alpine/tsc/-/issues/43

TCP support can be a really big deal for reliability at very large scales. When I led the container infrastructure team at $BIGTECHCOMPANY we eventually published a recommendation against using Alpine because musl's resolver was demonstrably less reliable than glibc's- we had the production data to show it.

The other case was when developers copied binaries compiled for glibc into alpine containers, which is user error to be fair, but it was easier to tell everyone to use glibc instead of teaching thousands of Python devs about how the compiler and linker works ;_;
Why I use Astro
Apologies for not clarifying -- the last release of Netbeans prior to the Oracle acquisition of Sun.
> a brick-and-mortar store should be able to ban someone who shoplifts

I don't even like this. Shoplifters should all go to prison, but once they've paid their debt to society and been rehabilitated, they should be allowed to do everything that law-abiding citizens can do, including going back as a legitimate customer to stores that they previously stole from.
Most of these bots already publish their IP ranges, so it would be just a simple firewall rule.

For chatgpt user:

https://platform.openai.com/docs/plugins/bot

And for gtpbot:

https://platform.openai.com/docs/gptbot
https://openai.com/gptbot.json
If you want to avoid having your site contents used to train AI and don't want to make your website unavailable to the open web, then blocking Common Crawl (among others) is absolutely mandatory.

We have very few tools to protect ourselves here, and need to make the most of the ones we have.
> I could go on indefinitely about the different tools I use on the web, but I won't.

I'd be interested if you did list them out.
That really just sounds like an axios issue - I've built in support for custom verbs with nothing but plain-old ES5 javascript. The verb is nothing more than a string component of the HTTP request and it's pretty trivial to modify it to your liking (even outside of standard verbs!).
Do you mean a different domain? mail-checker.com Looks like a parked spam domain.
This comes up pretty often in (well-designed) video games. Say you have colored doors that can only be opened by keys of the same color. If you put the blue key on the path to the blue door, then players will never learn that you need the color of the key to match the color of the door. But if you put the blue key on a side path and have the player encounter a blue door relatively early on, then they will encounter the door first and cannot progress until they find the key. The frustration at not being able to progress is much more effective at teaching the player about the "colored keys for colored doors" mechanic than any amount of explaining you could have done.
have you considered buying some btc and send it to your family member? then they can convert it back to whatever that danish excuse for a currency is
Just did some light reading[1] on the Canada convoy protest, and my reaction is: good.

That was not a "peaceful protest." People were armed, ramming police vehicles, plotting political assassinations, and this was all on top of the basic crime of blocking public roads. I don't care what your political hobby horse is. Blocking roads, which need to be open for emergency vehicles at all times, is not a valid form of peaceful protest.

If people supported that cluster of crimes financially they were making themselves part of the criminal activity and should deal with the consequences.

[1] https://en.wikipedia.org/wiki/Canada_convoy_protest
> Never once in my twenty years have I heard anyone say it’s nice because “you don’t have to read the docs” or “it works in a browser.

I've seen multiple people argue these points. shrug
But the scenario we're talking about here isn't repeated hard braking.
odd.sdk is stellar for Web based apps, great team behind!
REST is a design pattern. Do you use the bridge pattern for all your Java code? Nah! Do you use an ORM for all your data access and never drop down to SQL? Nah.
I definitely don’t have a well-formed opinion on how likely such an outcome is, but I absolutely believe that discussing that outcome as a serious concern is necessary discussion to have.
doesn't that depend on the purpose of the visit? Is it not the choice of a publisher?
I meant it's legit that the bank gets suspicous. Sorry I'm not a native speaker
Tesla, BMW, Ford, GM and Mercedes driver assist systems compare
no

not all circumstances of all cases – and to be clear, covid is brutal, so is burnout. remember though, they aren't mutually exclusive

i've heard some speak of long-covid symptoms as if burnout, without other respiratory concerns. and given numbers of sufferers of both, there must be many who have experienced burnout before covid, so already make a distinction

where symptoms overlap, and circumstances align, the simplest explanation for those overlapping symptoms, might be the aligned circumstances; and anything we can do to simplify the problem space is worth exploring, in parallel, of course
* ignoring leap seconds
so its a truly onprem cloud... as in you don't have access to almost anything but your compute payload.

i was expecting more like a sane-modular system for your own it team. not just someone to phone in their support as needed. we already have tons of companies like that.

had high hopes but seem they are just unify for data centers :( (hopefully they don't copy the ageism tiktok ads too)
> Emacs OR vim?
>
> Wait, you can use both?
>
> This can't be true... How...

Yes. It's called evil-mode[1]

[1]: https://github.com/emacs-evil/evil
But this also isn't true—fetch can run all the HTTP request verbs.

What they seem to mean is that you can't access most of them via the GUI directly, which is true, but their "solution" is to make queries and commands both use POST, which means they've now thrown away the ability to even access read-only endpoints via the GUI.
Hi there @vinniepukh - we already support this! If you upload your public key, then all messages stored to temporary storage will be encrypted. We have a guide at https://forwardemail.net/en/faq#do-you-support-openpgpmime-e... (note the "Optional Add-on" section).
Event-driven is the "reactive" part only. And the old implementations of it where so less capable of fine-handling the events and complex dependencies that it's reasonable to change the name.
And this is something the "Freedom!"-yelpers don't mention: Yes, adults can be "Free!" to do crappy and dangerous things to themselves, but when it's parents poisoning children, you have to be pretty damned sociopathic to only consider how the rights of the parents are being infringed by regulation. I honestly think some people consider children to be property.
And yet, I am still unable to update my Apple Watch with the latest iOS 16. iOS 17 is now required. iOS 17 is also required to rent a movie on my Apple TV.

So, to the author's assertion that "Apple does a good job supporting old hardware", they may give some security patches but interoperability between current and previous versions is seemingly deliberately broken.
> can run any random code they want at install time (which is why Node projects should always be run in some kind of sandbox).

You can install with the --ignore-scripts flag. Or set the option globally in your npm config file.
There are some things that simply don't fit into the REST structure, the most common one for me is bulk operations. Operating on multiple instances of a specific resource is a common thing, and you need a non-REST endpoint to do it properly. Of course you could just iterate over the items, but then you can never have transactional behaviour (either no write happens or all of them happen). And of course it's terribly slow for larger number of items.

Another annoyance is GET endpoints with complex filters like e.g. the index route for a specific resource. It's really annoying to be limited to the query params instead of a request body for that.
Sure but many people leave their computers on all the time, even if they're not with them.
If you made a point about that, it was not clear to me. Perhaps you were implying that simple life could be very common even if intelligent life isn't. While yes, that is a possibility, that says nothing of its probability. Were that the circumstance, it leaves the question open as to why simple life would be common but intelligent life not common.
if that were true indians woudlnt be the highest-earning ethnic group in USA