jhthorsen
jhthorsen on Hacker News
We actually just changed to convos.chat :)
It comes from "conversation by" iirc.
Can you explain? I don't understand "hacks the back button" :/
Thank you! It's all because of Mojolicious real time web framework. The fun of using the well designed components, and not to mention the ease of writing tests makes it a no-brainer to me :)
It's fun running cloc from time to time: Very evenly between Perl, JavaScript, CSS and template files: https://convos.by/doc/#statistics
I don't think the IRC server admins would be very happy if I started b64 encode live audio and video streams over their irc daemons ;)
STUN/TURN is not a requirement, but most users will have issues if you don't add those services to the mix.
CTCP messages are widely implemented, and there are no standardised or restrictions to how to format them. Since there are no good way to pass WebRTC signalling through IRC, I made up my own protocol. If a more standard way is available in the future, then Convos will for sure adopt it.
Posted by
jhthorsen on Saturday May 23, 2020 @04:00AM
from the convos.by dept.
The server part of Convos is like an IRC bouncer, but instead of supporting the IRC protocol from the client side, it has a HTTP/WebSocket interface that talks to the Convos frontend.
So Convos keeps your connection, so even if you close the web browser, you will still receive messages and you can see the history once you open your browser again.
If you stop the Convos server, then you will also be disconnected from the IRC server.
We decided to use Perl, because of the real-time web framework Mojolicious -
https://mojolicious.org/. It makes developing web apps a breeze.
I would very much like this as well, but "kiosk" mode is currently not planned. Might start consider it again after
https://github.com/Nordaaker/convos/issues/414 is closed... Please do open an issue where you describe what you think is required for Convos to work from within your email inbox, or join #convos on freenode and have a chat with us.
I don't understand what you mean about "web page should specify which IRC server to use". I'm also confused about notion about "request headers".
I highly doubt Convos will ever support chatting without JavaScript and CSS enabled.
Got any killer features that we should add to Convos?
Convos has auto complete for commands and nicks, and the auto reconnect should work, though I think it's hard making good tests for it.