You're not arguing in good faith when you equate those.
3,943 karma · joined August 15, 2011
You're not arguing in good faith when you equate those.
I'm curious, what's your use-case for this?
This is... obviously not true?
If you could (somehow) meaningfully damage a car via the app, do you think VW wouldn't be liable because of the Google Play developer ToS?
You can just have them charge your CC directly whenever you make a payment? Or is this blocked for US cards somehow?
You could just read the linked paper?
> Esp was prepared using a Sanremo Cube espresso machine. Brewing parameters were standardised following the supplier's guidelines: extraction time of 35 ± 3 s, pressure of 9 bar, and boiler temperature of 122 °C, with the corresponding group-head temperature of 94 ± 1 °C. A total of 21 g of ground coffee (GS = 2.6 ± 0.1; ∼262 μm) was placed in a ridged coffee basket and tamped using a constant-pressure tamper (MHW Flash Constant Pressure Tamper 2), applying 13.6 kg of force. The BR was reduced from 2 to 1.7 following the recommendations of the coffee roaster for better flavour (1 g of coffee grounds yielding 1.7 g of coffee brew).
1:1.7 is a bit short for my preferences (I like longer shots, usually aim for ~2.5); but otherwise that sure sounds like a pretty good double to me!
(You might quibble whether it's actually espresso if there's not pressure and it's extracted cold; but it's closer to espresso in strength.)
There's a semi-famous, super hipster cafe near me in Tokyo, that I sometimes go to.
Once, they had a special on the menu, when they give you a flat white, and a double shot of espresso on the side, with a thermometer hovering over the shot, with suggestions of tasting notes that you can get out from sips at different temperatures.
Now, that's generally very much a thing — things definitely taste differently based on the temperature (or maybe _they_ don't, but we _perceive_ them differently? distinction without a difference, I guess.).
The suggested temperature ranges were 51-40C; 40-30C, and 30-20C.
51-40 was great. 40-30 was getting weird, but still _interesting_, because you definitely got different notes.
But the 30-20 was terrible. That is absolutely too cool to enjoy a shot of espresso. I'm all for experimentation and doing weird things, but that was no longer riding the line of "not great but interesting" and went straight into "why would you ever do this" territory.
If you're drinking light, floral and acidic coffees, it's been relatively "trendy" recently to skim the crema off before drinking it.
I don't bother with that, but pulling two shots and removing the crema from one of them and trying them side by side is an interesting sensory experience — I'd encourage you to try, at least once!
Protocol in this context means a Swift language feature, like interface in some other languages: https://docs.swift.org/swift-book/documentation/the-swift-pr...
Infuse is a better Plex app than Plex is; and it supports Jellyfin and a bunch of other data sources.
It is, IMHO, a platonic ideal of what a “tv-shaped” video player app should be.
(Maybe it's also a cultural difference?
My native language distinguishes between the kind of "living" somewhere where you're just "staying" somewhere and where that place is the center of your life. I would not use the "I built my life here" verb for a 6mo stay.
Perhaps I'm letting that color my English a bit more than I should.)
But this is very much _not_ what this is.
Apple showed a bunch of new APIs at WWDC last week. One of this is a way for a developers to interact with LLM's in a way that let's you easily swap out models (with a bunch of other niceties around it), including swapping between on-device and remote models.
This is _Anthropic_ (not Apple!) shipping their support for that framework, so you can also switch between different Anthropic models using the same APIs you'd use to swap between a local or PCC model.
I expect OpenAI will probably ship their shims in the next couple of weeks too? (You can probably vibe-code one in half an hour if you point Codex at the Anthropic one, tbh).
(Apple also doesn't use "Apple Foundation Model" anywhere in the user-facing marketing materials AFAICT, this is strictly developer facing terminology, but I could be wrong?)
My impression is that people are _wildly_ misunderstanding what this _actually_ is, and running wild with speculation/interpretation.
>if OP is just living here on a tourist visa and doesn’t have any form of residency at all, and (s)he’s still following the rules as established
No, I don't think they are. I think if you're _living_ here on a tourist visa, that's very much "abusing the visa".
Are you thinking about Intents? That lets Siri interact with data (and perform some actions in them) from your apps, but it is something completely different.
You can definitely expose things from your app via Intents that will end up calling an external arbitrary LLM somewhere, but it does not require using Foundation Models API whatsoever.
But if they're here on a Digital Nomad visa, then their stay is limited to 6mo with no pathway to extending this — _I_ personally don't think that qualifies as "living" in a place, but perhaps reasonable people can disagree on this point.
Not for any reasonable definition of "live in", you can't.
That's pretty rich, gotta say!
I'd genuinely like to understand where you're coming from more.
I think we're all in agreement that this framework is very much about letting developers swap the models easily, and treat them as commodities. That seems pretty obvious.
I do however still don't see how this has anything to do with controlling the UX (or the new Siri for that matter! The new Siri doesn't use Anthropic models, and there are no extensions point for it to do so — that's pretty much the whole reason why it won't be available in the EU).
Help me see your point of view!
They are.
That API has no user-facing components, and has no influence over UX of what the end-users are interacting with.
The users won't know if you used Foundation Models API or integrated with OpenAI/Anthropic/Gemini SDK directly.
Special emphasis on the "isn't compiled in yet" and "or construct one" bit.