Show HN: MapChat – A simple location based chat in 300 lines of code
71–80 of 122 posts
Re: Show HN: MapChat – A simple location based chat in 300 lines of code
#72Looks like the user's dot/bubble can be dragged around.
Maybe I'll change it after I'll make messages dissolve after some time.
Re: Show HN: MapChat – A simple location based chat in 300 lines of code
#73Looks like the user's dot/bubble can be dragged around.
Yes, this is intentional. I found it easier to be able to move users that blocked my view. They pop back into place after they write again. Maybe I'll change it after I'll make messages dissolve after some time.
Also requested are message history and dots of different colors.
Re: Show HN: MapChat – A simple location based chat in 300 lines of code
#74Very nice! it would be nice to have an option though that would fuzz your location a bit - I dont have a problem with people knowing im from my city - pinpointing my house is a different thing though...
Re: Show HN: MapChat – A simple location based chat in 300 lines of code
#75> Mixed Content: The page at 'https://idoco.github.io/map-chat/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://chatmap.cloudapp.net/chat/info?t=1434731663123'. This request has been blocked; the content must be served over HTTPS
Re: Show HN: MapChat – A simple location based chat in 300 lines of code
#76Would be great if you could put all resources behind https, otherwise browsers do complain: > Mixed Content: The page at ' https://idoco.github.io/map-chat/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint ' http://chatmap.cloudapp.net/chat/info?t=1434731663123' . This request has been blocked; the content must be served over HTTPS
Currently the websocket connection is in http, I'm not sure how it will effect the server if I change it to https. Will it create more load on it?
Re: Show HN: MapChat – A simple location based chat in 300 lines of code
#77And then it took me like 5 seconds to figure out how to chat. I first tried to click on people's chat to reply to them and then I finally found the text input at the bottom of the screen. Then nothing would happen when I hit enter. Then I eventually found the blue circle send button and that didn't work.
Then I tried Chrome. Worked! So I found some bugs in Safari :)
Amazing that this was done in 300 lines. Something about this format is immediately appealing. Maybe it's because dots on a map feel more human than handles on a forum or comment thread. Anonymity is this double-edged sword in communities. Maybe this is the minimum amount needed to make people behave? Probably not, but something IS interesting here.
Right now it's just people shouting...I hope your next trick is to figure out how to turn it into conversations. Suggestion: Please don't be tempted to just rewrite it or start from scratch. Iterate from this version because 1) it would be faster and 2) this one already has some magic in it.
Thanks for sharing!
Re: Show HN: MapChat – A simple location based chat in 300 lines of code
#78So, this is how my experience started. http://cl.ly/image/071f1j0B0M3a And then it took me like 5 seconds to figure out how to chat. I first tried to click on people's chat to reply to them and then I finally found the text input at the bottom of the screen. Then nothing would happen when I hit enter. Then I eventually found the blue circle send button and that didn't work. Then I tried Chrome. Worked! So I found som…
Re: Show HN: MapChat – A simple location based chat in 300 lines of code
#79Re: Show HN: MapChat – A simple location based chat in 300 lines of code
#80So, this is how my experience started. http://cl.ly/image/071f1j0B0M3a And then it took me like 5 seconds to figure out how to chat. I first tried to click on people's chat to reply to them and then I finally found the text input at the bottom of the screen. Then nothing would happen when I hit enter. Then I eventually found the blue circle send button and that didn't work. Then I tried Chrome. Worked! So I found som…
Just another data point, but using Safari Version 8.0.6 (10600.6.3), and I didn't see this issue. It worked as one would expect.
Version 8.0.6 (10600.6.3)