sean_lynch
The real valuable capability MCP offers over skills/CLI is isolating the auth flow outside of the agent’s context window, and potentially out of the harness completely. This is valuable from a security perspective obviously. It’s also just a much easier user experience for normies and large businesses adopting AI tools. I hear all the context bloat and tool call redundancy complaints. But this structure for handling auth has real value.
Maybe the idealized form of MCP is just an auth gateway for the API and nothing else. That’d still be a win.
It looks like there's still plenty of hard problems in the indexing side of RAG and so maybe the vector DB that leans hard in that direction will carve out something defensible? Outside that, can't find a good reason to standup yet another piece of infrastructure purely for vector search.
Using Server-Sent Events (SSE) in Flask to stream ChatGPT
Poolside – Former GitHub CTO starts foundation model startup
https://github.com/openai/chatgpt-retrieval-plugin#memory-fe...
Learning Rust with ChatGPT, Copilot and Advent of Code
Asana S-1
FWIW - I don’t like that you stuffed everyone into the same t-shirt :)
https://www.sfmta.com/reports/original-2018-scooter-applicat...
This seems to be a marketing video for Apollo's products. Is that what most GraphQL stacks look like in production these days?
Udacity launches self-driving car nanodegree
Migrating from PostgreSQL to DynamoDB
Using the Dropbox Datastore API in Python
Introducing the Dropbox Sync API
Just to dive in a bit for the HN crowd: We base the changes that should be applied to your Dropbox on whether the client has successfully synced the previous version of the file. The server doesn't allow the client to apply changes unless the client is fully up to date. And in the case of deletions, the desktop client is only permitted to issue deletes to files that have been successfully created on disk and then later deleted.
We also have a proper support team to catch things that fall through the cracks, and if you have issues, you should reach out to them first (and as soon as you notice; their ability to fix things becomes harder the more changes you make to your account).
Again, not commenting on the above issue, but I did want to point out that we take the integrity of your data very, very seriously.
For most cases though, users should create a new account for the team. The Dropbox for Teams sign up process guides users towards creating a new account when joining a team for this reason.
tl;dr: The scenario described by the OP is now less likely to occur. Since October, individual Dropbox users are encouraged to create separate accounts when invited to a Team and warned that Teams admins will have control over the account.
We want individual and Team Dropbox users to have the best possible experience. Some users want to migrate their personal accounts into a Team. Others are much happier with separate personal and Teams accounts. We’ve been working to make that choice much clearer for the account holder and the Teams admin.
If users do choose to merge their personal account with a Team, things become a bit tricky. Teams admins want better control of data within a Team, and users want easy access to their personal stuff, but it’s not possible for us to differentiate between Team data and personal stuff in the same account.
Here are some thoughts on the points raised by the OP:
* Better support for multiple accounts: Users can quickly switch between using personal and Teams accounts on the web today and we intend to make this better across our platforms.
* Improved messaging to Teams admins: We plan to provide better messaging to admins before disabling an account that was migrated in.
* Disabled accounts are not immediately deleted: We can work with Teams admins and users to sort out account issues and recover users’ files.
We’ve contacted the OP to help resolve his case and are sorry for any pain this caused!