You're looking at Less Wrong's discussion board. This includes all posts, including those that haven't been promoted to the front page yet. For more information, see About Less Wrong.

malcolmocean comments on Open thread, July 16-22, 2013 - Less Wrong Discussion

13 Post author: David_Gerard 15 July 2013 08:13PM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (297)

You are viewing a single comment's thread. Show more comments above.

Comment author: Error 16 July 2013 11:50:18AM 7 points [-]

I've run into a roadblock on the Less Wrong Study Hall reprogramming project. I've been writing against Google Hangouts, but it seems that there's no way to have a permanent, public hangout URL that also runs a specified application. (that is, I can get a fixed URL, or a hangout that runs an app for all users, but I can't do both)

Any of the programmers here know a way around that? At the moment it's looking like I'll have to go back to square zero and find an entirely different approach.

Comment author: malcolmocean 16 July 2013 10:47:27PM *  5 points [-]

Could you have a server that knows where the dynamic url is at all times, and provides a redirect? So I'd hit up lwsh.me and it would redirect me to <https://plus.google.com/hangouts/_/etc> ...that would create an effectively permanent url, even though the hangout itself would change urls.

Looking at the Hangouts API, it appears that when the app is initialized you could call getHangoutUrl() and then pipe it back to the server. This could probably be used in a pretty dynamic manner too... like whenever anyone uses the app, it connects with the main server and adds that chat to the list of active chats...