Live data from Hacker News

Say Hello to Realtime Collaboration

cssdeck.com

31–40 of 47 posts

Re: Say Hello to Realtime Collaboration

#31
Not really a new invention - see 'etherpad-lite' (also opensource) Just with a little work, it would do the same...

But nice to see how all the trolls play... Maybe this is a real good idea... A contest battelfield for trolls... (as a game)

Re: Say Hello to Realtime Collaboration

#34
post #4

Random thought: Imagine if you could see comments on sites like HN being typed live (and the effects that would have on discussion).

Reminds of ICQ group chats back in the day. You're absolu You're absolutely wro (backspaces start) You I respectfully disagree Fun days. EDIT: better dummy conversation

Oh man, that was a fantastic feature! That takes me back...

Re: Say Hello to Realtime Collaboration

#35
This needs to override JavaScript commands to keep it from malicious use. For example, to override alert() do this:

  (function()
  {
    var proxied = window.alert;
    window.alert = function()
    {
      // replacement code here
      // call original function:
      proxied.apply(this, arguments);
    };
  })();

Re: Say Hello to Realtime Collaboration

#37

This needs to override JavaScript commands to keep it from malicious use. For example, to override alert() do this: (function() { var proxied = window.alert; window.alert = function() { // replacement code here // call original function: proxied.apply(this, arguments); }; })();

When I redefined alert to return false, it crashed Chrome pretty bad (note: I am not the owner).

If someone really feels like policing it, they can delete the iframe element (in FF, chrome, or opera) and just have access to the editor panes (which means no alerts, redirects, or other nastiness). I'm sure someone can figure out how to write a javascript snippet that will post some text that has been cleaned of all instances of "window.location", "alert", and probably "while". (I would do it myself, but it's 1am here).

Re: Say Hello to Realtime Collaboration

#38

This needs to override JavaScript commands to keep it from malicious use. For example, to override alert() do this: (function() { var proxied = window.alert; window.alert = function() { // replacement code here // call original function: proxied.apply(this, arguments); }; })();

When I redefined alert to return false, it crashed Chrome pretty bad (note: I am not the owner). If someone really feels like policing it, they can delete the iframe element (in FF, chrome, or opera) and just have access to the editor panes (which means no alerts, redirects, or other nastiness). I'm sure someone can figure out how to write a javascript snippet that will post some text that has been cleaned of all ins…

I put in return false; and it did nothing (using Chrome v22.0.1229.56 beta-m). You wouldn't want to return false anyways, alert is not defined as returning a value (see: https://developer.mozilla.org/en-US/docs/DOM/window.alert)

If you want to see what arguments are being passed, add a console.dir(arguments); to the code.

Re: Say Hello to Realtime Collaboration

#40

Looks like you're being hacked really bad. I got redirected to Google! It was fun to watch though! Add and you'll disable javascript. Good fast fix for now, later you'll want sandbox="allow-scripts allow-forms allow-same-origin" The 4th allowed value for html5 iframe sandbox is allow-top-navigation, which allows a script to do window.top.location.href = ' http://google.com and redirect someone like me.

[deleted]
Post reply on HN