Page 1 of 1

Shareaza commit log behaving incorrectly again

PostPosted: 20 Jan 2015 23:42
by Lanigiro
For the past 2 days I have been unable to view Shareaza's commit log at Sourceforge. The SF webserver incorrectly serves a 500 error page instead of the commit log and claims that "something went wrong" even though I did not do anything wrong (in particular, I triple-checked that I am using the correct URL, the same one that worked fine 3 days ago).

Why am I being refused the right to examine the commit log, even though that is supposed to be publicly viewable? I hereby appeal this sentence on the grounds that a) I did nothing wrong; b) there was no apparent due process attendant the decision to deny me access to view this document; and c) I was on no occasion given the opportunity to face my accusers, confront the evidence against me, or present my own defense. Either reinstate my ability to view the commit log or formally accuse me, present your case against me, and permit me to present my case in my own defense and let a neutral party evaluate things and come to a decision on whether to reinstate my ability to view the commit log.

Re: Shareaza commit log behaving incorrectly again

PostPosted: 21 Jan 2015 01:40
by Lanigiro
For the record, the URL I'm using is:

http://sourceforge.net/p/shareaza/code/HEAD/log/

If that is actually incorrect, please let me know. If it's not, then I demand an explanation for why I am being systematically obstructed in my efforts to view the web page at that URL. I've even tried going through a proxy in case the block was based on the connecting IP. No go. Somehow they/you still know it's me and serve that bogus error page instead of the web page with the commit log.

I will remind everyone here that the United Nations Declaration of Human Rights includes, among other things, the right of all people to receive and impart information, which in particular guarantees my right to view any piece of non-secret information in existence. I'm pretty sure the Shareaza commit log is neither a state secret nor a trade secret; therefore, I have the right to view it, and the highest organizations and courts on this planet agree that I have the right to view it.

Whoever is obstructing me from viewing that page is therefore violating a human right. Furthermore, if you are not the responsible party but someone at Sourceforge is, that individual is also violating *your* right to *impart* information.

What the hell is going on with that commit log page? Why is it recurrently a problem, as of the year 2015, when it never used to be? Someone is screwing around with me and quite possibly with you too. I want to know who, and I want it to stop and for that web page's behavior to return -- PERMANENTLY -- to normal forthwith.

Re: Shareaza commit log behaving incorrectly again

PostPosted: 27 Jan 2015 15:15
by ianap

Re: Shareaza commit log behaving incorrectly again

PostPosted: 28 Jan 2015 07:19
by Lanigiro

Re: Shareaza commit log behaving incorrectly again

PostPosted: 29 Jan 2015 18:29
by ianap
Those mean web servers, always misbehaving on their own!!!
What about a lawsuit? I'm pretty sure the Supreme Court would have the time of their lives with this case.

Re: Shareaza commit log behaving incorrectly again

PostPosted: 30 Jan 2015 08:16
by Lanigiro
I think specific users being inappropriately blocked from merely viewing selected pages is a bit more serious than is implied by the word "misbehaving". It's making a molehill out of a ... hill, I suppose. (A molehill out of a mountain would be to claim that Darren Wilson or George Zimmerman were merely "misbehaving" when they abused their authority.)