It's also staged. They did it in multiple takes, and then composited out one of the takes with a mosaic of the clean sun. None of the others are composites, and none of the others got multiple takes
Source for it being a composite? The article says under the headline
> This is not photoshopped. That’s really a person falling in front of the Sun.
I haven't watched all the videos. From the Reddit thread, it sounds like it was photoshopped (using that as a generic term for photo editing with a computer) but in a way acceptable to the astrophotography community. I don't understand where those limits are: somewhere strictly between cropping the photo and photographing the skydiver in front of a white screen before pasting the silhouette into a picture of the sun.
Sometimes the actions you want to perform does not map cleanly into one or two API calls, or would be too messy to assume correct parsing. Maybe your UI is fine POSTing to /users and PUTing to /groups or whatever but giving the LLM a direct CreateUserAndAddToGroup action simplifies the task and keeps context cleaner.
Imagine a future where we have an evolved version of MCP -- call it MCP++.
In MCP++, instead of having to implement a finite list of specialized variants like CreateUserAndAddToGroup, imagine MCP++ has a way to to feed the desired logic (create user, then add that user to $GROUP) directly to the endpoint. So there would be something like a POST /exec endpoint. And then the /exec endpoint can run the code (maybe it's WASM for something)...
Wait a minute! We already have this. It's called programming.
You could have the LLM write code, so that any pipelining (like your example), aggregation, filtering, or other transformation happens in that code, and the LLM only needs to spend the output tokens to write the code, and the only input tokens consumed is the final result.
I definitely am not the first person to suggest this:
... but I can say that, as soon as I read about MCP, my first thought was "why?"
MCP is wasteful.
If you want LLMs to interact with your software/service, write a library, let the scrapers scrape that code so that future LLM revisions have the library "baked into it" (so you no longer need to spam the context with MCP tool descriptions), and let the LLM write code, which it already "knows" how to do.
What if your library is too new, or has a revision, though?
That's already a solved problem -- you do what you'd do in any other case where you want the LLM to write code for you: point it at the docs / codebase.
I do this all the time with Shopify / Spotify. The number of times non-tech friends have had to ask what Shopify is when discussing music and I slip up :/
The cname is just a normal domain. That DNS entry is a real entry. The CNAME is real. You can go directly to that address too. If someone else knows the cname destination they could go to it or cname their own domain to it literally like any other domain.
The only specially handling is cloud flare has a mapping from subdomain to your private network via it's agent and that's it.
I don't get what's the wrong or complicated about this.
I gave you the benefit of the doubt for a moment, but as far as I can tell, you are incorrect for practical purposes. I went ahead and re-checked everything to make sure. Let's see:
1. I have a cloudflare domain with a working tunnel (managed through Access). In DNS Records, it shows as a CNAME to [redacted].cfargotunnel.com. But:
and no records are returned. Interestingly, it's an empty result, no NXDOMAIN.
2. I have multiple subdomains that appear to be CNAMEs to the same [redacted].cfargotunnel.net. And yet they are entirely different sites that just happen to share an instance of cloudflared at the origin. The sites aren't even served at the same origin address!
They are different "Published Application Routes". They don't even have the same protocol!
2. The tunnel above is on a domain with "Full (strict)" TLS. But traffic to the origin emerges from cloudflared in cleartext.
This whole configuration schema is nonsense. What should happen if a CNAME points at a tunnel that doesn't have a route for that application? What if a tunnel has a route for an application that is CNAMEd somewhere else?
I imagine that what's going on is that Cloudflare internally has a rule that traffic with a cfargotunnel.com origin goes out their Tunnel infrastructure instead of out to the normal Internet. And Cloudflare applies the same JWT that it would apply if the request went out via the normal Internet, and cloudflared verifies that JWT if "Enforce Access JSON Web Token (JWT) validation" is on (maybe the request is literally TLS wrapped inside the cloudflared tunnel? I've never tried to inspect what's going on inside). And then cloudflared unwraps everything? And if you configure cloudflared wrong, then it's totally insecure?
Apparently I was wrong about that part. Only the part about cents still being legal tender was correct. So you can pay the exact amount, but not demand the exact change.
> It feels like screenshots have become the de facto common denominator in our mobile computing era,
Google/Apple have taken notice. Both have recently redone their full-screen post-screenshot UI to include AI insights / automatic product searches / direct chat with Gemini/LLM / etc.
Its true everyone uses screenshots to save things they are interested in or want to look up / search more of / save for reason and this UI is the perfect place to insert themselves.
Unless you are buying the absolute cheapest package of cheese slices it will still be real cheese. I'm not even sure if I've ever even seen a Kraft or Valveeta sliced cheese product, only lesser no-name brands. I've been am American all my life and do not buy process cheese product as it does take like plastic, but actual American cheese is delicious on burgers and grilled cheeses and a few other select meals.
What's crazy is Europe allowing 5% non-milk-fat/vegetable fat products to be called "ice cream". Thankfully in America it has to be 10% milkfat at least.
You are looking at the wrong product. This one[0] does say "American cheese" as a single phrase. And the slices are not individually wrapped, as they don't need to be.
Kraft Singles and their Velveeta equivalent are what is available abroad, not the Kraft Deli Deluxe. 40 percent of American households in 2019 bought Kraft Singles.
You may not like it, but it is the public face of American cheese.
There’s no data to suggest that actual fancier American cheese sells more than heavily marketed slices, especially since a huge chunk of the remaining population, and I would say most, is not consuming either “American cheese” or “American cheese product” with sodium citrate.
reply