UN Human Rights Council Continues the Tradition of Going after Israel

September 16th, 2008 By: Michael van der Galien | Tags:

The United Nations Human Rights council continued on its path of anti-Israelism Monday by declaring that Israel may very well have committed ‘war crimes’ during its ’shelling of Beit Hanoun in Gaza.’

‘The report compiled by Archbishop Desmond Tutu casts doubt on Israel’s explanation that the shelling resulted from a flawed artillery firing system,’ the BBC reported.
Of course, the main problem with the UNHRC is that no one can take it seriously. The council was taken over by Arab countries, who hate Israel with a passion seldom seen before in international relations. They then proceeded to go after Israel whenever they could, in the end declaring that ‘zionism’ constituted racism.

Although it’s very nice of the council to keep a close eye on Israel, one wonders when it will file a report about the crimes committed by Palestinians**, their leaders, their organizations and their government. Until that happens, feel free to ignore whatever comes out of this ‘human rights’ council.’

If the UN Human Rights Council would be more objective and balanced in its approach and condemnation, it would be easier to take it serious; I’m quite positive that Israel may very well sometimes act in breach with human rights. Sadly, because of the obvious bias of the UNHRC I, for one, those real crimes are not getting the attention they deserve (and yes, even speaking as a Israel supporter I believe we should cover crimes committed by Israel, or its potential crimes). At this moment, however, the UNHRC and its members should be happily ignored.

** And lets not even mention countries like Syria, Iran and Saudi Arabia. When was the last time the council spent time and attention to these countries rather blatant and open inhumane policies?

Share and Enjoy:
  • Digg
  • del.icio.us
  • Technorati
  • SphereIt
  • NewsVine
  • TailRank
  • Reddit
  • StumbleUpon

PoliGazette Comments Policy

PoliGazette encourages comments from all viewpoints, especially those that disagree. Comments submitted must, however, adhere to the following standards. Comments that violate these standards may be edited or deleted without notice at the sole discretion of the editors. Commenters who repeatedly or egregiously violate these standards or who attempt to argue publicly with editors regarding the comments policy may be banned from commenting further.

(1) Comments should address the substantive content of the post. Comments that repeatedly or blatantly misrepresent the content of the post or of others' comments are not welcome. Comments that respond to something other than which the contributor or commenter may have said are irrelevant and should not be posted.

(2) Comments should avoid vulgarity as well as racial, ethnic, religious, or sexual bigotry.

(3) Comments should not personally attack the character, personal integrity, or professional reputation of any PoliGazette contributor or of other commenters.

(4) Comments should reflect the contributions of the commenters themselves and should not include extensive cut-and-paste reproductions of others' words except insofar as necessary to supplement the commenter's own arguments. Link spam, trackback spam, and propaganda spam will be instantly deleted.

(5) Public figures are considered open to all substantive criticism of their policies and statements. Comments that present objectively false factual information about public figures (i.e. "Obama is a Muslim") or that attack public figures by attacking their families are not welcome. Comments that merely repeat slogans for or against a candidate without engaging in substantive comment are not welcome.

Questions or challenges to these policies or their application should be directed to the editors by email only.


Warning: is_writable() [function.is-writable]: open_basedir restriction in effect. File(error_log) is not within the allowed path(s): (/home/p6525pol:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/p6525pol/public_html/wp-includes/wp-db.php on line 500