<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Web Prescience, Coming True Every Day</title>
	<link>http://www.johnon.com/663/futures-research.html</link>
	<description>I think there's an opinion on that subject lying around here somewhere....</description>
	<pubDate>Sat, 31 Jul 2010 11:46:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: Jeremy Luebke</title>
		<link>http://www.johnon.com/663/futures-research.html#comment-128769</link>
		<pubDate>Mon, 13 Apr 2009 00:22:07 +0000</pubDate>
		<guid>http://www.johnon.com/663/futures-research.html#comment-128769</guid>
					<description>To host it yourself. http://www.activecampaign.com/12all/</description>
		<content:encoded><![CDATA[<p>To host it yourself. <a href="http://www.activecampaign.com/12all/" >http://www.activecampaign.com/12all/</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Lea</title>
		<link>http://www.johnon.com/663/futures-research.html#comment-128768</link>
		<pubDate>Sun, 12 Apr 2009 23:38:19 +0000</pubDate>
		<guid>http://www.johnon.com/663/futures-research.html#comment-128768</guid>
					<description>Yes, I read that article too and was somewhat horrified at that quote - being an employee (whether or not they have cleverly classified them as contractors) yet having no surety of income. 
The current system of relationship between 'employees' and 'employers' gives people a lower income offset by some level of assurance of that income.
While one article isn't enough to give full insight into their system, putting all the risk to the employee while the possibility of benefit remains with the employer isn't a fair system - we weren't hearing that these contractors could make huge amounts under this system, just a living.

Admittedly, the article did hint that there may be enough feedback in the system that it does properly look after employees, but I would hate to see other companies copying this system, but not as well, and without that feedback.

But - If you aren't happy with an employee's performance, don't slowly reduce the work they can have - sack them, and let them find a niche they can fit better elsewhere.

On the newsletter question, no, I haven't seen a hosted system that allows control of the list to a proprietary level. I suspect its implied; you can't have the spam-free ness without the 3rd party.
It has occurred to me to pickup a second domain eg in your case Webpresciencemail.com, to send from that I would consider disposable; and dump it and move on if the spam problem became too large.</description>
		<content:encoded><![CDATA[<p>Yes, I read that article too and was somewhat horrified at that quote - being an employee (whether or not they have cleverly classified them as contractors) yet having no surety of income.<br />
The current system of relationship between &#8216;employees&#8217; and &#8216;employers&#8217; gives people a lower income offset by some level of assurance of that income.<br />
While one article isn&#8217;t enough to give full insight into their system, putting all the risk to the employee while the possibility of benefit remains with the employer isn&#8217;t a fair system - we weren&#8217;t hearing that these contractors could make huge amounts under this system, just a living.</p>
<p>Admittedly, the article did hint that there may be enough feedback in the system that it does properly look after employees, but I would hate to see other companies copying this system, but not as well, and without that feedback.</p>
<p>But - If you aren&#8217;t happy with an employee&#8217;s performance, don&#8217;t slowly reduce the work they can have - sack them, and let them find a niche they can fit better elsewhere.</p>
<p>On the newsletter question, no, I haven&#8217;t seen a hosted system that allows control of the list to a proprietary level. I suspect its implied; you can&#8217;t have the spam-free ness without the 3rd party.<br />
It has occurred to me to pickup a second domain eg in your case Webpresciencemail.com, to send from that I would consider disposable; and dump it and move on if the spam problem became too large.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
