Update on killassange.com, domainsbyproxy #IFWL

Continuing my efforts to alert registrars and hosting providers on IMHO defamatory domain names, which started here.

The domain killassange.com has no DNS entries at the moment, meaning you cannot reach it. Which is a good thing and thanks to HPCISP.com for reacting so timely and solving this matter.

However, the domain itself still exists and can become active at any time. Hence my request to domainsbyproxy.com, the company the registered the domain on behalf of their customer through godaddy, as revealed by the whois data.

domainsbyproxy.com offers a webform for complaints, which I used to send this request:

As documented in my blog post at

WRT killjulianassange.com, killassange.com and godaddy

It is my honest opinion that the domain kulljulianassage,com is unacceptable. Your Domain Name Proxy Agreement at https://www.domainsbyproxy.com/policy/ShowDoc.aspx?pageid=domain_nameproxy states in 4 – iv – G:

G. If it comes to DBP’s attention that You are using DBP’s services for purposes of engaging in, participating in, sponsoring or hiding Your involvement in, illegal or morally objectionable activities, including but not limited to, activities which are designed, intended to or otherwise:

[…]

2. Defame, embarrass, harm, abuse, threaten, or harass third parties;

[…]

In my humble opinion the domain name killassange.com is without doubt in this definition. Therefore I urge you take the appropriate action and remove this domain name from the registry, inform the owner of this domain of your actions and update me via e-mail in the next 48 hours

This complaint has been documented at my blog at http://jan.wildeboer.net/2011/01/update-on-killassange-com-domainsbyproxy-ifwl/ and I would like to publish your reply at ethe same place. Should you object to this, please state so in your reply.

Jan Wildeboer

The popup after submit told me:

Thank you for your submission. Your tracking ID number is 575601. Please refer to this ID number when communicating with our office (generalmanager@domainsbyproxy.com) regarding this report. Please allow up to 3 business days for us to contact you about this claim.

Updates will be added to this entry as they come to my attention.

No comment. #IToldYouSo #IFWL

Peter T. King, Chairman of the House Committee on Homeland Security.

To Clinton:

Dear Secretary Clinton:

I am writing to request that you undertake an immediate review to determine whether WikiLeaks could be designated a Foreign Terrorist Organization (FTO) in accordance with Section 210 of the Immigration and Nationality Act (INA). In addition, I urge you to work with the Swedish government to determine the means by which Mr. Julian Assange can be brought to justice for his actions while recognizing and respecting Swedish sovereign law.

As Admiral Mike Mullen, Chairman of the Joint Chiefs of Staff concluded, the “irresponsible posting of stolen classified documents by WikiLeaks puts lives at risk and gives adversaries valuable information.” I concur with Chairman Mullen’s statement.

As you know, on Sunday, November 28, 2010, WikiLeaks released its third trove of classified information, in part consisting of 250,000 classified documents from the Department of State, causing grave damage to U.S. national security and our diplomatic relations. The latest release follows WikiLeaks’ October 22, 2010 disclosure, which surmounted to the largest classified military leak in history. The latter, known as “The Iraq War Logs,” included 391,832 classified documents pertaining to U.S. military operations in Iraq from January 1, 2004 through December 31, 2009. That release followed WikiLeaks’ July 2010 release of 76,900 classified documents pertaining to U.S. operations military in Afghanistan. By the sheer volume of the classified materials released, rendering harm to the United States seems inevitable and perhaps irreversible.

From these acts, WikiLeaks appears to meet the legal criteria for FTO designation as a (1) a foreign organization; (2) engaging in terrorist activity or terrorism which (3) threatens the security of U.S. nationals or the national security of the United States. Specifically, pursuant to Section 212 (a)(3)(B) of INA (8 U.S.C. § 1182(a)(3)(B)) WikiLeaks engaged in terrorist activity by committing acts that it knew, or reasonably should have known, would afford material support for the commission of terrorist activity.

The Department of Defense has already recognized that WikiLeaks’ dissemination of classified U.S. military and diplomatic documents affords material support to terrorist organizations, including Al Qaeda, Tehrik-e-Taliban Pakistan (TTP), Al Shabaab, and Hezbollah. In fact, On October 22, 2010, Pentagon spokesman Col. Dave Lappan stated:

We know terrorist organizations have been mining the leaked Afghan documents for information to use against us and this Iraq leak is more than four times as large. By disclosing such sensitive information, WikiLeaks continues to put at risk the lives of our troops, their coalition partners and those Iraqis and Afghans working with us.

The WikiLeaks releases provide valuable information and insights to FTOs throughout the world on U.S. military and diplomatic sources and methods and allow our enemies to better prepare for future U.S. and allied military, intelligence, and law enforcement operations targeting them. In addition, the leaks allow nation-states such as Russia, China, and Iran access to information regarding how the United States collects, analyzes, and produces intelligence products.

WikiLeaks presents a clear and present danger to the national security of the United States. I strongly urge you to work within the Administration to use every offensive capability of the U.S. government to prevent further damaging releases by WikiLeaks.

Thank you for your time and consideration of this urgent matter.

Sincerely,

PETER T. KING

