The Anti-disclaimer

A friend and fellow college student of mine asked why I didn’t have a disclaimer on the front off my blog. Then he said, “why should you need a disclaimer?”

I loved how he made a statement, thought about it, and revised it all in a moment of thought. And it got me thinking… thus this post.

Advertisements

Tell me what you're thinking...

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s
https://polyatruelovestory.wordpress.com/2013/02/11/the-anti-disclaimer/
polyatruelovestory.wordpress.com
crawl=CC-MAIN-2018-39
67770
application/http; msgtype=response
sha1:KB5V2NXIWY5BNL2P64PIVLK2MD3MO5FQ
<urn:uuid:897b8452-19c1-42e9-ba6f-f8e3ce03f106>
2018-09-19T09:55:46Z
192.0.78.13
text/html
sha1:DK5RBZXMXZIYNNMZRRLO3DFSRPPZB5MM
<urn:uuid:ff5413de-bd7c-45df-8aca-c8cf5c29f2f4>
https://polyatruelovestory.wordpress.com/2013/02/11/the-anti-disclaimer/
response
<urn:uuid:a03f4b10-fec7-45c0-b45e-e24c72543067>
isPartOf: CC-MAIN-2018-39
publisher: Common Crawl
description: Wide crawl of the web for September 2018
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-95-180-234.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/