4 ms·
I'm sorry to hear that. Here is a page about us and who is behind it: https://www.ircrelay.com/about https://www.ircrelay.com/about A high level overview of ho
by mitchellh 14y ago
I'm sorry to hear that. Here is a page about us and who is behind it: https://www.ircrelay.com/about https://www.ircrelay.com/about
A high level overview of how it works: When you sign up, we provision a private ZNC installation on EC2 for you. It is multi-tenant, but we leverage various mechanisms for security: passwords are one-way hashed, each ZNC process runs as a separate unix user for each IRCRelay user, file permissions are such that no other ZNC user can read another users config even if there was an exploit, etc.
As for the payment: We only wanted to sign up people who were serious about using the service, and asking for payment details up front is a way to do this. All payments are done through stripe, and we don't see the CC details, ever. Your card is not charged until after the 30 day trial, and we send a warning email a few days prior so you can cancel your account if you're not happy.
But thanks for checking it out!
- nuclear_eclipse 14y agoSince you are using a separate ZNC instance for each user, what are prospects of allowing users to install (or choose from a pre-selected list of) third-party ZNC extensions? In my case, I wrote a service-agnostic push notification module for ZNC [1] that I think would be a decent additional feature for you to compete with services like IRCCloud or TapChat. 1: https://github.com/jreese/znc-push https://github.com/jreese/znc-push
- pavel_lishin 14y agoMaybe I'm wrong, but it seems to me that people who are even aware of what ZNC is would be able to run their own instance on a server under their control.
- zwily 14y agoHow do you handle the fact that most IRC networks limit the # of connections that can come from a single IP address?