OpenVoice VS pgmq

Given the inevitability of easy voice cloning[1], it seems irresponsible to be using voice as a positive authentication signal.

Unfortunately, major US financial institutions seem to be ramping up adoption of this technology[2].

Am I missing something?

[1] https://github.com/myshell-ai/OpenVoice

They might have been forced to give a signal after this rose on HN today:

https://research.myshell.ai/open-voice

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

And lots of interesting extensions use it, like

https://github.com/tembo-io/pgmq

https://github.com/zombodb/zombodb

https://github.com/supabase/pg_jsonschema

Have you considered https://github.com/tembo-io/pgmq for the queue bit?

some notes about pgmq, https://github.com/tembo-io/pgmq, that is on this list. It is built as an extension in Postgres, which makes it compatible with all languages that have a Postgres driver.

There's no 'magic' to it, it uses existing Postgres features so all the performance and consistency guarantees of Postgres are to be expected. Easily gets to 10k+ concurrent reads and writes even on smaller sized Postgres instances, which is more than most applications need.

Newer project but there's no library needed. https://github.com/tembo-io/pgmq. They have a pretty simple SQL api similar to SQS. It's an extension though, so some cloud provider will not support it.

PGMQ does not require a client library, https://github.com/tembo-io/pgmq so long as your language of choice can run SQL. All the functions live in Postgres, and you just call them with SQL statement. Very similar feel and semantics to SQS.