node.js ko
Matt Miller
Former software engineer turned lawyer practicing patent, trademark, copyright, and technology law in New Orleans.
Votes (11)
I get it. This is a good implementation of a feature that dropbox should have. But, who knows. Apparently, Jobs told dropbox that they were just a feature, but now they're more of a platform. So, me telling you that you are a feature of dropbox is kinda like a matryoshka dolls of web based file sharing. An engima wrapped in a mystery.
If you go forward with this, I would change the name and have some good terms of service.
Yes, I played Drug Wars on my 85. Now please go remake a TradeWars 2002.
I like the idea. I am a fan of graphs, and I often use a graphing program called yEd, you might take a look at it.
My comments are that the site was slow. I tried some of my own search terms (other than iran) and didn't get anything to come up.
Here's my suggestion. The graph is good, but the graph isn't necessarily the thing you show the user. It's there, but behind the scenes. The user needs to see a different "view" of the relations. If you do show a graph, don't show a graph with a lot of nodes, as it becomes hard to see everything (or, at least, decrease the node density - everything smushed together becomes cluttered).
I think something like this could be useful for telling the user "if you are searching for X, then you might also try searching for Y" or "if you are reading article A, then you might be interested in article B or articles having terms, B, and C"
jheusala
contestantSlowness is mostly because we didn't have all the data in the database when testing it (and we didn't get time to test the app as much as we would have wanted) but also because Neo4j was totally new technology for us. We wanted to use something new. We already know some queries we could have done faster and of course that current amount of tags is not good at all. We'll fix these after the competition is over.
There's a lot of things we'll probably do later. We were planning to take geo-coordinates and there was also an idea to build a clever cluster of distributed RSS readers.
Looks fun, looks like you could do all kinds of games with this. I'd like to be able to play against a computer opponent, too. Nicely designed. I like the black and white design. Because you are devoid of color, you could make good use of limited amounts of bright color, perhaps even incorporated into the games.
0) I totally get this, I'm from New Orleans and have been though Katrina and the more recent Ike, and I know engineers who have rebuilt the city power systems; 1) Normalize by population and # of reporting users. Right now, if 3 people report in one location, but nobody reports in another location, it looks like the relative damage is greater just because it's been reported; 2) MOBILE. My experience is that mobile service is much more reliable than regular internet, so people will want to use something like this on a mobile device. Just a few months ago, I was sitting in my house at night with no power (Hurricane Ike), but I could stream netflix to my iphone; 3) My power company (Entergy) has a "reporting hotline." Other power companies likely have similar reporting systems. I would not want someone to report damage HERE then not go to their power company. The power company needs to get the reports to know what to fix (they really do. I know people who work on them); 4) You need to have links to other reporting systems. for example, for me, it's this: http://viewoutage.entergy.com/la.aspx - 5) You need to have more categories of reporting. Your damage types are really damage "causes" not damage "types." I suggest, at least, "downed power line" "power out" "cable out" "tree down" "tree down in street" and the like; 6) You have advertising opportunities. Emergency preparedness, insurance, public service (buy flood insurance), etc., etc. I have a pinterest board I've been working on (slowly) to collect all the hurricane items I've found. http://pinterest.com/jmatthew3/hurricane-preparedness/ - the radio is the best (charges your iphone, weather radio, solar, hand crank, etc.)
nicholas-eden
contestantWow, thanks for the lengthy review. You gave me plenty to think about if I continue to work in this.
You need to explain to the user what the site is about on the first page. It's your idea, you know it already. The new user doesn't. Tell them what they get out of using your site. Give more information in the right column. Why is it there? Tell the user. Let the user click on things in that column. If the user needs to be logged in for something to happen, display an appropriate error message.
freehaha
contestantHi, thank you for voting and feedback. You are right that people will probably get lost when they first enter our site. We'll work on that and probably get this site hosted somewhere after the judging ends so thanks for your advise. As for the error message, it's basically because we couldn't get the facebook login information when people enter the site with their facebook already logged on. We'll also fix it as soon as the judging ends. Again, thanks for your valuable opinion!
I get the idea - communicate with your users when your site goes down. I think that further, the site is a way to communicate via all the methods at once. Something like a hub for communications when the shit hits the fan.
This could be a good feature for a site monitoring service. I.e., pay the fee to get site monitoring, then you also get this nifty control panel to communicate with your customers when you go down.
I'd also like to see the "public url" be shortened (possibly to a vanity url) and perhaps even do some fancy auto-redirecting (failover) in conjunction with site monitoring.
This is a very useful product, though perhaps not new. From your video, I understand that English is not your first language. Even if it's not, it's important to have the text of your website written in clear and proper English so people can understand what your site is about without being distracted by language.
This is an interesting use of GIF89a. Appears to be designed fairly well, but I have a few comments. Don't take my comments as negative, I think the idea is very cool. My comments are intended to be constructive criticism.
1) The background static gets annoying quickly. 2) The screamcast overlaps on top of the chat box. My typing is hidden when I chat. 3) My messages obscure my view of the other side. This is unusual to me, although perhaps an intentional design decision to do something unusual. 4) Your team name is unprofessional, and it makes me take you less seriously. 5) Generally speaking, it is a good idea to have proper rights to images, especially ones displayed prominently. For user submitted content, it's generally a good idea to have a strong EULA. Also, it's generally a good idea to register a DMCA Agent for websites displaying user submitted content.
bu
EragonJ
This is good shit. All kinds of places you can go with this. Keep player rankings, saved game boards, drum tracks, etc.