Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • Seems like a monopolistic move.
    by ferfumarma
  • At least you got a heads-up. Few months back GCP "Agent Studio - Build" failed compiling the code in sandbox with a vague error message. Spent weeks troubleshooting, spoke to google engineers and reps, sending code, step by steps, screenshots. No one had a clue, until I switched from Firefox to Chrome out of desperation and it worked without a hitch.
    by wwizo
  • I love that google always sends useless canned responses after basically requiring you to perform a blood sacrifice to get ahold of anyone.
    by nosioptar
  • It states something about "your organisation's security requirements", do they document what requirements cause this rejection page? Some kind if changed default perhaps?
    by jeroenhd
  • It appears website developers desperately want to return to a world where browsers actively pretend to be another browser*.

    Want to check for DBSC? Enjoy not knowing whether the browser vendor decided to just roll a simple software implementation.

    Nothing good comes from browser detection over feature detection anyways. It's time to do away with user-agents and other overt identifying markers, and if we're still not in a better place, aggressively start stubbing features.

    * to some degree they still are. Firefox still ships with an user-agent override list for certain websites that have outdated user-agent sniffing for feature detection (and other fixes in about:compat).

    by chmod775
  • Hi folks, blog author here.

    Few comments based on common threads

    - No we don't have, or use, IAP and haven't configured it

    - Yes I'm the admin so can confirm this

    - "Context aware access" is only available on enterprise, we're just on "Workspace business plus"

    Happy to answer any other questions

    by RichardoC
  • Is it not:

    https://knowledge.workspace.google.com/admin/security/create...

    The Org admin can put all sorts of restrictions on who can do what based on the client device setup.

    by lokar
  • This is not a Google-wide thing… this is from Google’s Context-Aware Access product, which is configurable in Google Workspace environments. OP should direct their ire at their corporate IT or infosec team.
    by bgc

Explore Birbla archives