Hacker News Reader

Comment by alexsolo | Hacker News Reader

I went to the site and clicked on the "chat live on visitrs" link in the bottom right corner. I got a tiny pop-up which was blocked by Firefox's popup blocker. I think there are ways to fix this so the pop-up does not get blocked when clicking on the link.

I set FF to allow the pop-up, and then got a blank window (not sure if this is a problem with the site or with FF). I closed the window, and clicked on the chat link again, at which point I did get a pop-up asking me to login or register. At this point, I just gave up.

I would strongly recommend not requiring registration for this type of application.

View on HN

i guess popup frenzy will be problematic, but it's the only way i could come up with to enable using the same chat window in multiple sites.

thanks for comments about registration. I have the idea of allowing users to discriminate by nicknames. By Openid and Oauth users are already using the same id's on many websites, so i believe it would be ideal to use same ids on visitrs, for it's aim is to connect the websites community online in almost realtime. But maybe i'm wrong :)

thanks

I've added anonymous login option. Visitors can just login by entering user name, if chosen username is not registered.

Thanks for feedback.

Chrome blocked that window, too. I guess an inline div would be better.

By default blocking the unwanted popups is set in browsers.

Visitrs enables chatting in the same window regardless of whichever different domain the user is coming from, which serves the purpose "not interrupting the surfing process while chatting or vice versa" well (i guess :). In other implementations like using floating page elements or iframes for chatting, when user moves away from the domain,or opens another link in the same window, chat is interrupted.

I've updated the popup window contents where if popup is blocked, visitor can continue by simple clicking the inner link of the popup. I hope this will help usability.

Thanks for feedback.

Reply on news.ycombinator.com