devzat

Similar to DevZat: https://github.com/quackduck/devzat

If going that route perhaps code could be borrowed from Devzat [1] not my repo It is ssh chat and has word filters. [1] - https://github.com/quackduck/devzat

Cool, the source code is amazingly readable. Also love the sense of humor :-D such as https://github.com/quackduck/devzat/blob/main/commands.go#L1...

Corporate Slack instances are probably not a great place to discuss such things. One could in a pinch fire up one of the ssh chat daemons [1] on an EC2 assuming that most of the employees are familiar with using SSH. There is a demo documented in that git repo. People can ssh under a pseudonym rather than using a real name. The daemon uses private keys to track identity so make a new SSH key specific to that server. Not my repo but the maintainer is here on HN. # append to ~/.ssh/config # ssh-keygen -q -t rsa -b 2048 -N "" -C "chat" -f ~/.ssh/ssh-chat Host chat Hostname some-ec2-ip Port 22 User some-username IdentityFile ~/.ssh/ssh-chat # Go's ssh lib is old HostkeyAlgorithms +ssh-rsa PubkeyAcceptedKeyTypes +ssh-rsa Another quick, lightweight and simple option is uM

I've tried to make this argument in the past and gained no traction. What I did instead was to create self hosted chat things as a fallback for the times when Discord or Slack have a green status page but their applications fail to operate. Even light-weight daemons like uMurmur [1] or devzat [2] ssh-chat can be handy in a time of need if a quorum know to fall back to it, especially how simple they are to deploy. Self hosted tools are also handy when one wants to share links or text that should not be on 3rd party sites forever and for eternity. Such things may also be handy if some day the internet censorium gets a little bit out of hand. [1] - https://github.com/umurmur/umurmur/wiki/Configuration [2] - https://github.com/quackduck/devzat

did not know it was possible to use such ports as not-root. anyway here is a direct link to how you can host your own devzat server: https://github.com/quackduck/devzat#want-to-host-your-own-in... good luck, OP!

- One method could be a Linux laptop and using SSH to talk over devzat [1] They should generate a site-specific ssh key to talk to your devzat instance. The developer is here on HN. Configure devzat to listen on port 443. To do this as a non-root account use "setcap cap_net_bind_service=+ep /path/to/devzat". They have a live instance both of you could try out. Using SSH takes most of the risk of compromised state-run certificate authorities out of the picture. - If the goal is to have voice chat then install uMurmur [2] on your router or a VM or any node that is publicly reachable. They should use Mumble on a Linux laptop but if they had to use a cell phone then there is the Mumla app to talk to your uMurmur instance. uMurmur takes a couple minutes to set up. Self-hosted uMurmur reduces the risk of utilizing platforms that have a

The go ssh packages are a popular choice: https://github.com/shazow/ssh-chat https://github.com/zachlatta/sshtron https://github.com/quackduck/devzat https://github.com/donuts-are-good/shhhbb/ There's also a assembly library: https://2ton.com.au/sshtalk/ And for rust there's trush, and for python paramiko as mentioned. > expose a TUI/cli-app over ssh without actually caring about securing OpenSSH If you already have an app, see maybe: https://drewdevault.com/2019/09/02/Interactive-SSH-programs....

> That sounds like a great feature/configuration option. Maybe even allow a admin-defined backlog size for people that want persistent instances. Done! https://github.com/quackduck/devzat/commit/00160b83751d90176... > SSH based chat is not super popular which really surprises me. I could see devzat being an amazing fall-back for a private chat inside a company when Slack or Discord are having a moment or for those times when people want to say something that isn't recorded forever and especially not visible to their management. I think it would also be amazing for people in oppressive regimes that block access to all the mainstream chat platforms but allow SSH to specific VPS providers. :))))) I'm glad you like devzat. I'd love to talk to you on the main chat!

I rarely use IRC any more and I used to run some small IRC servers. Most moved to Discord but I refuse to use such platforms for their abuse of retaining both text and voice transcription chat history forever. Discord voice transcription can run silently in any public or private channel and nobody can prove otherwise. This was not impossible on IRC but far less likely. Public channels were recorded with publicly visible bots that had permission to be in the channel. Some IRCD's had modules that would allow a NetAdmin to monitor private chats but that can be mitigated with clients that support OTR. Nowadays if I need to spin up a chat with people I know I just give them a shell function that utilizes a self-hosted instance of devzat. # uncensored chat using self hosted https://github.com/quackduck/devzat.git # add to .bashrc o

Can people in Iran SSH out to other countries? If so the folks familiar with SSH could use something like sshchat or devzat [1] see demo info, not my project This does not persist chat, but that may be a net positive in a surveillance state. ssh-keygen -q -t rsa -b 2048 -N "" -C "devzat" -f ~/.ssh/.id_devzat ssh -i ~/.ssh/.id_devzat some-name@devzat.hackclub.com If DNS is blocked then edit ~/.ssh/config and append: Host devzat devzat.hackclub.com Hostname 150.136.142.44 Port 22 # Port 443 User some_name IdentityFile ~/.ssh/.id_devzat LogLevel VERBOSE [1] - https://github.com/quackduck/devzat