{"id":98,"date":"2006-08-21T15:48:54","date_gmt":"2006-08-21T15:48:54","guid":{"rendered":"http:\/\/blog.bananasplit.info\/?p=98"},"modified":"2006-08-21T15:48:54","modified_gmt":"2006-08-21T15:48:54","slug":"layered-technologies-reconnect-me","status":"publish","type":"post","link":"https:\/\/blog.stmellion.org\/?p=98","title":{"rendered":"Layered Technologies reconnect me!"},"content":{"rendered":"<p>Well it came as a surprise to me that <a href=\"http:\/\/www.layeredtech.com\">LayeredTech<\/a> not only accepted my proposal to block the complainants address, but they did it politely and without any additional conditions.  My communications were with someone called Logan and it was a refreshing change to not be treated as a criminal.  My personal thanks to him.<\/p>\n<blockquote><p>\nGreetings!  Thanks for the update.  We are closing this abuse ticket at this time.<\/p>\n<p>We consider use of Tor (or similar software) as not releasing you from our Acceptable Use Policy.  I must warn you that per our policies we hold you accountable for all activity occurring on or through our network. Example, if your use of Tor to hide source\/destination information of packet headers were involved in a more serious incident such as child pornography, we would require you to either discontinue use of Tor or we would have to shutdown the server. Our policy does not permit Acceptable Use Policy violation on or through our network and does not allow alteration of headers of any packet, email, or other service connection. In short, if an abuse occurs such that tracking the origin is modified then you are held responsible. I am not saying at this time that you cannot use Tor, but you are responsible for any\/all abuse which occurs on your server or passes through your server regardless. Therefore, it is your responsibility to install, write, or otherwise place software on your server that would prevent abusive issues from being trafficked through the server to a 3rd party.\n<\/p><\/blockquote>\n<p>I&#8217;ve seen the above paragraph before in communications with <a href=\"http:\/\/www.layeredtech.com\">LayeredTech<\/a>, it&#8217;s obviously a policy they have drawn up to deal with situations like Tor where their paying client is unable to pass the blame on to a specific user.  I&#8217;m not sure how this policy would work in practice as I keep no logs to prove or disprove any complaint that&#8217;s made against me.  Based on this I can only assume that <a href=\"http:\/\/www.layeredtech.com\">LayeredTech<\/a> would take the word of anyone who contacted them and said my <a href=\"http:\/\/tor.eff.org\">Tor<\/a> Server had been used to access Child Porn (for example).  Such a charge would likely get my server disconnected for good regardless of whether it was true or false accusation.  This is a really tricky scenario as the complainant could easily trump up false charges and I would be unable to dispute them owing to the nature of <a href=\"http:\/\/tor.eff.org\">Tor<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Well it came as a surprise to me that LayeredTech not only accepted my proposal to block the complainants address, but they did it politely and without any additional conditions. My communications were with someone called Logan and it was a refreshing change to not be treated as a criminal. My personal thanks to him.&hellip; <a class=\"more-link\" href=\"https:\/\/blog.stmellion.org\/?p=98\">Continue reading <span class=\"screen-reader-text\">Layered Technologies reconnect me!<\/span><\/a><\/p>\n","protected":false},"author":24,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[],"class_list":["post-98","post","type-post","status-publish","format-standard","hentry","category-layered-technologies","entry"],"_links":{"self":[{"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/posts\/98","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/users\/24"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=98"}],"version-history":[{"count":0,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/posts\/98\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=98"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=98"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=98"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}