<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://www.23hq.com/resources/um/rsstohtml.xsl"?>
<rss version="2.0" xmlns:media="http://search.yahoo.com/mrss" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:fh="http://purl.org/syndication/history/1.0">
    <channel>
        <title>Messages in controlling spam</title>
        <link>https://www.23hq.com/photogroup/suggestions/</link>
        <description>How to make 23 better? Post and discuss ideas here.</description>
        <author></author>
        <language>en-us</language>
        <generator>23people</generator>
        <atom:icon>http://www.23hq.com/resources/um-style/logo-20.gif</atom:icon>
        <docs>http://blogs.law.harvard.edu/tech/rss</docs>
        <source>https://www.23hq.com/rss/photogroup/suggestions/conversation/6785752</source>
        <link rel="self" href="https://www.23hq.com/rss/photogroup/suggestions/conversation/6785752"/>
        <fh:incremental>false</fh:incremental>
        <item>
            <title>Message from Th Clvr Mnky</title>
            <link>https://www.23hq.com/photogroup/suggestions/conversation/6785752</link>
            <description>&lt;b&gt; controlling spam &lt;/b&gt;&lt;br&gt;One problem is that spammers don't necessarily care that their URLs are formed correctly, do they? It ends up being a war of attrition, and spammers will just change their tactics to sell you shoes or hats or drugs.&lt;/p&gt;
&lt;p style="margin-bottom: 0px;"&gt;They attack forums and comments to hack SEO results, I think, so whether or not the URL is good or not doesn't really matter to them. I think we'd see tactics change to get around the URL regexp so that they would still get comments published. Even a busted text link will still attract some sort of search engine result (they hope.)</description>
            <guid>https://www.23hq.com/photogroup/suggestions/conversation/6785752</guid>
            <pubDate>Wed, 01 Jun 2011 15:00:17 GMT</pubDate>
            <enclosure url="" type="" length=""/>
        </item>
        <item>
            <title>Message from Perkin-warbeck</title>
            <link>https://www.23hq.com/photogroup/suggestions/conversation/6785752</link>
            <description>&lt;b&gt; controlling spam &lt;/b&gt;&lt;br&gt;I have no personal experience with such sites, but a Google search shows that it is a common practice.  I also like Iko Tikashi's recent suggestion (in another discussion).  This is the wikipedia approach -- allowing plus members to tag comments as spam (the policy of what to do with those tags is to be determined).</description>
            <guid>https://www.23hq.com/photogroup/suggestions/conversation/6785752</guid>
            <pubDate>Tue, 31 May 2011 18:43:42 GMT</pubDate>
            <enclosure url="" type="" length=""/>
        </item>
        <item>
            <title>Message from Steffen Fagerström Christensen</title>
            <link>https://www.23hq.com/photogroup/suggestions/conversation/6785752</link>
            <description>&lt;b&gt; controlling spam &lt;/b&gt;&lt;br&gt;I should probably add to this, but find myself agreeing 100% with clvrmnky: Our bind is exactly that we want to keeps stuff open for commenting, and on the backend we try to block and ban as many IP addresses as possibly from spamming our servers.&lt;/p&gt;
&lt;p style="margin-bottom: 0px;"&gt;Are there other examples of people doing the no-external-links thing well?</description>
            <guid>https://www.23hq.com/photogroup/suggestions/conversation/6785752</guid>
            <pubDate>Tue, 31 May 2011 14:36:57 GMT</pubDate>
            <enclosure url="" type="" length=""/>
        </item>
        <item>
            <title>Message from Perkin-warbeck</title>
            <link>https://www.23hq.com/photogroup/suggestions/conversation/6785752</link>
            <description>&lt;b&gt; controlling spam &lt;/b&gt;&lt;br&gt;We already have the option to block comments from non-members.   Why  not also have the option to block comments from members who link to external web sites?  It's just an option, and not everybody would use it.  I would.</description>
            <guid>https://www.23hq.com/photogroup/suggestions/conversation/6785752</guid>
            <pubDate>Tue, 31 May 2011 14:06:59 GMT</pubDate>
            <enclosure url="" type="" length=""/>
        </item>
        <item>
            <title>Message from Th Clvr Mnky</title>
            <link>https://www.23hq.com/photogroup/suggestions/conversation/6785752</link>
            <description>&lt;b&gt; controlling spam &lt;/b&gt;&lt;br&gt;This was discussed a long time ago in another thread.&lt;/p&gt;
&lt;p&gt;The overarching paradigm of 23 is "sharing", and there is a desire by many to keep 23 open to all, including non-members.  I appreciate this, because no one is going to sign up for yet another service just to see and comment on my pictures. Sharing links is an important part of that for many (though not so much for me, though I also do not have a large problem with spam comments.)&lt;/p&gt;
&lt;p&gt;Basically, there is no perfect solution for combating spam. It will always be a trade-off between convenience and correctness.&lt;/p&gt;
&lt;p style="margin-bottom: 0px;"&gt;We've seen a big improvement since 23 installed the anti-spam service a few years back.</description>
            <guid>https://www.23hq.com/photogroup/suggestions/conversation/6785752</guid>
            <pubDate>Tue, 31 May 2011 13:05:51 GMT</pubDate>
            <enclosure url="" type="" length=""/>
        </item>
        <item>
            <title>Message from Perkin-warbeck</title>
            <link>https://www.23hq.com/photogroup/suggestions/conversation/6785752</link>
            <description>&lt;b&gt;controlling spam&lt;/b&gt;&lt;br&gt;Here's an idea: Since most spammers want you to visit their site, 23hq could disallow  external links in comments.  Or, only allow "plus"  members to embed external links.</description>
            <guid>https://www.23hq.com/photogroup/suggestions/conversation/6785752</guid>
            <pubDate>Tue, 31 May 2011 03:56:24 GMT</pubDate>
            <enclosure url="" type="" length=""/>
        </item>
    </channel>
</rss>
