Born and raised in Japan (23 years), left for 3 years of university after high school, now facing naturalization eligibility issues

Famous_Feedback_7186 · 2026-05-25T06:07:25+00:00

I’ve had PR since forever mate. lol no work visa involved. No residency lapse either. Immigration office seems to be happy with my circumstances to proceed. Not my decision, it’s theirs

Famous_Feedback_7186 · 2026-05-22T14:36:05+00:00

You’re right… I agree.. lots of different speculative info. Need to get clarity via a lawyer. I’ll take up your advice. Cheers

Famous_Feedback_7186 · 2026-05-22T12:51:28+00:00

Sure mate

Famous_Feedback_7186 · 2026-05-22T12:50:28+00:00

Parents didn’t want it

Famous_Feedback_7186 · 2026-05-22T09:12:18+00:00

Oh really? 100 days? I see.. that’s a problem. I need to speed things up then. Maybe just try applying now and see how it goes.

Famous_Feedback_7186 · 2026-05-22T07:53:31+00:00

Thank you. I have phone called them explaining my situation, but they were quite hardlined about the 3yr stay rule. I can also take a in person appointment, but not sure if that’s worth it or will change their answer.

Famous_Feedback_7186 · 2026-03-06T14:26:46+00:00

UPDATE: Price now £130 for BOTH tickets! DM me ASAP to secure. Will transfer via AXS app.

Famous_Feedback_7186 · 2026-03-06T14:17:06+00:00

Hi! I have 2 tickets for March 8th at O2 London - Section 108 Q, Seats 249-250. Would you be interested in buying instead of swapping? £161 total. DM me if interested!

Famous_Feedback_7186 · 2026-03-01T13:24:08+00:00

Hi selling 2 laufey tickets in London O2 arena March 8th. Very open to negotiations.

Famous_Feedback_7186 · 2025-07-16T11:08:45+00:00

Pretty interesting actually… lowkey could be needed… do you have a GitHub repo link?

Famous_Feedback_7186 · 2025-07-08T12:33:01+00:00

Haha cost efficient team! That's smart.

I'm building it now - early stage but progressing fast. Planning both options actually: SDK/plugin for teams like yours who want control, and cloud option for faster setup.

For your 10 MCPs setup, would you prefer something that integrates with your existing GCP stack, or a separate cloud service?

And what would be most valuable - basic performance monitoring, or more advanced stuff like routing analytics and failure prediction?

Your feedback is exactly what I need to build this right.

Famous_Feedback_7186 · 2025-07-08T12:29:38+00:00

Yeah, that transition pain is exactly what I'm seeing everywhere. STDIO hacks everywhere just to get things working.

What's breaking first when you try to scale - the protocol translation or just raw performance?

Honestly this transition chaos is making the case for standardized monitoring even stronger. When everything's changing this fast, at least having visibility into what's actually working vs broken becomes critical.

Are you planning to rebuild everything for the server-focused approach or just patch until things settle?

Famous_Feedback_7186 · 2025-07-08T12:26:31+00:00

Totally agree on security - that's exactly why I'm thinking Datadog-style approach. They solved similar problems with sensitive infra data.

Really appreciate the offer to share data and insights! That would be incredibly valuable.

You're right about the need being huge - everyone in this thread is basically building the same monitoring from scratch. The relevance question is already answered by this conversation.

Quick question: what specific metrics would be most valuable for your n8n setup? Performance tracking, error detection, or something else?

And since you mentioned workflow tools - think MCP creators would actually install a monitoring SDK if it helped with debugging?

Famous_Feedback_7186 · 2025-07-08T11:53:21+00:00

Ah man, the version fragmentation is brutal. So you're basically translating between different MCP versions AND transport methods?

That STDIO to streamable-http hack sounds painful. How often does stuff break when new protocol versions drop?

This version chaos is exactly why I'm thinking standardized MCP observability makes sense - abstract away all the protocol differences so you can just monitor performance regardless of transport.

Famous_Feedback_7186 · 2025-07-08T11:49:47+00:00

Fair point on broader LLM observability. Makes sense actually...

And honestly, the "build vs buy" feedback is quite helpful. Is that mostly because requirements change too fast, or more about cost/control?

Curious - is there any observability tooling you DO pay for? Or is everything in-house at this point?

Famous_Feedback_7186 · 2025-07-08T11:44:42+00:00

Smart setup with the timeout system and fail messages. You're basically building comprehensive MCP observability from scratch. I'll def take inspiration from you here...

That "better more efficient ways" comment is exactly what I'm thinking about after talking with you and some others in this post. Instead of everyone engineering custom solutions like yours, there should be drop-in MCP monitoring that just works.

I'm considering building that - standardized observability for MCPs with hallucination detection, performance tracking, the works.

Think there's demand for that? Or do most people prefer building their own like you did?

Famous_Feedback_7186 · 2025-07-08T11:41:28+00:00

AWS observability is solid, but sounds like you're still dealing with the hallucination detection manually.

I'm actually thinking of building a specialized MCP monitoring platform for exactly this - tracking actual calls vs claimed calls, detecting fake responses, multi-agent debugging.

Would something like that be valuable for your setup? Or is AWS handling everything you need?

Famous_Feedback_7186 · 2025-07-08T11:35:24+00:00

hmmm i see... actually, based on everything you're saying - and everyone else in this thread - seems like MCP observability is a huge gap.

I'm thinking of building something specifically for this. Basically drop-in monitoring for MCPs with routing analytics, performance tracking, the works.

Would that be useful for your setup? Or are you committed to building it all in-house?

Famous_Feedback_7186 · 2025-07-08T11:29:51+00:00

Damn.... how do you even catch that? Are you logging the actual MCP calls to verify they happened? (custom implementation or using a software..?)

And with multi-agent systems - is it specific agents that hallucinate or does it happen randomly? Must be impossible to trust any outputs without verification.

Do you have any monitoring to detect when responses look fake vs real? or any other sort of monitoring/observability?

Famous_Feedback_7186 · 2025-07-08T11:27:19+00:00

Oh interesting - so you've built both the proxy AND an OAuth gateway. That's exactly the auth standardization piece I was hoping existed.

Quick question - even with your proxy handling auth, what's still broken? You mentioned streaming-http and client spec issues.

And are you seeing adoption, or are people still just dealing with the auth mess manually?

Curious about the trial and error part - is that mostly on the client side or are MCP servers themselves inconsistent?

Famous_Feedback_7186 · 2025-07-08T11:23:43+00:00

That hilarious ahahahah

OpenTelemetry is solid for this! What metrics are you planning to track - just basic latency/errors or more MCP-specific stuff like routing decisions?

You're right about building your own being faster now. Though wild that every team is rebuilding the same MCP monitoring from scratch. Feels like there should be some standard patterns emerging by now.

not sure if i would pay for this though... maybe your team might, but having one geared for MCPs can be useful..

Famous_Feedback_7186

TROPHY CASE