Link to Original Source
That said, I want to ask Dice why they are so eager to kill off Slashdot.
Is there a secret buyer somewhere waiting to grab this domain, Dice ? Just tell us. There are those amongst us who can afford to pay for the domain. What we want is to have a Slashdot that we know, that we can use, that we can continue to share information with all others.
Please stop all your destructive plans for Slashdot, Dice.
Flickering and architectural problems. The first is purely cosmetic, but is impossible to fix without making chances to the core protocol. The second means that an order of magnitude more work is required to add new functionality than what could be done with a more modern design.
Daniel Stone explains the problems with X11 in great details here: http://www.youtube.com/watch?v=RIctzAQOe44
obviously by ssh admin he means whoever administrates access to ssh, and would allow X forwarding in the sshd_conf file...
You are incorrect. X forwarding still requires giving your local host permission to the x server.
I don't know which distro you use, but usually that is enabled unless whoever administrates access to ssh disables it.
Well, assuming that the ssh admin has permitted ssh forwarding. And that you invoked your ssh client with the appropriate flags. And that you export the DISPLAY variable on the remote host. And that you set your xhost permissions on your own host.
Other than that, nothing to be done.
ssh -X user@host xterm?
Damn hard that is!