Live data from Hacker News

Google Workspace thinks my domain is an email provider (2025)

blog.elis.cc

141–150 of 163 posts

Re: Google Workspace thinks my domain is an email provider (2025)

#141

Earlier quoted context omitted.

Has anyone ever tried giving LLMs a backspace? I have long wondered if their responses could be better if they had the ability to correct earlier parts of their text. Imagine how much harder it would be for us to write coherently with no backspace!

Chatgpt will erase text it wants to censor if you get near sensitive topics.

What sort of prompt would exercise this?

Re: Google Workspace thinks my domain is an email provider (2025)

#143
post #5

I would hope that somewhere at Google there is a policy that says you can't do anti-fraud and security checks in frontend only...

But isn't the web so much better now that everything is client side instead of server side?

I still think client side JS apps are the biggest mistake this industry ever made.

Re: Google Workspace thinks my domain is an email provider (2025)

#144
post #129

Earlier quoted context omitted.

It's not exactly this. It's something like it. But it's not a token that erases a previous token. Not that I know how that would work or how you'd get training data (edit histories of internet comments seem too few). (You could have a token that hides previous tokens, but that'd be rather closer to CoT.)

I'm not sure how that would work. You'd need to be able to reverse the operations in the KV cache, and I'm not sure if it's doable or not. And then you'd need to pick another path, or "rebalance" the probabilities or you'd go the same token path. CoT is probably easier to implement (but not necessarily better).

You could set up checkpoints where you store off the current state, and roll back to those checkpoints?

Re: Google Workspace thinks my domain is an email provider (2025)

#145
post #129

Earlier quoted context omitted.

I'm not sure how that would work. You'd need to be able to reverse the operations in the KV cache, and I'm not sure if it's doable or not. And then you'd need to pick another path, or "rebalance" the probabilities or you'd go the same token path. CoT is probably easier to implement (but not necessarily better).

You could set up checkpoints where you store off the current state, and roll back to those checkpoints?

Definitely, this is the easy "bruteforce" way, but it would require more memory, and would not resolve the second part of the problem (i.e "how to pick a better path").

Re: Google Workspace thinks my domain is an email provider (2025)

#149

Earlier quoted context omitted.

Chatgpt will erase text it wants to censor if you get near sensitive topics.

What sort of prompt would exercise this?

I inquired into a court case against a police officer who committed a sex crime. I only wanted to know the disposition of the case with no details. It briefly spit out a response involving the victim and wiped it away with a refusal to answer more questions. This was a year ago and the behavior may have changed by now.
Post reply on HN