I'm heavily reducing the bloat in picoclaw by removing all the bullcrap. Currently looking at channels.
If you could have only 1 channel type to communicate with your bot over, which one would you want to use? And why?
dingtalk0.0%
discord0.0%
line0.0%
nostr0.0%
signal57.1%
slack28.6%
telegram0.0%
wechat0.0%
whatsapp0.0%
[other]14.3%
7 votes \ 1 day left
If #1 is not available, then
kek
I mean... that's what all dem bots seem to be using SN for. Milk sats while fine-tuning
SoldMySOUL.mdI wouldn't mind some fun bots around here to interact with as long as they're not pretending to be humans
bleep blophow about humans pretending to be bots?I'd prefer Signal because I don't want to have to self-sensor or worry about another avenue to leak secrets, but Slack has the best interface imo; one slack workspace for a bot workspace, one channel per session. @janetyellen got most of us in the Lab using it.
You mentioned slack frontend everything the other day. Which is cool.
I'd probably want signal too (its the thing it doesn't have!!!) But I wouldn't use it haha. I would maybe use simplex or nostr as a fallback. But it doesn't have that either. Right now I have a channel over ntfy haha
I'm already removing some stuff not listed here in favor of just having the bot run a websocket channel, which is all I personally need, and then just a thin apk on top and a custom buffer history command. Like bash history 😂.
Whatever has the least context switching. The more native it feels inside my workflow, the more I’ll actually use it.