tjanczuk/w3

w3's Issues

show pin on map for every location specified in message

Textbox styles should be consistent (no round corners)

enforce single location and time for posting

how do we go viral

I had that nagging feeling we were missing something important in w3: what are the mechanisms that would support its going viral?

I think we need to consider the Twitter-like concepts of retweeting and following and how they apply to w3.

Unlike on Twitter where you can only follow people, we have additional options of following locations. For example: "I want to follow everything related to 50 miles around Seattle.". How would a timeline look like to visualize this? Is it a map or a list?

I can't think of a scenario for following based on the time attribute.
@Gissues:{"order":33.33333333333332,"status":"backlog"}

pre-load data into system

idea: link shortener

Links in messages should be shortened using our own redirection service. This will give us more data to mine as we will understand what people click on.

list view of results

a mechanism to add events by twitting

special hash tag or follow folks who use our system

Keep query count for messages

Every message should have a counter that is increased every time the messages is returned as part of a user query.

add scripts to configure MongoDB

Primarily to add appropriate indexes.

add twitter and fb auth for posting

preserve user ID with posts

expose rest api for post (authenticated)

make search for location work on the map

should we consider having users to sign up since day one

We need to decide if we want users to sign-up in order to use the app.

cluster map markers

In event-dense areas we should have a way to aggregate icons on the map, a la redfin.

idea: layers

Layers can be a first class concept, or a lightweight concept where layers are created "on the fly" using tags in messages across the viewport.

Markup resolution requires a space after $here and ^now

This should also work with other whitespace characters.

First cut

• authentication with Twitter
• clustering of markers
• better info box
• pre-load data
• opacity of markers - time representation
• 5 star ranking

What limit on the size of the message we should have

140 perhaps to be consistent with Twitter and preserve the option to better integrate?

add date and time accuracy for searching

the map provides geo constraints for search
originally we don't have "what" component in the query

beta people

T Tomek's brother, @andrzejjanczuk, [email protected]
T Glenn, @gblock, [email protected]
T Omri, @Omrig, [email protected]
C VJ
T Alex Dej, @alexdej, [email protected]
C JC
C Andrew Clinick
T Jan Alexander, @janalexcz, [email protected]
T Elad Bin-Israel, @emeshbi, [email protected]
C Ari Bixhorn
T Shawn Burke, @funcshawnal, [email protected]
C Peter Galli
C Tom Hughes-Croucher
T Miika, @mantyvaara, [email protected]
C Eugenio Pace @Eugenio_pace [email protected]
T Andrew Miadowicz
C Tal Saraf @tsaraf, [email protected]
T Erich Pleny, @erichpleny, [email protected]
C Trent Swanson
T Oliver Sharp, @ojsharp, [email protected]
T Mikolaj Sibila, [email protected], no twitter account yet
T Adam Tepper
T Michal Zawirski, @mzawirski, [email protected]

expose rest api for query (anonyous)

Make the web site work in IE in addition to web browsers

Chrome - works
Safari - works
FF - works
IE - blank screen

Autocompletion for markdown chars

It would be great if we can display autocompletion/hint when the user types the special chars: ^ $, ....

Show My Current Location should display a Pin on the map

$here in the search box takes you to Here, Maharashtra 416509, India

latitude/longitude are in the wrong order in the REST response

Maybe it is the Google's map convention but usually coordinates are in Latitude-Longitude order
In the README, the REST call samples seems to be in the opposite order: longitude-latitude.

"location": {
"type": "Point",
"coordinates": [
-122.043556008789,
47.6222513047473
]
}

Not a big deal, just make sure we are consistent.

clone map icons

add authentication to post API

upper left corner: Google Street view mode

There is a small bar in the upper left corner that allow users to switch to street view.
If the user clicks on that there is no way to go back to the W3 app, clicking on the browser's back button take the user back to the twitter login page.

Maybe we should disable Street view for now

geocode named locations in real time

https://developers.google.com/maps/documentation/javascript/geocoding

zoom controls look squashed

Long live SO: http://stackoverflow.com/questions/9663375/google-map-infowindow-not-showing-properly

idea: social features

Some ideas:

• voting events up or down
• commenting on events
• "re-twitting" the events
• sharing via twitter or facebook

add index for hash tags

TIme field contains the date when the post was submitted, not the date defined in the post

"time": {
"type": "Moment",
"time": [
1371600000000
]
Should this field contain the date the user specified in the post instead of the date of when the post was submitted?
Ex.
POst submitted on 07/31/2013
$(Monroe, wa) ^(2013-08-01) Farmers' market
the time field should be set to 2013-08-01 instead 2013-07-13

@Gissues:{"order":66.66666666666666,"status":"backlog"}

support correlating normalized entries resulting from a single post

Several entries can be created in the DB when a post specifies more than one location or time. We should be able to correlate them back to one post to enable more data analysis.

add client validation to Post

Feedback widget

For Alpha/Beta should we have a UI widget to allow users to submit quick feedback about the app?