4 ms·
The text of their "tweet that got me fired" is: > Introducing the Google Workspace CLI: https://github.com/googleworkspac https://github.com/googleworkspac e/c
by stevage 4mo ago
The text of their "tweet that got me fired" is:
> Introducing the Google Workspace CLI: https://github.com/googleworkspac https://github.com/googleworkspac
e/cli - built for humans and agents.
> Google Drive, Gmail, Calendar, and every Workspace API. 40+ agent skills included.
Yeah, that absolutely looks like an official product announcement from Google. Surely it was obvious they'd get in trouble for that.
- etothepii 4mo agoIs the issue primarily caused by the English language? (Google Workspace) CLI vs Google (Workspace CLI) Because Google has there name in the product for which the CLI was produced it looks like he's using the Google brand when he's only using a descriptor of what his CLI was for. Trademarks are funny, but if I build a thing that only works with Google Workspace wouldn't it be a bit weird to not say that?
- zipy124 4mo agoProbably contributes to the fact. In Opensource to avoid legal threats for instance with USB/HDMI and the likes you usually say "Compatible with" to avoid claiming certification/trademark infringement.
- stevage 4mo agoGood point. "CLI for Google Workspace" would be less ambiguous.
- echoangle 4mo agoIf you launched a “google workspace cli”, as a random person not affiliated with google, wouldn’t you expect to get sued too? You could maybe try to get away with “CLI for google workspace” (although clarifying it with “compatible with google workspace” or something like that would be better), but the first one just sounds like it’s an official thing. If you namedrop a copyrighted name, you have to make sure that people won’t think you’re officially affiliated with that.