To Holder:

Dear Attorney General Holder:

I am writing to urge you to criminally charge WikiLeaks activist Julian Assange under the Espionage Act, 18 U.S.C. § 793.

On Sunday, November 28, 2010, WikiLeaks released its third trove of classified information, which in part consists of 250,000 classified documents from the Department of State, causing grave damage to U.S. national security and our diplomatic relations. This latest release follows WikiLeaks’ October 22, 2010 disclosure, which surmounted to the largest classified military leak in history. The latter, known as “The Iraq War Logs,” included 391,832 classified documents pertaining to U.S. military operations in Iraq from January 1, 2004 through December 31, 2009. That release followed WikiLeaks’ July 2010 release of 76,900 classified documents pertaining to U.S. military operations in Afghanistan. By the sheer volume of the classified materials released, rendering harm to the United States seems inevitable and perhaps irreversible. Moreover, the repeated releases of classified information from WikiLeaks, which have garnered international attention, manifests Mr. Assange’s purposeful intent to damage not only our national interests in fighting the war on terror, but also undermines the very safety of coalition forces in Iraq and Afghanistan. As the Department of Defense has explicitly recognized, WikiLeaks’ dissemination of classified U.S. military and diplomatic documents affords material support to terrorist organizations, including Al Qaeda, Tehrik-e-Taliban Pakistan (TTP) and Al Shabaab.

As you are aware, following Private First Class Bradley E. Manning’s unauthorized access and transmission of classified materials, he was charged under the Uniform Code of Military Justice for several counts, including violation of 18 U.S.C. § 793(e) for willfully transmitting a “classified video of a military operation filmed at or near Baghdad, Iraq, on or about 12 July 2007 to a person not entitled to receive it.” Given Mr. Assange’s active role in encouraging the theft and distribution of classified material, he should be held liable pursuant to section 793(g), which provides that if more than one person conspire to violate any section of the Espionage Act and perform an act to the conspiracy, then “each of the parties to such conspiracy shall be subject to the punishment provided for the offense which is the object of such conspiracy.” In addition, Mr. Assange should be chargeable for obtaining classified documents pertaining to national defense initially acquired in violation of the Espionage Act and for willfully retaining such documents with the knowledge that he was not entitled to receive them.

There should be no misconception that Mr. Assange passively operates a forum for others to exploit their misappropriation of classified information. He actively encourages and solicits the leaking of national defense information. He pursues a malicious agenda, for which he remains totally immune to the consequences of his actions. In his July 2010 interview, Mr. Assange discussed his editorial control over the classified materials, noting that WikiLeaks is “clear about what we will publish and what we will not. We do not have

ad hoc editorial decisions.” He was even more resolute in his motivations: “I enjoy crushing bastards. So it is enjoyable work.”

As Admiral Mike Mullen, Chairman of the Joint Chiefs of Staff concluded, the “irresponsible posting of stolen classified documents by WikiLeaks puts lives at risk and gives adversaries valuable information.” I concur with Chairman Mullen’s assessment.

Thank you for your prompt attention to this matter.

Sincerely,

PETER T. KING

WRT killjulianassange.com, killassange.com and godaddy

