<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:admin="http://webns.net/mvcb/"
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns:content="http://purl.org/rss/1.0/modules/content/">

	<channel>

	<title>&#45; CircleID</title>
	<link>https://www.circleid.com/blogs/</link>
	<description>Postings from  on CircleID</description>
	<dc:language>en</dc:language>
	<dc:rights>Copyright 2026, unless where otherwise noted.</dc:rights>
	<dc:date>2026-03-31T21:29:00+00:00</dc:date>

	
	<item>
		<title> Regulating and Not Regulating the Internet (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/postsregulating_and_not_regulating_the_internet</guid>
		<link>https://circleid.com/postsregulating_and_not_regulating_the_internet</link>
		<description><![CDATA[There is increasingly heated rhetoric in DC over whether or not the government should begin to "regulate the internet." Such language is neither accurate nor new. This language implies that the government does not currently involve itself in governing the internet -- an implication which is clearly untrue given a myriad of laws like CFAA, ECPA, DMCA, and CALEA (not to mention existing regulation of consumer phone lines used for dialup and "special access" lines used for high speed interconnection). <a href="https://circleid.com/postsregulating_and_not_regulating_the_internet">More...</a>]]></description>
		<dc:date>2026-03-31T14:29:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>