Not a chance, they cannot deny entry to a legal us citizen. They can however detain one at the border if some criminal charge can be made.

To the US citizen?

How are they going to prove the phone was not clean to begin with? What if he wiped it up on the plane before even border crossing? Is this still 'destroying the evidence' ? Yea - this is very sketchy. Advice for regular criminals - you just come through with a clean phone. For the rest of us mortal, expect you browser history to be exposed.

Well - but are you still forced somehow to tender the self incriminating evidence? Is 'destroying evidence' equivalent to 'refusing to cooperate' (as in not givin up the password? What if the phone was wiped out on the plane?

Sustained! My ca2008 SunPower (RIP) still works at full capability (or at least not noticeable degradation). The inverters though, are dying (only last 8-10 years due to design issue in voltage sensing circuits, not even power parts, sic!). There are non-replaceable as the SP used non-standard grounding polarity.

Thanks for the article. It does start describing the 3 computers as TTL based with wire memory but then later describes a design move to CMOS for both logic and memory.

Oh dang, TTL? That is power hungry! I guess in early 70s there were no CMOS ICs?

As much as first incident could be considered a mistake and perhaps handed by an apology, the second one is clear neglect and should end up in penalty and remedy.

Out of curiosity I have checked what CPU ISs were available in '77, there was 6502, 8080, Z80 (10x speed of viking's CPUs) albeit all done in NMOS, and NMOS is susceptible to radiation. Hence, the Viking's CPU were build on low-density CMOS discrete logic instead. Also better for power consumption. But I agree that 21th century equipment is designed with few years life span. Use and refuse, but not reuse.

I keep flipping between "he is a village idiot" to "he is village monster abusing circumstances". I dunno. When i see his speeches and behavior, defiantly an idiot, very lucky idiot that is exploited by gray eminences perhaps?

And more demand, due to gas prices. Thanks go to the president for making electric cars more desirable.

Ah!

> Dropping the protocol-level session doesn’t force your application to be stateless. If your server needs to carry state across calls, mint an explicit handle from a tool and have the model pass it back as an argument. We found this works better than session state hidden in the transport - the model can see the handle and thread it between tools.

Most of my MCPs require context and are not stateless. A gdb mcp needs to hold on to a debugee. Multi step operations will require context like open, edit edit close.
So something need to hang on the 'other side' to these contexts. Yea the 'server' implies this, I understand but who then manages the live of the instance of the local MCP? This is notoriously left for the harness implementer and notoriously is done differently in each. Some are local to session, some are global and shared between sessions, hence mixing contexts possibly.
Maybe there is a need for local/tools MCP-like spec?

Hmm - no my experience. Almost the opposite. Structuring the code is often hard for lazy humans. I see a lot of very well structured code from AI and this is more a telltale of AI. Good comments as well though their pedantic correctness is again purview of AI. (Mostly C++ and Python on my side).

But alas, by this flat refusal do they not shoot their feet off? There is a lot of good this tool can do. Rather, just penalize submitting AI slop as it burns reviewers energy?

Some are obviously AI-generated. But there as the code quality gets better how would it be distinguishable from human written? Less bugs?

And at that - would they use AI to find out if it was AI-written?