Live data from Hacker News

The session you cannot take with you

earendil.com

151–160 of 238 posts

Re: The session you cannot take with you

#151

I think most LLM work will migrate to open weight models in a couple of years for this exact reason (as well as price), unless the big providers manage to have their way and the market gets regulated in a way that favors closed source models. To me it seems though like most models are becoming good enough for most tasks we want them to do so no need to use the latest super intelligent one that knows how to compose op…

> (as well as price) LLM pricing is now Business Gacha - the whales will open more loot boxes and the normals will serve as fodder and feeder for them. > market gets regulated This MUST happen, but not in the way or for the reasons that any one thinks. There is a question of liability when one of these models causes massive damage to a 3rd party. If I am running an open source model on a "rented" platform and it goes…

The person who approves or uses the LLM output will be responsible of course. You can't just say "the computer did it" and expect to walk away. In the few cases I've seen, that seems to be how it's been going.

Even if it wasn't, the big players would lobby hard to make sure it isn't them.

Re: The session you cannot take with you

#152
post #64

Earlier quoted context omitted.

Only for people invited to the Tailnet. To create your own account, you still need a third party.

You can host your own identity provider. Authentik, Keycloak, authelia or Zitadel work. I don’t fully agree with tailscale’s decision to not want to be an identity provider but I understand it on some level. It simplifies their service greatly and the amount of asks for that will essentially have them build a full enterprise Entra-like solution that would be a constant maintain headache and they are not interested in…

Beyond simplifying their service, it allows Tailscale to have reduced responsibilities (because of reduced collection of sensible data), and makes them a less interesting target for people wanting access to the data (wether illagally by hacking, or legally from government agencies). This probably makes them less attractive as targets for censorship.

Re: The session you cannot take with you

#153
post #98

Earlier quoted context omitted.

I'm opposite. If my email goes down, or I do not have access to it, I cannot login. With passwords I still can.

My email is with Google. They are less likely to go down than my password manager.

Until one day your Google account gets locked with an automatically generated message that you violated an unspecified rule. Good luck getting contact to a human support.

Re: The session you cannot take with you

#154
post #61

This is an important article. I hadn’t realized it was already getting this bad. Like a frog enjoying a nice warm bath ... > Most people do not switch their operating system or phone provider every week either. But even if you do not utilize that freedom, it matters because it changes the relationship you have with the provider and the provider has with you. This is why it’s important to utilize your freedoms. Do NOT…

You are building a phone app for open code? You mean like fossify phone or?

no he means he's locked him self into a bloated and slow react based terminal ui.

waste of time. should be using pi mono

Re: The session you cannot take with you

#155

> “Most People Do Not Switch Models Mid-Session” I do, quite regularly. Because different models have different strength (for example when producing text for live presentations based on the text for a reading deck). Or when it comes to other aspects of the work. I regularly switch between open wheight models and closed models. I know, I am a tiny minority here. And this behavior only ever started a few weeks ago. But…

switching models mid session kills your KV cache.

you should fork or handoff or start a new one and tell the new one to read the old session.jsonl

Re: The session you cannot take with you

#156
post #10

Earlier quoted context omitted.

And yet people still go with Sign in with Google as the only login method.

I am guessing that's because Sign in with Google is the least of the evil, as compared to other popular OAuth Sign-in options like Facebook, X...

A password manager has an almost as efficient UX

Re: The session you cannot take with you

#158
post #49
post #28

OpenAI has been nudging their users toward the Responses API lately. Chat completion can still do everything if you are clever. The obvious reason to push everyone into the Responses API is that the reasoning process can be locked down and encrypted. The semantics of the chat completion API are fundamentally transparent. 100% of the tokens are visible. If you have patience and the willingness to endure a little bit o…

You don't see real reasoning tokens with the Chat Completions API; and 'store: false' with Responses really isn't that different to Completions. FWIW, if you have some tokens to spend, you might want to test Responses vs Completions in intelligence. Since GPT-5 models, we've consistently seen small, but statistically significant and reproducible improvements in intelligence with Responses API vs Completions. However…

[deleted]

Re: The session you cannot take with you

#159

Earlier quoted context omitted.

It’s odd, I just saw my first one of these today. Some former Figma person linked an AI site comp designer. I was going to give it a shot, but the only choice was a Google login. So very weird.

It's not that weird. Building a modern accounts system is a lot of work and people don't like creating new accounts. So it's the path of least resistance for developers and users.

I dunno, I’d say it’s never been easier.

If you’re building a paid service you’re probably already using cognito or supabase or something. That puts you a few clicks aways from 5+ other identity providers and normal accounts.

Re: The session you cannot take with you

#160
post #49
post #28

OpenAI has been nudging their users toward the Responses API lately. Chat completion can still do everything if you are clever. The obvious reason to push everyone into the Responses API is that the reasoning process can be locked down and encrypted. The semantics of the chat completion API are fundamentally transparent. 100% of the tokens are visible. If you have patience and the willingness to endure a little bit o…

You don't see real reasoning tokens with the Chat Completions API; and 'store: false' with Responses really isn't that different to Completions. FWIW, if you have some tokens to spend, you might want to test Responses vs Completions in intelligence. Since GPT-5 models, we've consistently seen small, but statistically significant and reproducible improvements in intelligence with Responses API vs Completions. However…

> You don't see real reasoning tokens with the Chat Completions API

That's because there are no "reasoning" tokens. That is the entire point of doing it this way.

One major advantage is that I can switch to a different provider if OAI starts to get weird about this stuff and be able to have a fighting chance of re-adapting my harness to the new vendor's model. If 100% of my reasoning process is outsourced into the proprietary blackbox, there is little hope by comparison.

Post reply on HN