[UPDATE 2011-01-13 12:30 CET Trying to get at the domain owner of killassnge.com via domainsbyproxy in seperate post]
[UPDATE 2011-01-12 18:20 CET: killassange.com seems to have no DNS entry ATM, therefore not resolving. Success?]
[UPDATE 2011-01-11 21:54 CET: killassange.com and killjulianassange.com both up and running, no reply from godaddy so far]
[UPDATE 2011-01-11 11:44 CET: Seems the domain julianassangemustdie.com has been deleted by its owner. See Godaddy WHOIS entry]
[UPDATE 2011-01-11 11:33 CET: Seems killjulianassange is down ATM. Could be simple change though.]
[UPDATE: I send an updated mail with the doamin julianassangemustdie.com added and clarified some aspects. New version reproduced here, old version archived in this same post.

I have just sent this mail to abuse@godaddy.com and urge you to do the same:

Dear Godaddy,

as instructed by your twitter account, I hereby request to check if the domain names registered by godaddy on behalf of your customers

* killassange.com
* killjulianassange.com
* julianassangemustdie.com

are in violation of your terms of use.

In my personal opinion they are in violation of your terms of use as stipulated at

http://www.godaddy.com/Agreements/ShowDoc.aspx?pageid=TOU&ci=20801&app_hdr=0

more specifically 4 iv which I partly quote verbatim here:

* Promotes, encourages or engages in hate speech, hate crime, terrorism, violence against people, animals, or property, or intolerance of or against any protected class;

Therefore I kindly request to take the appropriate action and inform the owner of these domains about your findings.

I also kindly request to be informed of the outcome in the next 14 days.

I will continue to check if these domain names are active and which content is hosted.

I have published this email on my blog at

WRT killjulianassange.com, killassange.com and godaddy

I would like to publish your response at the same place, as my readers and twitter/identi.ca followers have indicated their interest in the resolution of this issue.

Should you not want to see your reply published, please explicitly state that in your reply.

Kind regards,

Jan Wildeboer

This is the old version I sent yesterday.

Dear Godaddy,

as instructed by your twitter account, I hereby request to check if the domain names

killassange.com and
killjulianassange.com

are in violation of your terms of use.

In my personal opinion they are in violation of your terms of use at

http://www.godaddy.com/Agreements/ShowDoc.aspx?pageid=TOU&ci=20801&app_hdr=0

more specifically 4 iv:

* Promotes, encourages or engages in hate speech, hate crime, terrorism, violence against people, animals, or property, or intolerance of or against any protected class;

Therefore I kindly request to take the appropriate action and inform the owner of these domains about your findings.

I also kindly request to be informed of the outcome in the next 14 days.

I will continue to check if these domain names are active and which content is hosted.

Kind regards,

Jan Wildeboer

I will update this post should I receive a reply.

PRR – Privacy Respecting Router a #freedentity idea

In the next few weeks I will outline more parts of something we (a few friends of me) are calling FreeDentity. That’s why I have added a category and a tag to my posts with the same name. So stay tuned for the philosophy, while in this post I talk about a project idea that actually implements that philosophy.

The PRR – Privacy Respecting Router

The typical internet user in the developed countries has a DSL connection with quite some speed (and unused bandwidth). For many people the main communication paths are email, facebook, twitter. Domain names are cheap. DynDNS etc allow you to reach your router at home with a defined hostname.

Current news show us a future that isn’t that bright. Subpoenas against twitter users that only see the light due to twitter legal department asking to unseal the sealed (thus secret) subpoena are just the tip of the iceberg.

The only solution is actually quite simple. In order to gain more control over your privacy and data, you should keep it under your control whenever possible. Handing your data to Facebook, twitter or gmail however is the opposite of that. You hand over your data under typically broad terms of use that give Facebook, Twitter, Google a lot of rights and leave you in the dark about what actually happens with it.

Two things have happened however that might make a change for some of us (hopefully becoming more and more):

  • Decentralized Open Solutions like statusnet, diaspora and good ole email servers
  • Powerful routers that can handle a lot of work, not just forwarding and NATting IP packets.

So let’s combine all of that into one thing. An Open Source firmware for typical routers that offer these functions, thus keeping your data private but still allowing you to share with the world. All of that under an extremely simple User Interface.

A firmware that when doing its first-time config asks you for your domain name, sets up a local mail server for that domain, updates the DNS entries to make sure your mail comes to you.

A firmware that sets up a simple instance of statusnet, with the possibility to sync your dents to twitter.

A firmware that runs a simple instance of diaspora, allowing you to do the facebook dance from your home.

A firmware that hands out WebID so you can use your server from the internet in a secure way, eg from your android phone, netbook etc when on the road.

A firmware that stores all of your data in a secure way either on flash, USB Harddrive or NAS – but local, not in the cloud.

The requirements are thus:

  • Simple Installation Ask only what is really needed, do everything with automagic in the background.
  • Reliability run forever, use minimal resources.
  • Secure Encrypt whatever goes out and comes in.
  • Open Use only open standards, only Free Software. Royalty Free. No calling home. No central registry of users.

Would that be what Moglen talks about when referring to his freedom box? I don’t know. But I do know that my data is too valuable to let out uncontrolleed or governed by companies that I cannot trust forever.

[SOLVED] Joindiaspora and me – #FAIL all over the place

*UPDATE* My problems are fixed! I am impressed. Finally I can use Diaspora again. Thanks to the devs who finally looked at Bug #734 and fixed my problems.

So I am one of those with an account at joindiaspora. And I have some requests by other users to become my contact.

Which is nice! But since 2 weeks, I cannot accept these requests, I cannot read notifications, I cannot use anything but the homepage. Because everytime I click on the requests, on the notifications, on my aspects, I get a nice Error 500:

I found out after a bit of thinking and searching that the root cause probably is in this bug report:

Not sure, but I think it’s because someone who invited me has deleted their account.

Which could make sense. If someone sends me a request and deletes his account before I accept the request, the now orphaned request seems to cause trouble. Ofcourse this means that the current process of deleting an account in diaspora is a bit sloppy as it seemingly doesn’t care about such orphaned requests. With all that in mind, some other brave soul with is own diaspora node tried my guess and – guess what – it turns out to be reproducible:

“I managed to reproduce the error on my local Diaspora installation by deleting the person from whom the request comes from manually from MongoDB. I get exactly the same error so this I probably the cause.”

OK, so we have the root cause nailed down, we have a bug report. Now the only thing needed is a developer who fixes it and pushes the fix to joindiaspora.com.

And that is where we are. Unfortunately nothing seems to happen. No developer takes the bug, no one reacts. This bug renders my account effectively useless as I can do nothing besides doing a reload on the homepage. As soon as I switch to aspects, try to answer requests or even read my notifications . error 500.

I do hope this blog entry might be read by one of the diaspora devs. Please fix this. I am ready to help. But you need to react on your won bugtracker first. ATM this is a #FAIL situation. 16 days of an open bug and not a single action from the devs.

To those of you that sent me requests and wonder why I don’t act – here you are.