Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. San Francisco Onion Futures Company(onionfutures.com ↗)
    10comments
  2. Android 17 is the first since 3.x to add new APIs without releasing to the AOSP(grapheneos.social ↗)
    334comments
  3. Science Is Open Software(jepedersen.dk ↗)
    15comments
  4. SDCC – Small Device C Compiler(sourceforge.net ↗)
    8comments
  5. Cloudflare Quick Tunnels(cloudflare.com ↗)
    268comments
  6. How OpenAI Used Its Own LLMs to Design Its Jalapeño Chip(ieee.org ↗)
    69comments
  7. Typesafe-computer-use drives a Mac toward a goal for 1/50th of a cent per step(github.com/awlevin ↗)
    2comments
  8. Saving another 100TB of RAM(cloudflare.com ↗)
    58comments
  9. NASA-IBM Lunar Foundation open-Source Geospatial AI Model(usra.edu ↗)
    discuss
  10. How to Write with an LLM(sockpuppet.org ↗)
    304comments
  11. Show HN: Seal – Letters and passwords that open for your family after you die(github.com/jasonepage ↗)
    discuss
  12. Why building a Rust LSP is hard(rust-glancer.github.io ↗)
    11comments
  13. Xcode 27.1 Beta Release Notes(developer.apple.com ↗)
    75comments
  14. The first new cat species discovered in 100 years(nationalgeographic.com ↗)
    81comments
  15. Show HN: Cactus Needle 3: 8-29MB automation models can match DeepSeek V4 Flash(cactuscompute.com ↗)
    81comments
  16. Photon-Emission-Guided Laser Fault Injection Enables RP2350 Secure Debug(ledger.com ↗)
    61comments
  17. Harm Laundering in GPT Models: Gender Discrimination Transformed Rather Than(arxiv.org ↗)
    discuss
  18. OpenJev(openjev.com ↗)
    250comments
  19. The Farnese letter(simonklee.dk ↗)
    5comments
  20. Cache-to-Cache: Direct Semantic Communication Between LLMs (2025)(arxiv.org ↗)
    12comments
  21. Cyclomatic Complexity in C#(ndepend.com ↗)
    16comments
  22. Minimal Phone 2(minimalcompany.com ↗)
    199comments
  23. LispBM is a concurrent Lisp for microcontrollers with message passing(lispbm.com ↗)
    3comments
  24. Claude Code now reads AGENTS.md if there is no Claude.md(claude.com ↗)
    208comments
  25. Goroutine Leak Profiles(go.dev ↗)
    1comments
  26. Show HN: LiveWorld – Every 24/7 YouTube live camera on one globe(liveworld.info ↗)
    32comments
  27. Alibaba open-sources AI model that can detect cancer and nearly 150 conditions(scmp.com ↗)
    10comments
  28. Warez: The Infrastructure and Aesthetics of Piracy (2021)(archive.org ↗)
    39comments
  29. Inside ZCode: Silently uploading your Git history to the cloud(ferstar.org ↗)
    94comments
  30. How SpaceX streamlined the Raptor engine(construction-physics.com ↗)
    56comments

Ask HN: Locked out of Google Aps email with no recourse - advice?

9 pointsby 11y ago
11 comments
I've been locked out of my Google Apps email for over 24 hrs due to "suspicious activity". I am the admin of the domain so "contacting my admin" is of no help. Filled Contact Us form and spoke to customer support lady who is unfortunately clueless and cannot help me at all.

Terrible experience for such a mission-critical service.

Anyone has suggestions on how to deal with this to restore access?

PS: I did not sent out any spam or do anything that goes against their ToS. Just a loyal customer for 7 years doing normal day to day emailing.

11y agoHN ↗

Yes. I enter my credentials and it says my account is suspended.

11y agoHN ↗

Email is a critical communication channel. Don't put up with this sort of crap from any company. If you control your domain and have capability to modify records. Buy mail service from another provider and redirect MX record to new service. And if you can estimate approximate value lost due to this action and you are in U.S., send a bill to Google, file a small court claim against Google if unpaid for 30 days.

11y agoHN ↗

I totally agree with you for the medium term. My challenge right now is that I don't have access to the DNS records and migrating to a new email service will take days/weeks.

11y agoHN ↗

Migrating to new email service doesn't take days/weeks, at best a few hours as long as you were prepared with existing email aliases (catch all can help minimize the missing aliases) and configuration and access.

In the short term, you are at the mercy of Google. Next time you want to avoid similar fiasco, when you purchase any service from a vendor, please consider the whole offering from sales to support. If you don't see a quick resolution pathway for situations when shit hits the fan, walk away from those vendors.

Personally, I have never bought or recommended others to purchase any "paid" services from Google. They are incapable of and not setup for providing enterprise level product, service and support.

11y agoHN ↗

Which email provider do you recommend? I am ready to switch after another full day of BS from their support staff.

11y agoHN ↗

How long it takes to switch services depends on how long you have your TTL set on your MX records. If he set it to expire after days or weeks, it would take days or weeks to switch services. Usually the default is a much lower value, but there are some legitimate reasons to want a high TTL (It could help mitigate a domain hijacking for example).

11y agoHN ↗

Were you on the free or the paid plan? I am guessing if you were on the paid plan, you would have more recourse?

11y agoHN ↗

Unfortunately it's the same deal for free and paid.

11y agoHN ↗

Probably not what you want to hear, but I'd avoid Google for any mission critical things, and any business model that relies on Google products for revenue (YouTube, AdMob, AdSense). Their automated "fraud detection" algorithms frequently have false positives and ban innocent users, without chance to appeal and have recourse. Terrible customer service.