koito17

All I get are train stations unless I decide to input the city instead of the street... but then the areas are no longer 30-minute walks!

Interesting failure mode, but I like the concept overall.

The law is somewhat vague. You have a "duty to make efforts" (努力義務) in rescinding your foreign citizenship after electing Japanese citizenship. The Ministry of Justice has never clarified its interpretation of 努力 (i.e. what counts as "making efforts"?) I am friends with a few Japan-US dual citizens who have done nothing after electing Japanese citizenship; they are essentially gambling on a gray area of law.

Note if you acquire Japanese citizenship afterwards (or never had a second citizenship in the first place), then 国籍法11条1項 automatically voids your Japanese citizenship at the time you obtain a foreign citizenship.

I accepted I was reading LLM output by the time I got to

   None are constexpr — debugging is a runtime concern.

I am not very experienced with C++, but runtime debug functions are one of the last things where I'd expect compile-time computations. Inlining? Sure. Doing anything else at compile-time? Not really.

The sentence feels like a remark about something a human reader is very unlikely to be thinking about.

Well-designed cryptographic systems are designed so that you can understand everything about the system and still not get inside.

It's pretty much the exact opposite of security through obscurity.

> It's going to be the banks first.

In Japan, this is already the reality. The FSA required brokerages to implement passkey authentication, and the effect is that it's no longer possible to have a brokerage account without a passkey. (Some brokerages, like Nomura Securities, will offer two separate client portals. The portal with money and trading-related functionality requires a passkey).

The thing that sucks a lot is that brokerages seem to also restrict the allowed software/hardware. Don't know the details, but none of my FIDO2 hardware keys were able to be used. I consistently use these hardware keys through WebAuthn, so I was surprised when my brokerage explicitly told me my hardware key is unsupported and I must use either Windows Hello or the iOS Passwords app.

The FSA's official explanation for mandating passkey implementation is that people kept falling for phishing attacks, and the attacks were getting too sophisticated thanks to "AI" or something.

I swear I've seen these "[Latest macOS release] does not appear in UNIX certification site" threads every year since the release of Big Sur in 2020.

It takes several months for the certification to appear on the site. What would be newsworthy is if we see a release next year without this release getting certification.

Even then, visual diffs were pretty flakey for web development, because one's OS and browser choice would slightly alter the exact pixels blitted to the screen. At least this was the case for the tests that would simply match pixels instead of computing a sort of visual hash.

It's also partly why some people preferred snapshot tests that compared the DOM tree instead, though that was brittle in other ways (e.g. tests would break if an application's frontend used a major UI library and an update to the library permuted the order of classes in some part of the HTML).

There's quite a few implicit assumptions in that.

In my case, I am double-taxed (both Japan and US side) on capital gains. Tax treaties reduce, but not eliminate, the extent of double-taxation.

Many US-based brokers do not allow Americans abroad to purchase mutual funds, so VFIAX is not a choice for me.

Maybe I can go with eMAXIS Slim All Country... Oh, but that is a PFIC under IRS rules and I'd be taxed on unrealized capital gains. So I guess no Japan-equivalents of VT for me. That's fine, I guess I'll just buy VT in my US-based brokerage account; but now I'm in a suboptimal spot with respect to monthly contributions, calculating JPY-denominated income tax on dividends, etc.

I even made an implicit assumption when I said "calculating JPY-denominated income tax on dividends". That assumes your tax status is permanent resident. If your tax status is non-permanent resident, then a decent financial advisor will recognize that only the extent of income remitted to Japan gets taxed, so VT distributing at all isn't an issue (until 5 years later). What should you do before the 5 year threshold is hit? etc. etc.

But yes, if you're born in America and plan to stay within the same state for the rest of your life, then a 100% automated setup that simply deposits $1,000/mo into VFIAX is probably fine. (But keep in mind, to most non-Americans, VOO is not really diversified compared to funds like VT).

Otherwise, there is value in consulting someone (or something) that regularly handles taxes and financial planning.

Users generally have no way to verify that a third-party provider, even if they advertise themselves as privacy-focused, will adhere to their own terms. This is similar to the issue of privacy-focused VPN providers that claim to not log user activity (and then end up leaking user activity). You can get proof of ~P, but rarely proof of P, and often times the proof of ~P is due to police raids, data breaches, etc., not something of the provider's volition.

What you can possibly audit is probably data sovereignty. For instance, I would not be surprised if Mistral's customers demand concrete evidence that their data is held within the European Union. But that is a distinct issue from training on input tokens.

GP's point is about "sending tokens to someone else's computer" versus "keeping the tokens locally". I think model capabilities are secondary.

In May of this year, I was running qwen3.6:35b-a3b on my MacBook (bought in 2024). Obviously not as fast as, say, running a model on Cerebras, but a year ago it wasn't really feasible to have a local model running on my 2024 laptop with vision support. (Concretely, I was passing apartment diagram pictures to Qwen and making it compare different apartments for which ones would feel the most spacious while optimizing for initial moving costs and other factors.)

This was back in May and I wouldn't be surprised if there have been significant improvements since then.

Overall, I think it's fair to compare a workflow like "use llama.cpp locally to upload some pictures and ask questions" to "open the ChatGPT app, upload pictures from your phone, and ask questions". Sure, you can't run a model like GPT-5.4 locally, but the model is mostly an implementation detail here. What a user will care about is: "when I go with the llama.cpp option, am I getting useful information from my conversations?"

It looks close to the kind of documentation artifacts GPT 5.6 Sol would generate for me.

That style is still rare enough that I prefer it over OP's "we installed shadcn + Tailwind and look like every seed-stage startup SaaS from 2024" style.

The Japanese word used in the context of price lists would be something like 料金表 or 料金メニュー.

When I see "tariff", my mind only thinks of 関税 , and I was just as confused as you were. Turns out its just an item in a price schedule.