Why Some People Love the Trump Type and Others Can’t Stand It

There are broadly two types of people when it comes to someone like Donald Trump. Trump constantly promotes himself. He doesn't seem particularly embarrassed by self-promotion. He can say, in effect: "I'm the best. I'm successful. I'm great." Most people, at least internally, would probably have a reaction like: That sounds very arrogant. How could … Continue reading Why Some People Love the Trump Type and Others Can’t Stand It

AI Degradation in Long Contextual Conversations

Context degradation is real. This session started with a long summary of prior work which is useful for continuity but it also means: stale information gets treated as current, AI check memory which could be outdated. The more context I carry, the harder it is to distinguish what's verified vs what's just noted. lose track of user's question … Continue reading AI Degradation in Long Contextual Conversations

Deploying MedGamma Mini Model Locally and Create an MCP Server

I have an idea to let MedGemma become the specialized local engine, MCP becomes the interface, and Claude/ChatGPT becomes the high-level reasoning/orchestration layer. The flow would be Claude Desktop sends a tool call → the MCP server builds a prompt → llama-server runs MedGemma inference on CPU → structured JSON comes back to Claude. Deploying … Continue reading Deploying MedGamma Mini Model Locally and Create an MCP Server

The 4 Common OAuth/auth Patterns for MCP Servers

1. Standard OAuth 2.1 (MCP spec-compliant) Who uses it: Remote/hosted MCP servers (e.g., a server on Fly.io, Cloudflare, etc.) How: Full OAuth 2.1 flow — the MCP server is a resource server, a separate auth server (Auth0, Okta, Keycloak, etc.) issues tokens. Client discovers auth server via /.well-known/oauth-protected-resource, opens browser with PKCE, exchanges authorization code for access token. Example: An MCP … Continue reading The 4 Common OAuth/auth Patterns for MCP Servers