3 ms·

Show HN: Pipecat – Connect message queues with Unix pipes

• sjs382 11y ago
  That logo... yikes.
  • lps41 11y ago
    Yeah... Maybe change it to a cat crawling into a pipe? Depicted from the side?
  • dexwiz 11y ago
    Well it's...memorable?
    • morgenkaffee 11y ago
      Now that I look at it again it also seems offensive. Switched it to a more boring but more suitable logo. Thanks.
      • tokenizerrr 11y ago
        I didn't see anything wrong with the old logo. Too bad you felt the need to change it.
        • tekromancr 11y ago
          Yea, cats have/are prominent assholes. It's just how they are!
      • sjs382 11y ago
        I actually liked the original logo, despite my comment. The new one works very well, too.
• kenny_r 11y ago
  This looks really cool. I went ahead and added it to the Arch User Repositories[0]. [0]: https://aur.archlinux.org/packages/pipecat-bin/ https://aur.archlinux.org/packages/pipecat-bin/
• nyan4 11y ago
  Why no 0mq? :)
  • morgenkaffee 11y ago
    I don't have any experience with zeromq as I mostly deal with AMQP protocols. But good that you mention it - if there is a demand I can dig into it. There are quite a few other message queue systems out there. I can also imagine that pipecat could work as a kind of migration systems between them. But this probably should be a separate tool as it requires shuffling around metadata as well.
• jbverschoor 11y ago
  Very cool!
• pdkl95 11y ago
  Ok, I know message queues[1] are not the most popular part of System V IPC, but was it really necessary to overload the name? (I mean ActiveMQ et al overloading "message queue" in general, not you pipecat project) [1] http://beej.us/guide/bgipc/output/html/singlepage/bgipc.html#mq http://beej.us/guide/bgipc/output/html/singlepage/bgipc.html...
• nikolay 11y ago
  Great job! I am definitely gonna use this daily!
• agborkowski86 11y ago
  hey guys can u provide usage scenario ?