Hacker News new | past | comments | ask | show | jobs | submit | cwilby's comments login

> Internally, we call the request’s destination server its “origin”

Origin: The point at which something comes into existence or from which it derives or is derived.

How can the request's destination server be the origin, if it is the destination server?


Depends on your perspective :)

"Origin" is a term from web browsers, from their point of view it refers to where a web page came from.

see https://developer.mozilla.org/en-US/docs/Web/Security/Same-o...


This hilariously reminds me of the complaining about X server semantics back in the day.


On the internet, the origin is the server sending the response to the user. I suppose you can look at it from the perspective of the owner of the server -- from their frame of reference, their journey _starts_ when they receive, process, and respond to the request.

Granted, computer scientists are infamously known for being terrible at naming things.


Had any fun with “Referer” headers lately?


The origin is the origin of the content.


Thus cross origin resource sharing. Thanks!

At least it's consistently inconsistent.


gross


Seeing the title reminded me of "Warriors of the Net".

We were genuinely told, as a class, to watch this video to learn how the internet worked.

https://www.youtube.com/watch?v=RhvKm0RdUY0&themeRefresh=1

Good times!


It looks to be contained to just GitHub, azure service page shows no outages at this time.


The timeout can be about 200 before you need to chill out..


I just started learning Chinese about 2 months ago, to me it seems they stuff whole concepts into characters.

For example,

"去" (pronounced "Qú") is "going to the". "超市" (prounced "Chao Shi") is "supermarket" "去超市" (pronounced "Qú Chao Shi") is "going to the supermarket".

3 syllables vs 7 syllables.

To me, it seems that instead of composing letters into words to convey meaning, they have more letters that are mini-words unto themselves.


Don't forget all the abbreviation. "超市", supermarket, is abbreviated from "超級", super, and "市場", market. The equivalent in English would be "sup-mark" or something along those lines. (Or in Japanese, just "super".)


Since we're now talking about verbal rather than written:

> No matter how fast or slow, how simple or complex, each language gravitated toward an average rate of 39.15 bits per second, they report today in Science Advances.

-- https://www.science.org/content/article/human-speech-may-hav...


This tracks - it's difficult to speak at the same pace in Chinese as I can English. That said - are those 39.15 bits plaintext? Compressed? Encrypted?

The size of a word does not correlate with it's concept - I still posit that some languages can transfer concepts faster than others, minus our baud rate.

Edit: Or, perhaps I am not as gifted an English speaker as my bias has presumed :| For example, I had to lookup "syntagmatic".


Actually “去” is pronounced “Qù”


Thank you


Saw the headline, found your comment within two seconds, exhaled with relief.

Every time a cohesive pair of words is redefined, a new JS framework is born.


Yeah me too, but then I actually read the (very short) article, which immediately addresses that and not much else.

Better title would be 'instead of authz & authn ...' to make that clear, because it does just sound like they haven't heard of the concept at first.


I don't know what to say more than - I wish they'd calculated in KWh instead of $.

I really want to know that figure, but I'm left extrapolating.

I could _guess_ it's huge, but that's not the point.

> "Can we make a separate intelligence beside ourselves, damn the energy expenditure?"


"Clearfix" - when this article was in the bookmarks bar: https://css-tricks.com/snippets/css/clear-fix/


We recently installed something similar (https://miniprofiler.com) into a legacy ASP.NET MVC app. It is setup to only be visible in local development environments.

In areas of the code where ORMs obscure the actual SQL that runs, it's shortened the amount of time and effort it takes to discover a slow route and optimize it.

"Handy to have that extra info in your dev environment" is pretty spot on.


Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: