Privacy Policy updated (20AUG2015)

by DareNET on Thu, Aug 20 2015 17:00:00

We've updated our privacy policy so it's more explicit about how we actually use and store your personal information.

The reason behind this long overdue update was a paragraph (shown below) in the old privacy policy.

2. Business Transfers: In some cases, we may choose to buy or sell assets. In these types of transactions, user information (in an aggregated form) is typically one of the business assets that is transferred. Moreover, if DareNET, or substantially all of its assets, were acquired, user information would be one of the assets that is transferred.

This paragraph simply meant that should we have elected to sell or buy any assets, user information (in aggregate form) may have been involved in such transactions. It also goes on to state that should we have transferred ownership of the network to another individual or entity, user information such as email addresses, usernames and passwords (in their hashed form) would have been part of such an arrangement.

We removed this paragraph because DareNET has never taken part in such transactions, nor will do so. You can rest assured that DareNET has not, nor will we, share or sell your personal information with any third party.

Services Update (1.7.0)

by DareNET on Sun, Jul 26 2015 10:05:00

Evo 1.7.0 is now live on the network. We fixed so many bugs the Orkin Man started calling US, including one where temporary change levels would expire prematurely in some circumstances.

Channel staff can now also track who is responsible for userlist additions and changes.

If you notice anything out of the ordinay, feel free to stop by #help and let us know.

Services Update (1.6.0)

by DareNET on Thu, May 28 2015 22:03:00

Thanks for using DareNET! We're always making improvements and fixes to Evo (our services), and strive to bring you updates every few weeks. This update:

  • UGH IT'S SUMMER AND MOSQUITOS BLOW (so we killed some bugs in protest).
  • Did too many shots last night and texted Tina. Again. SMH.

If you notice anything out of the ordinay, feel free to stop by #help and let us know.

Introducing W

by culex on Wed, Apr 01 2015 06:26:00
Happy April Fool's Day 2015!

Our development team's valiant development efforts present to you: W!

Now, you may be wondering "Why change services? Didn't you just say you were working on a new fork from srvx?" and the answer is... sort of long.

Developing New Services

As mentioned in a few blog posts, which are over a year old by now, we had been working on a srvx fork. Now, that's all fine and dandy, but somewhere down the road, we realized that the codebase is just unmaintainable. we have no modularity, "modules" follow a strange approach in the sense that they are only compile time options. Furthermore, srvx comes with many historical decisions that simply make no sense today: Why does O have a default level of 100 for cmode +o override, but 300 for cmode +v override? Why do we still have no NoSQL support for going full web-scale?

It all began with a little comment from me, culex: "Can't we change uset to something less idiotic?" After multiple rounds of talking to the higher-ups, I managed to get permission to rewrite services from scratch to make them more consistent, user-friendly and maintainable.

If you remember how painful it was to find commands amongst the entire selection of services then you know how I felt: Spending minutes digging in the help files, then going source digging, only to be told that srvx uses non-standard terminology or separates C uset from N set where it makes the least sense. Thus I took it upon myself to write verbose help files to aid newcomers.

In case you didn't notice, near the end of May 2014, we switched our IRCd to ircd-darenet2. This was necessary to make W work reliably, as it uses fairly complex server-to-server communication mechanisms to save bandwidth that required shifting a lot of code around and introduced incompatible changes that simply couldn't be emulated.

Unfortunately, this has the side-effect that support for multiple languages has been lost, but we are actively working on it. Translators are welcome to contact me on IRC.

About W

W is state-of-the-art software, the likes of which haven't been seen in a long time. Highly configurable flood protection, wildcard-based access list searching, verbose logging of oper overrides, a NoSQL database customized for speed, a modern web panel to control your channel from, blazingly fast lookups and properly packed structs, efficient commands, useful help files, scrypt password hashing, sane default behavior and familiar 500-level design will make your experience on DareNET faster, safer and easier than ever before. For reasons of simplicity, for example, we have abandoned the old and dusty account system in favor of a channel-based account system, which also gives more safety in allowing you to lock down every account with a separate password.

Unfortunately, cue bad timing, the services databases have been deleted due to hardware failure, right as we were writing a database converter. That means that all channel and user data has been completely lost. Users wishing to re-register channel must have ops to use /msg W REGISTER #channel. Please take your time to study the help files, usage should feel familiar to most users who have been active on IRC since around 1997 or so. Should you have any questions, please do not hesitate to contact #help. A web panel can be found at

Please keep in mind that, while W has been extensively tested by our staff before deployment, there is always a chance of bugs and unforeseen issues; do not hesitate to contact us if you are unsure whether certain behavior is to be interpreted as a bug or a feature.


Upcoming Privacy Changes

by DareNET on Fri, Oct 31 2014 04:39:00

Our current network setup allows other users to see your IP address when you join channels. While this is standard practice for IRC, we feel it doesn't fully reflect our commitment to privacy. We believe it's important such information be hidden, and that's why we'll soon be enabling host hiding for all users.

Keep on on eye on this space for updates.

UPDATE: this feature is now live on the network.

In the meantime, we'll answer some of the most frequently asked questions.

What will the hidden host look like?

For non-authenticated users, the hidden host will be in the form of <uniqueid>.guest.darenet.

For example:

Joins: JohnDoe (ident@84c76229-50628879-a0c02cc1-05a4b2eb.guest.darenet)

Authenticated users will continue to receive their custom group host or title.

Will I need to apply umode +x to take advantage of the new feature?

No, the "guest hidden host" will automatically be applied when you connect to the network.

I have a custom title on my account, will I still be able to use it?

Yes! Authenticated users will continue to receive their custom group hosts and titles.

What if I don't like the new feature? Will I be able to disable it?

Yes, but you will need to disable autohide for your account and use login-on-connect.