<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml"
	>
<channel>
	<title>Comments on: File Size Matters</title>
	<atom:link href="http://www.trustyetc.com/trustyblog/2007/02/28/file-size-matters/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.trustyetc.com/trustyblog/2007/02/28/file-size-matters/</link>
	<description>Effective and Efficient Education</description>
	<lastBuildDate>Fri, 10 Feb 2012 17:39:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Alvin&#8217;s Educational Technology Blog &#187; Efficiency Tip #70 - No Attachments</title>
		<link>http://www.trustyetc.com/trustyblog/2007/02/28/file-size-matters/comment-page-1/#comment-1432</link>
		<dc:creator>Alvin&#8217;s Educational Technology Blog &#187; Efficiency Tip #70 - No Attachments</dc:creator>
		<pubDate>Thu, 05 Jul 2007 12:14:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.trustyetc.com/trustyblog/?p=54#comment-1432</guid>
		<description>[...] are some efficiency issues.Â Here is part ofÂ a previous post on the subject: Do you realize the process involved in sending someone a file attachment. Since [...]</description>
		<content:encoded><![CDATA[<p>[...] are some efficiency issues.Â Here is part ofÂ a previous post on the subject: Do you realize the process involved in sending someone a file attachment. Since [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alvin&#8217;s Educational Technology Blog &#187; Efficiency Tip #69 - Zip</title>
		<link>http://www.trustyetc.com/trustyblog/2007/02/28/file-size-matters/comment-page-1/#comment-1372</link>
		<dc:creator>Alvin&#8217;s Educational Technology Blog &#187; Efficiency Tip #69 - Zip</dc:creator>
		<pubDate>Tue, 03 Jul 2007 03:12:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.trustyetc.com/trustyblog/?p=54#comment-1372</guid>
		<description>[...] a previous post, I mentioned that file attachments are something you should avoid.Â There are times when they are [...]</description>
		<content:encoded><![CDATA[<p>[...] a previous post, I mentioned that file attachments are something you should avoid.Â There are times when they are [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Schinker</title>
		<link>http://www.trustyetc.com/trustyblog/2007/02/28/file-size-matters/comment-page-1/#comment-78</link>
		<dc:creator>John Schinker</dc:creator>
		<pubDate>Fri, 02 Mar 2007 18:15:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.trustyetc.com/trustyblog/?p=54#comment-78</guid>
		<description>For people without an LMS for transferring files, one option is to use senduit (http://senduit.com/). Essentially, you upload a file, decide how long the file should be available online (30 minutes to one week), and it gives you a URL. Just send the URL via email, and the recipient can download the file.

It&#039;s probably not a great idea for confidential information, and it does have a 100 MB limit, but it would help keep the attachment volume down. 

In my school district, we&#039;ve considered implementing a system that intercepts email attachments larger than a defined size (4 MB, for example), uploads them to a file repository, and replaces the attachment in the email message with a link to the file. While this would solve the huge attachment problem, it does it by working around the users&#039; irresponsible technology choices instead of teaching them how to use the technology more reasonably. I&#039;m not sure that&#039;s a direction we want to head, so at the moment we just limit the message size at the server.</description>
		<content:encoded><![CDATA[<p>For people without an LMS for transferring files, one option is to use senduit (<a href="http://senduit.com/" rel="nofollow">http://senduit.com/</a>). Essentially, you upload a file, decide how long the file should be available online (30 minutes to one week), and it gives you a URL. Just send the URL via email, and the recipient can download the file.</p>
<p>It&#8217;s probably not a great idea for confidential information, and it does have a 100 MB limit, but it would help keep the attachment volume down. </p>
<p>In my school district, we&#8217;ve considered implementing a system that intercepts email attachments larger than a defined size (4 MB, for example), uploads them to a file repository, and replaces the attachment in the email message with a link to the file. While this would solve the huge attachment problem, it does it by working around the users&#8217; irresponsible technology choices instead of teaching them how to use the technology more reasonably. I&#8217;m not sure that&#8217;s a direction we want to head, so at the moment we just limit the message size at the server.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

