<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DailyStuff &#187; marketeers</title>
	<atom:link href="http://blog.dailystuff.nl/tag/marketeers/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dailystuff.nl</link>
	<description>toen Internet stil stond en weer doorging</description>
	<lastBuildDate>Sat, 04 Feb 2012 07:46:44 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<atom:link rel="search"
           href="http://blog.dailystuff.nl/opensearch"
           type="application/opensearchdescription+xml"
           title="Content Search" /><atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>		<item>
		<title>Marketeers en Tweets</title>
		<link>http://blog.dailystuff.nl/2009/12/marketeers-en-tweets/</link>
		<comments>http://blog.dailystuff.nl/2009/12/marketeers-en-tweets/#comments</comments>
		<pubDate>Tue, 22 Dec 2009 08:44:50 +0000</pubDate>
		<dc:creator>Hans</dc:creator>
				<category><![CDATA[Internet, Unix en security]]></category>
		<category><![CDATA[Bayesian]]></category>
		<category><![CDATA[e-mail]]></category>
		<category><![CDATA[marketeers]]></category>
		<category><![CDATA[SpamAssassin]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://blog.dailystuff.nl/?p=930</guid>
		<description><![CDATA[Het was te verwachten uiteraard, maar bij het bekijken waarom sommige spamberichten niet netjes naar de Junk-folder viel me iets grappigs op. Sommige partijen zijn begonnen om niet alleen hun responses te monitoren met Google Analytics, maar laten nu ook automagisch een Tweet aanmaken om zo hoger op sommige lijsten te scoren. Of het fair [...]]]></description>
			<content:encoded><![CDATA[<p>Het was te verwachten uiteraard, maar bij het bekijken waarom sommige spamberichten niet netjes naar de Junk-folder viel me iets grappigs op. Sommige partijen zijn begonnen om niet alleen hun responses te monitoren met Google Analytics, maar laten nu ook automagisch een Tweet aanmaken om zo hoger op sommige lijsten te scoren. Of het fair is laat ik even in het midden, maar het lijkt wel langzaam een trend te worden om Twitter-achtige dingen te gebruiken in marketing en de kans dat gebruikers dit naar elkaar doorsturen is vrij klein.<br />
<code><br />
describe  LOCAL_TWEET   Mailing with Tweet-API<br />
rawbody   __A_LOCAL_TWEET   /\bhttp:\/\/api\.tweetmeme\.com\/share\?url/i<br />
rawbody   __B_LOCAL_TWEET   /\bunsubscribe\b/i<br />
meta      LOCAL_TWEET   ( __A_LOCAL_TWEET &#038;&#038; __B_LOCAL_TWEET )<br />
score     LOCAL_TWEET   0.001<br />
</code><br />
Met de bovenstaande ruleset voor <a href="http://www.spamassassin.org/">SpamAssassin</a> is te controleren wat de impact gaat zijn. Een paar dagen loslaten op de honeypot die het <a href="http://blog.dailystuff.nl/2009/05/een-bayesian-filter-vullen-met-data/">bayesianfilter</a> van kenmerken voorziet zou voldoende moeten zijn om te kijken wat de score daadwerkelijk moet gaan zijn en of het effectief is.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.dailystuff.nl/2009/12/marketeers-en-tweets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Aggressive marketeers</title>
		<link>http://blog.dailystuff.nl/2009/05/aggressive-marketeers/</link>
		<comments>http://blog.dailystuff.nl/2009/05/aggressive-marketeers/#comments</comments>
		<pubDate>Sat, 30 May 2009 16:10:56 +0000</pubDate>
		<dc:creator>Hans</dc:creator>
				<category><![CDATA[Internet, Unix en security]]></category>
		<category><![CDATA[Maatschappij & leven]]></category>
		<category><![CDATA[2009]]></category>
		<category><![CDATA[marketeers]]></category>
		<category><![CDATA[phone]]></category>
		<category><![CDATA[spam]]></category>

		<guid isPermaLink="false">http://blog.dailystuff.nl/?p=793</guid>
		<description><![CDATA[The financial crisis or as we&#8217;re being told to believe, now also starts to make marketeers and sales more aggressive. In the Netherlands there are a lot of companies again who say they spoke to you about three months ago, made a deal and if we could confirm it. After requesting for something on paper [...]]]></description>
			<content:encoded><![CDATA[<p>The financial crisis or as we&#8217;re being told to believe, now also starts to make marketeers and sales more aggressive. In the Netherlands there are a lot of companies again who say they spoke to you about three months ago, made a deal and if we could confirm it. After requesting for something on paper the conversation normally ends quickly.</p>
<p>Now they have a new strategy and start calling that they spoke with you last year and that you would skip this year as well on god knows what, but they want to confirm this and start requesting your details. They then sent you a form with your details and the request to confirm it that everything is correct. But with the urge to do it quickly or else they need to remove you from there database.</p>
<p>It sounds like some companies are trying to work around the new law that becomes effective on July 1st 2009. This law limits marketeers what they may sent to businesses for there marketing campaigns as now also is for normal people. It also raises a question with me who is site scraping for contact details since they had the VoIP-number for voice, but now for fax or e-mail. And they refused to use the info@ mail address as a nice detail to this all. Again July 1st 2009 becomes interesting for spammers, marketeers and sales.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.dailystuff.nl/2009/05/aggressive-marketeers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

