<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/srvx/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/srvx/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/srvx/feature-requests/</id><updated>2016-09-28T02:08:45.784000Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>#309 Use SHA256 or SHA1 for Auth</title><link href="https://sourceforge.net/p/srvx/feature-requests/309/?limit=25#91c1" rel="alternate"/><published>2016-09-28T02:08:45.784000Z</published><updated>2016-09-28T02:08:45.784000Z</updated><author><name>Entrope</name><uri>https://sourceforge.net/u/entrope/</uri></author><id>https://sourceforge.net2501bba6476329de1137244c175892cb0dd0483f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed-accepted&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;assigned_to&lt;/strong&gt;: Entrope&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Group&lt;/strong&gt;: 1.3.x --&amp;gt; 1.4.x&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</summary></entry><entry><title>#309 Use SHA256 or SHA1 for Auth</title><link href="https://sourceforge.net/p/srvx/feature-requests/309/?limit=25#9965" rel="alternate"/><published>2016-09-28T02:08:28.826000Z</published><updated>2016-09-28T02:08:28.826000Z</updated><author><name>Entrope</name><uri>https://sourceforge.net/u/entrope/</uri></author><id>https://sourceforge.netc2a6a1b34b7aa69a99006926fbcd346112fd981d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Implemented in commit fb1dbb2fbd2e96f19098b8aa09331fff67546c65.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Use SHA256 or SHA1 for Auth</title><link href="https://sourceforge.net/p/srvx/feature-requests/309/" rel="alternate"/><published>2016-09-26T23:26:15.334000Z</published><updated>2016-09-26T23:26:15.334000Z</updated><author><name>Eric Hocking</name><uri>https://sourceforge.net/u/trainhappy/</uri></author><id>https://sourceforge.net1a7205524b96840a53093ae1dbd18a812a9bcb9e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Use SHA256 or SHA1 for NickServe over the current md5 method.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Use SHA256 or SHA1 for Auth</title><link href="https://sourceforge.net/p/srvx/feature-requests/309/" rel="alternate"/><published>2016-09-26T23:26:15.334000Z</published><updated>2016-09-26T23:26:15.334000Z</updated><author><name>Eric Hocking</name><uri>https://sourceforge.net/u/trainhappy/</uri></author><id>https://sourceforge.netac2f316523189078f8557ae31a67680d613b2aef</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket 309 has been modified: Use SHA256 or SHA1 for Auth&lt;br/&gt;
Edited By: Entrope (entrope)&lt;br/&gt;
Status updated: u'open' =&amp;gt; u'closed-accepted'&lt;br/&gt;
_milestone updated: u'1.3.x' =&amp;gt; u'1.4.x'&lt;br/&gt;
Owner updated: None =&amp;gt; u'entrope'&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>New Channel Mode: Strip Color</title><link href="https://sourceforge.net/p/srvx/feature-requests/308/" rel="alternate"/><published>2015-02-14T13:26:43.690000Z</published><updated>2015-02-14T13:26:43.690000Z</updated><author><name>Fironet</name><uri>https://sourceforge.net/u/fironet/</uri></author><id>https://sourceforge.net969cb6bb79263c7ff32aad2e2513221624c3f9e4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;On several networks including Freenode the Channel mode +c strips color from messages rather than blocking them completely. On other networks &lt;a class="" href="https://wiki.mozilla.org/IRC#Channel_Modes" rel="nofollow"&gt;like Moznet&lt;/a&gt; there's a separate mode to strip color, +S.&lt;/p&gt;
&lt;p&gt;In many cases using +c as implemented by SRVX on networks like GameSurge is too restrictive for users on a channel who have formatting commands and scripts, or simply want their message to be seen and not outright blocked. Adding a new mode that simply strips the color from messages would be immensely useful.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>New command suggestion: !mdeluser</title><link href="https://sourceforge.net/p/srvx/feature-requests/307/" rel="alternate"/><published>2012-05-21T17:19:56Z</published><updated>2012-05-21T17:19:56Z</updated><author><name>Bladerunner</name><uri>https://sourceforge.net/u/b1aderunner/</uri></author><id>https://sourceforge.netb11bc9151e19bd424b8be3e21b294708d65aa641</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The !mdelop, !mdelmaster commands were very useful years ago, and sometimes if your users have the basic access levels (200, 300, etc) still can be. However, it is becoming common in channels to have various access levels in between, and now that addban is available at 250 and events at 350, those have become useful and more common access levels to organize users in your list. Commands such as !mdelmaster don't work on a master who has access 350, thus you have to do it the other way.&lt;/p&gt;
&lt;p&gt;Proposal 1:&lt;br /&gt;
!mdeluser [pattern] deletes any user with any access level matching given pattern, with the optional paramater of:&lt;br /&gt;
!mdeluser [100-150] [pattern] which allows you to provide a single access level or range of access levels.&lt;/p&gt;
&lt;p&gt;Proposal 2:&lt;br /&gt;
The old !mdelmaster/!mdelop, etc commands would not require only 300, or 200 access, but instead require you to have access anywhere between 300-399 for !mdelmaster, 200-299 for !mdelop, etc.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>timestamp of user count record in !info</title><link href="https://sourceforge.net/p/srvx/feature-requests/306/" rel="alternate"/><published>2010-07-17T10:53:19Z</published><updated>2010-07-17T10:53:19Z</updated><author><name>ZeRoFiGhter</name><uri>https://sourceforge.net/u/zerofighte/</uri></author><id>https://sourceforge.net62ac708ed66998dbff01adf010ac6ab4eacf090b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;hi&lt;/p&gt;
&lt;p&gt;some of our users said it would be nice to have the timestamp when the "record visitors" have been in the chan displayed also.&lt;/p&gt;
&lt;p&gt;maybe this is a feature you wanna implement.&lt;/p&gt;
&lt;p&gt;regards&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>+N channel mode</title><link href="https://sourceforge.net/p/srvx/feature-requests/305/" rel="alternate"/><published>2010-04-19T13:03:05Z</published><updated>2010-04-19T13:03:05Z</updated><author><name>Lucario</name><uri>https://sourceforge.net/u/lucario/</uri></author><id>https://sourceforge.netfd4af44d60686dabd1bdd5241336829608cb7aea</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;A +N channel mode which stops channel-wide notices from being sent would be useful. Together with the existing mode +C which stops CTCPs, these two channel modes would prevent alot of channel abuse/harassment. Currently the best way to deal with notices is to use SpamServ's noticescan to kick or ban the user who sends a channel-wide notice but preventing the user from sending a notice in the first place would be even better/more effective as other users won't even hear the beep sounds associated with notices by default for those using IRC. &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Improving Dynlimit setting</title><link href="https://sourceforge.net/p/srvx/feature-requests/304/" rel="alternate"/><published>2010-04-19T12:30:02Z</published><updated>2010-04-19T12:30:02Z</updated><author><name>Lucario</name><uri>https://sourceforge.net/u/lucario/</uri></author><id>https://sourceforge.net95c7f173624a98f9b5997c093434fc9fa473aaa4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Currently the dynlimit setting only allows coowners+ by default to toggle it on and off. To improve this feature, users could be allowed to control more aspects of it. On GameSurge, the floating limit is the no. of current users +15. Users should be allowed to set their own margin for the floating limit for greater flexibility e.g. current no. of users +5 to +10 or +2 to +20 etc. They should also be allowed to control the time period before ChanServ resets the chhannel limit.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>NoAddToChan and NoGiveOwnership</title><link href="https://sourceforge.net/p/srvx/feature-requests/303/" rel="alternate"/><published>2010-04-19T12:00:53Z</published><updated>2010-04-19T12:00:53Z</updated><author><name>Lucario</name><uri>https://sourceforge.net/u/lucario/</uri></author><id>https://sourceforge.net89427903ad20812530f26923ad9a3052a3e81adc</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This AuthServ setting could be called "NoAddToChan" or "NoAddUser". Some other IRC networks already have this command. When turned on, nobody can add you to a userlist. This prevents people from adding you to a channel's userlist without your permission. Network helpers or ircops could override the setting using security override in scenarios which they need to add users. "NoGiveOwnership" would prevent people from giving ownership of a channel to you without your knowledge/permission. Sometimes this could happen and you would only find out about it when you check your access list. The current way to prevent unwanted channel ownership is to DNR your own AuthServ account (or own 10+ channels so that the FORCE parameter must be used) but since the DNR feature is only available to GameSurge staff,  an account setting/flag would be useful for normal users.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>