edmund-huber / ergonomadic Goto Github PK

Should support at least one of them.

After #34 is done we can automatically acquire certs via ACME LetsEncrypt

Can probably use this acme library.

Can we just build native support for TLS/SSL already?

See also #8

What is websocket.go really doing here? Nothing by the looks!

What is it meant to be doing? I've not seen of or really heard of any IRC servers that build in websocket support (really). This really should IHMO belong to the domain of clients, bouncers and fancy web frontends?

@edmund-huber I noticed you closed and did not merge all of my PRs.

If your intention is to close/discontinue this project I want to rebrand it based on your codebase.

Do you wish for you to retain your name in the LICENSE as the previous author/maintainer of the original codebase or are you happy to let me diverge the codebase entirely?

etc. should include NewNickName as well. These should check that the Name conforms to the character limitations of the type

We ought to figure something out about federation so that we can have some resilience to network and host issues.

• investigate existing IRC federation protocols
• figure out something better?

Setting a password in the config file doesn't actually seem to enforce authentication to the server at all via the PASS <password> command. It happily lets a client connect without supplying a password :/

Would you be interested in opening up some of the internal API you use?

In particular I would like to have access to some of the channels.

My use case: I'm trying to build a proxy between Hipchat and IRC. I just hate the Hipchat client and really like WeeChat 😄, so I want to have a proxy in between.
It might grow into something more generic like an XMPP - IRC proxy.

But with the current implementation I'm unable to use this project. But I'm reluctant to build the whole IRC server part myself.

I can understand if you are not willing to do it, as this project is meant for end-users and maintaining an API is something different.

Wanted to know if you have some plan to support WebSocket?
I am looking for a good solution for my chat system but I must keep IRC protocol.

After few looks at your code...I start to think the workload would not be major, if you confirm I can maybe try to work on that.

Would you be willing to accept a PR for a Dockerfile so we can publish automated builds of this thing? I'd like to try out your ergonomadic

In another issue (don't recall which one) you mentioned that you run a small IRC network with ergonomadic -- How do you do this? Is there support for server linking and some kind of server <-> server protocol builtin that I'm not seeing?

Just had an issue where stunnel was running, and listening on a port, but not actually forwarding connections to the backend.

so maybe stud or haproxy is a better idea

maybe also expose http://golang.org/pkg/runtime/#Stack for per-goroutine observations

Issuing a /topic command in mIRC 7.43 causes my client to disconnect and then reconnect to the connected server after 10-20s. Not sure if my client is receiving any messages from the server inbetween the /topic and the disconnect

How does the server perform (CPU, memory) with many (thousands) of chatty clients?