> The ~2,500 MCP servers out there become composable CLI tools you can script and run in CI without an LLM in the loop
That's pretty cool.
The harder part is getting the various coding agents to run !mtpcli by default + getting cli tool maintainers to add --mtp-describe. Creating a standard is hard, I guess.
Check out the Google I/O video I mention in the article if you need convincing. As far as not collecting user data fo privacy reasons, I think brandon0's comment says it all.
Yeah, we do that kind of stuff as well. At least you know what your data means. But when you start getting millions of hits a day, you won't necessarily want to spend some time scaling your system... In that case leaving it to the pros and focusing instead on your product may prove the most sensible move.
Custom variables don't let you consolidate on users though? In the visitor count, for instance, I don't think there's a way to tell GA to use a custom var to distinguish between visitors.
Agreed, these are edge cases. They did create a lot of questions for me though, and made the whole thing rather confusing as a user.
As to how much of an issue these edge cases represent, I find it hard to get a real sense of it. I guess it really depends on the situation, what you want to measure and the user experience you offer to your visitors.
The fact that it links accounts retro-actively though can be dangerous, in the scenario of publicly-accessed devices. I'll have to admit though, this is not the common case.
I guess my personal gripe with what MP and KM are doing boils down to: if you can't infer stuff about who is visiting my website, be honest about it and don't.
I think Alex meant OSX, not iOS here. As for Linux, he's right that it's mostly a matter of packaging - which I think puts the prospect of a Linux release closer than that of an OSX release.
You can check out the streaming part of the site at fleex.tv/Home/Streaming. We have a large selection of videos, from TED talks to web series to web-produced movies.
Just click the 'MY ACCOUNT' link and create an account. Don't tick the 'no newsletter' box to make sure you'll get the news when the player is out. We'll probably post something here as well when it gets out anyway.
These are all good ideas, that we've of course considered and been pondering for quite a while now. There are various difficulties associated with them, at various degrees. Personally I tend to think that in most cases, ideas are relatively cheap: finding the right way to implement them in a way that's highly scalable really is the hard part.
We can of course chat sometime this week - as a teacher, we'd of course love to hear what you have to say. Could you maybe send us an email (see our contact page) with your availability?
I get your concerns - this is precisely why we added adaptative subtitles as one of our first features. So people could say: "I'm a beginner, keep 80% of the subtitles in my native language", vs. "I'm a more advanced speaker, let's go ahead and put 100% of the subtitles in English".
That's pretty cool.
The harder part is getting the various coding agents to run !mtpcli by default + getting cli tool maintainers to add --mtp-describe. Creating a standard is hard, I guess.