Live data from Hacker News

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

blog.elis.cc

151–160 of 163 posts

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

#151
post #145

Earlier quoted context omitted.

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").

I'm not an LLM engineer, but I just got an idea of how it could work, combining CoT + checkpoints :

- use checkpoints to save KV cache before trigger CoT

- trigger CoT, save result as a summary

- go back to previous checkpoint

- instead of generating tokens, add result of CoT summary as input tokens

- continue normally

For the price of twice the KV cache memory, the context stays perpetually small, allowing smarter sessions. You can even apply that continually by summarizing tool calls, etc.

This idea is free.

I'm not sure it's that advantageous though: it consumes more memory, and the sessions are already quite long at 1M+ tokens. One would need to run the economics down, and just test if the shorter sessions are actually smarter with the continuous summarization.

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

#152
post #101

I had a similar experience with Google's support this year when I logged to my older Google account from a new device, and I was automatically logged out from everywhere, when I was trying to login again it asked me to provide an OTP, when I asked the form to send me the OTP, it said that I've done so many attempts. Later, I learnt that this is actually very common problem, if you see the "Me too" count on the Google…

I'm now at the point where I cannot create a new Google account as my phone number "has been used too many times".

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

#153

Earlier quoted context omitted.

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.

That's just a standard nanny filter. The filter realized it was in the process of saying "sexual assault" or the like, and just shut the conversation down.

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

#154
post #15

I get this sort of thing constantly because my domain, 3e.org, which I have had for 30 years, is apparently impossible. It's either too short to be real, or starts with a number (obviously impossible). And like the author, 90% of the time I can just disable their front-end validation and go on my merry way.

ahaha I still remember when 3com forced icann to allow leading numbers and that was some shitstorm

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

#155
post #154
post #15

I get this sort of thing constantly because my domain, 3e.org, which I have had for 30 years, is apparently impossible. It's either too short to be real, or starts with a number (obviously impossible). And like the author, 90% of the time I can just disable their front-end validation and go on my merry way.

ahaha I still remember when 3com forced icann to allow leading numbers and that was some shitstorm

Huh? From RFC1123:

2.1 Host Names and Numbers

      The syntax of a legal Internet host name was specified in RFC-952 [DNS:4].  One aspect of host name syntax is hereby changed: the restriction on the first character is relaxed to allow either a letter or a digit.  Host software MUST support this more liberal syntax.

It's from 1989. ICANN was founded in 1998.

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

#156
post #123

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.)

Backtracking, of sorts. The LLM descends a seemingly fruitful path, and all of a sudden that path seems less so. So you backtrack a few tokens ("erasing"/"undoing") and resample the probability distribution a bit back in the stream.

Would it retain some memory of the fact that it backtracked? That path becoming less likely somehow?

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

#157

Earlier quoted context omitted.

ChatGPT does this. It will present an initial response, then change its mind partway through the thinking process and present a different response.

Oh wow, I'd like to see this. Any prompt which reliably triggers it? (Seahorse emoji comes to mind!)

It does it quite consistently on higher reasoning.

I believe they have made display answer a tool call so that it can keep updating its answer as it thinks, instead of doing all the reasoning up front, essentially inverting the usual flow. You can use this pattern with any model that supports tool calling.

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

#158
post #123

Earlier quoted context omitted.

Backtracking, of sorts. The LLM descends a seemingly fruitful path, and all of a sudden that path seems less so. So you backtrack a few tokens ("erasing"/"undoing") and resample the probability distribution a bit back in the stream.

Would it retain some memory of the fact that it backtracked? That path becoming less likely somehow?

Yeah that's what I was imagining. No idea how though, so this is just rambling on my part :)

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

#159
post #155
post #154

Earlier quoted context omitted.

ahaha I still remember when 3com forced icann to allow leading numbers and that was some shitstorm

Huh? From RFC1123: 2.1 Host Names and Numbers The syntax of a legal Internet host name was specified in RFC-952 [DNS:4]. One aspect of host name syntax is hereby changed: the restriction on the first character is relaxed to allow either a letter or a digit. Host software MUST support this more liberal syntax. It's from 1989. ICANN was founded in 1998.

It's all ancient history, but before 3com domains with a leading digit 'just weren't done'. When they forced that through there was a general consternation on what crap internets are becoming.

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

#160

I can only presume this regex is there because Google had to block various scammers trying to use email hosting donain names when novel TLDs came onto the market. You can try to manage gmail.zip or outlook.mov but Google will probably flag you as a scammer if you try to email from them. Just because web.de isn't well-known outside of German circles doesn't mean the risk doesn't exist. These email providers, especiall…

  > "gmail.zip or outlook.mov" will probably flag you as a spammer
  > "web.de isn't well-known outside of German circles"
I'm not sure that "gmail" or "outlook" would cause people to think that the sender was in some way "authoritative", but I can understand the organisations wanting to discourage potential pretexting (plus the trademark violation).

I'm not sure how "web.de" or "web.one" would be perceived as especially trustworthy though.

"It must be genuine, it's from the official Web"?

Post reply on HN