Mojofull (@furoku)

Google Workspace의 공식 CLI 출시 소식입니다. CLI와 MCP 양쪽에서 사용 가능하다고 하며, 향후 많은 문서 작업과 자료업무가 채팅 기반으로 전환될 것이라고 전망합니다. 첨부된 작업들이 모두 채팅으로 수행될 수 있게 된다는 설명입니다.

https://x.com/furoku/status/2029366972945949018

#googleworkspace #cli #automation #chatops

Mojofull (@furoku) on X

■Google Workspace の公式 CLI CLIとMCPの両方で使えるので、近い将来、ほとんどの資料業務もチャットベースに変わっていくと思います。 添付のような作業がすべてチャットベースでできるようになっていきます。

X (formerly Twitter)

TestingCatalog News (@testingcatalog)

MiniMax가 MaxClaw 모드를 공식 출시했습니다. MiniMax Agent 내부의 신규 모드로 OpenClaw로 구동되는 항상 켜진 AI 에이전트를 10초 이내에 생성하며 Telegram, WhatsApp, Slack, Discord와 통합되고 10,000개 이상의 사전 구축된 Expert를 제공한다고 보고됩니다.

https://x.com/testingcatalog/status/2027743326732964200

#minimax #maxclaw #aiagent #openclaw #chatops

TestingCatalog News 🗞 (@testingcatalog) on X

MiniMax has officially launched MaxClaw, a new mode inside MiniMax Agent that gives anyone a fully operational, always-on AI agent powered by OpenClaw in under 10 seconds! Integrates with Telegram, WhatsApp, Slack, and Discord, and reportedly offers 10,000+ pre-built Expert

X (formerly Twitter)

@levelsio (@levelsio)

작성자는 OpenClaw 관련 스레드에서 소셜 엔지니어링 해킹이 자신이 그룹 채팅에 허용한 것이 주 원인이라고 인정했습니다. 그 경험을 바탕으로 OpenClaw보다 더 단순한 대안을 만들고 싶었다고 밝히며, 도구의 보안 취약성과 안전한 운영에 대한 경고를 제공합니다.

https://x.com/levelsio/status/2023996857760854197

#openclaw #security #socialengineering #chatops

@levelsio (@levelsio) on X

P.S. the social engineering hack on OpenClaw here is mostly my fault for letting it in my group chat But I still wanted something simpler than OpenClaw which this is

X (formerly Twitter)

@levelsio (@levelsio)

작성자는 Telegram을 통해 자신이 운영하는 사이트들과 직접 채팅하면서 기능을 만들고 버그를 고칠 수 있게 되었다고 밝혔습니다. 이 작업에는 OpenClaw를 3주간 사용해 보았고 기능은 훌륭하지만 실제 프로덕션 서버에 바로 배포하기에는 보안상 우려가 있었음을 언급합니다. 실무용 채팅 기반 개발·운영 사례입니다.

https://x.com/levelsio/status/2023960543959101938

#openclaw #telegram #chatops #webdev

@levelsio (@levelsio) on X

✨ A dream I had finally came true: I can now chat directly with my sites to build any feature or fix any bug just via Telegram I've been playing with OpenClaw for 3 weeks now and it's great but I was always too scared to run it on any production server And I was right a bit as

X (formerly Twitter)
I really don't like #telegram but it seems to be the only viable way to implement personal #chatops

There's no other popular messaging service has an easy way to implement bots it seems. discord is just much too much. matrix is more complicated to get into than xmpp ever was. signal refuses to ever implement bots...
Krang is watching. Telegram alerts when disk space dips, PostgreSQL hiccups, or I even think about sleeping.
This bot has become my second brain.
#InfraMonitoring #KrangOpsBot #ChatOps
I know #chatops is a bit dated by todays standards of freshness but I really am sick of reading a Jenkins message or alertmanager message and then having to login to an interface and do a bunch of routine stuff. I think #robusta is probably the most recent thing I’ve looked at (a few years ago). Anyone have suggestions #devops #slack #jenkins
.@peculiaire: have the arc of the story prepared; to-the-second details can be filled in later. #chatops tools are useful. #srecon16europe
Bluesky

Bluesky Social

After years of using #IRC and #Jabber for #chatops at $WORK, I'm now using Slack. Here's my hot-take:

Slack is a massive backslide in not only portability/compatibility, but efficiency. Holy ADHD batman, I've never lost conversations in IRC/Jabber. Like, I have no fucking clue where they are.. they're gone.. no.. they're just arbitrarily hard to access because, and again, hot-take, fuck threads.

Not just one, but two talks at #OSMC for @chronosphereio engineer Patrick Stephens! This talk was about using @fluentbit as the engine to power #ChatOps. https://youtu.be/KCnpx77_6IA?feature=shared&t=9
OSMC 2024 | Fluent Bit, the engine to power Chat Ops by Patrick Stephens

YouTube