That’s not a single CCD though. That’s an array of multiple smaller sensors that are next to each other, but there will be gaps where they meet. They take multiple pictures and combine them to make a regular image of the sky, something you probably can’t really do for photography (or videography of course).
Since it’s just used once, you can also just have an agent solve the captcha and then use the returned api key yourself. This has to be engagement bait.
It can't be. It's the same confusion as "email address normalization" being wrong (for example when gmail ignores dots when mapping an address to an inbox).
It matters where the normalization happens, and server-side behavior is out-of-scope of these identifier RFCs.
Yeah I would say that falls under the origin defining both paths as equivalent.
> Therefore, collapsing // to / in HTTP URL path segments is not correct normalization. It produces a different, non-equivalent identifier unless the origin explicitly defines those two paths as equivalent.
nginx is frequently used as a reverse proxy and not "the server" (or only to the extent that it's the client-facing server). Its defaults assume that it's fine to do a "normalization" pass to remove double slash, etc., even though that's potentially out of step with how the actual content/application server wishes to deal with those requests.
That’s purely a server side configuration issue and has nothing to do with web standards though. There’s nothing that says that the internal communication on the server needs to follow the standards for user agents.
And at least according to this, the default setting is off so nginx actually is compliant unless you manually make it not be:
When it's the default, it's not a case of someone having configured nginx to do the thing described, as is their prerogative. It's nginx's defaulting to doing the wrong thing and requiring specific configuration to do the right thing. The author's position is that this violates the RFCs.
> and has nothing to do with web standards though
Yes it does. Prescriptions for how intermediate servers are or are not to munge data before passing it to the origin server are written directly into the HTTP RFCs. They're filled with references to this.
> There’s nothing that says that the internal communication on the server needs to follow the standards for user agents.
And is there anyone arguing that that's the case here?
> When it's the default, it's not a matter of someone configuring nginx to do the wrong thing. It's nginx's defaulting to doing the wrong thing and requiring specific configuration to do the right thing.
This assumes that „the reverse proxy requests a different URL upstream from what it got as a request“ is wrong. Who says that it is?
And as I said, it doesn’t seem to be the default. But I can also continue defend it being the default because I think even as a default on it wouldn’t be wrong.
> Yes it is. Prescriptions for how intermediate servers are or are not to munge data before passing it to the origin server is written directly into the HTTP RFCs. It's filled with references to them.
Which RFC forbids a reverse proxy from rewriting the request URL?
If I have a legacy PHP app that expects values as query strings and I use a reverse proxy to map the URL path to those query strings, is that wrong too? Would it be wrong if my reverse proxy did that by default?
> This assumes that „the reverse proxy requests a different URL upstream from what it got as a request“ is wrong. Who says that it is?
For this case (double/multiple slash "normalization"), the author of this post is saying that—and they're saying RFC 3986 says so, too.
> Which RFC forbids a reverse proxy from rewriting the request URL?
Ibid.
> If I have a legacy PHP app that expects values as query strings and I use a reverse proxy to map the URL path to those query strings, is that wrong too? Would it be wrong if my reverse proxy did that by default?
Clearly, it's not wrong if you selected and/or configured a software package specifically for the purpose of providing that functionality. And clearly it is wrong if it were to do that when not configured to do anything other than act as generic middleware, with that software's creator(s) operating under the assumption that it's safe to do so all while arguing that it's standards-compliant.
> For this case (double/multiple slash "normalization"), the author of this post is saying that—and they're saying RFC 3986 says so, too.
No. The RFC says that the rewritten URL is not considered the same URL. But nothing says that the reverse proxy has to request the same URL.
The rewrite is not a normalization, but nothing says that the reverse proxy is only allowed to do normalization.
> Clearly, it's not wrong if you selected and/or configured a software package specifically for the purpose of providing that functionality. And clearly it is wrong if it were to do that when not configured to do anything other than act as generic middleware, with that software's creator(s) operating under the assumption that it's safe to do so all while arguing that it's standards-compliant.
It’s not wrong and it is standards-compliant, because no standard says that the default has to be „pass the original URL on without rewriting it“.
This implies the only content with moral worth are those that teach knowledge or skills, and presumably only the kinds that are worthy for productivity and advancement or something. But one person's "just an entertaining story or just a silly hobby" is another's life-changing or mind-opening allegory, or therapeutic pursuit with little immediate "practical" value.
I can sort of see the original point; this appears to be a careless risk when there were other options, but I have to push back against the idea it's just some dumb music. It's still an artifact of humanity that's worth accessing and preserving as much as any other.
> This implies the only content with moral worth are those that teach knowledge or skills
This is not what OP said. He was talking about the "moral goodness of providing access to X, despite it being illlegal. He never said anything about the moral worth of X itself, let alone that Y had no moral worth.
> AA is providing a valuable service to tons of people who don't have access to these books otherwise. There's a strong argument to be made for the moral goodness of that -- that even if it's illegal, it's at least in the spirit of a public library.
Trying to imagine telling somebody writing about the history of music copyright that they can’t hear Ice Ice Baby, on account of they might enjoy it, which means it has no research merit.
How would you ever prove that it’s by an LLM? There’s no text an LLM can produce that I couldn’t theoretically type myself, too. But the style is strong evidence.
I envy you, I can’t even read more than a few paragraphs because this style of adding catchy sentences to make you go „wow“ every few sentences is so annoying.
You don’t really need to block all, you just need to annoy the users enough that paying is easier. And I think there are enough games to use up the IP reserve pretty quickly and getting new ones every time is pretty annoying.
I can provision a new VPS in about 5s of active work. I'd probably fully automate spinning up new servers and failing over because automatically detecting which got blocked is trivial. Bonus points if you use providers that let you attach multiple IPs to each VPS for cheap. Use some censorship resistant decentralized protocols to provide the next couple IPs to your client software and you're good.
And then they still need to monitor hundreds of VPN providers for whether they have new IPs, which is not neccssarily as easy as just grabbing a list of them. Once they have some, they then need to forward them to the ISPs and ask for them to be blocked. Their process is significantly less friendly to automation.
No country ever won this fight short of total shutdown/disconnects.
Wild that they manage to fly to the moon but still seem to be having those comms problems. Asking the astronauts if they’re really pressing the PTT button is wild.
My friends and I have been deriving much amusement from the comms issues. We can fly people around the moon, talk with them, send back high res video, but talk to the boat that’s close enough to swim to? Forget about it!
i was thinking maybe astronauts can be disoriented when splashing down and that's why they figured they should ask if the right buttons were being pushed?
Or because you’re interested in the products and the „company community“ is fun and you like talking about it.
reply