mike-bailey

Claude Opus and Gemini 2.5 speak to each other about the timing and similarity between Gemini CLI and Claude Code.

Claude Opus demonstrates advanced ability in spoken dialogue, assertiveness and respectful conversation.

I added a two way voice interface to Gemini CLI.

https://youtu.be/HC6BGxjCVnM?feature=shared&t=36

It's a FOSS MCP server I created a couple of weeks ago:

- https://getvoicemode.com

- https://github.com/mbailey/voicemode

# Installation (~/.gemini/settings.json)

{

  "theme": "Dracula",  

  "selectedAuthType": "oauth-personal",  

  "mcpServers": {  

    "voice-mode": {  

      "command": "uvx",  

      "args": [  

        "voice-mode"  

      ]  

    }  

  }  

}

openai-proxy connects the many open source models (ASR, TTS, LLMs) with OpenAI compatible APIs with existing tools that use OpenAI SDKs.

By pointing `OPENAI_BASE_URL` at your haproxy load balancer service running this config you can selectively migrate API requests from OpenAI to other services (including self-hosted open source models).

Last time BMA was on front page of HN was 1 Jan 2020 (for about 23 hours IIRC).

https://news.ycombinator.com/item?id=21921293

The __bma_read_filters function is designed to take all arguments and join them with | to create a grep pattern. Adding quotes around $@ would break this functionality because:

__bma_read_filters "arg1 arg2" arg3

With unquoted $@:

• Gets word split into: arg1 arg2 arg3 • Results in: arg1|arg2|arg3

With quoted "$@":

• Would be passed as: "arg1 arg2" arg3 • Results in: "arg1 arg2"|arg3

The unquoted version is correct here since the function is intentionally using word splitting to create individual grep pattern elements.

This is one of those cases where the normal "always quote your variables" rule has a valid exception because word splitting is part of the intended behavior.

Here's the video from my talk on Bash-my-AWS at LinuxConf 2020 in the Gold Coast Australia.

https://www.youtube.com/watch?v=UbH_cg7Ev1Q

It's probably my fault if you haven't heard of Bash-My-AWS.

Bash-My-AWS is a simple but extremely powerful set of CLI commands for managing resources on Amazon Web Services. They harness the power of Amazon's AWSCLI, while abstracting away the verbosity. The project implements some innovative patterns but (arguably) remains simple, beautiful, readable and easily extensible.

The project started in 2014 and while many hundreds of hours have gone into it, far less has gone into promotion.

I'm speaking about it at LinuxConf and have created a documentation site at https://bash-my-aws.org

https://linux.conf.au/schedule/presentation/144/