HN user
I'd say it stands to reason that people didn't want to miss the outcome.
You could imagine someone casually watching the game is now suddenly riveted to what he or she is watching since the intensity and drama just spiked.
Millennia of imbalance towards men having the upper hand in just about all societies is a plain fact.
However, progress and equality is not the reversal of an imbalance - it's the leveling of a playing field and accepting that to achieve real meaningful change, the notion of retribution must be taken off the table.
Either it's ok for both genders to have a service like this, or it is not ok for either gender to have a service like this. End of story.
Personally I'd find any site like this reprehensible for either gender (or any other biologically or socially discernable metric, for that matter).
Could not agree with the sentiment of this article more.
Do not copy and paste code when you're trying to learn
Always type it out
Off the cuff, I'd suggest something like #2
Charging per client will probably lead to people getting clever, and simply giving multiple clients the same login, that they themselves own and consider as the cost of the service.
Also, it seems like a per-client pricing directly "punishes" people who work on larger, multi client projects, whereas a flat rate for a tiered product encourages them to make the most of what they've been given.
Just my 2 cents, take it for what it's worth.
Might be able to do UserAgent parsing then... since you're doing a very specific target, it might (keyword might) be simple to do a string compare against whatever the UserAgent of the WinForm app is (I have no idea what it would be, but you could test this very easily), and use that as how you detect.
Is this HTML that you control?
If you're loading it through a C# WinForm control, you might be able to do something like pre-inject a hidden input tag onto the page with a particular name/value, and then in the javascript on the actual page, check for that tag to determine if the page was loaded via a form... I'd guess you'd make a HttpWebRequest out to the resource you want, manipulate the response in some way, then load it into your viewable control... I'm shooting from the hip here, so this is just a guess. I haven't worked in WinForms for a while now.
You might want to look at your approach, however... Are you absolutely in need of having this page be loaded through a WinForm?
Edit: Also the dude suggesting you post this on SO is correct
I hate to hijack the comments with a response that doesn't address the OPs question at all, but I felt like that wasn't necessarily a fair comparison.
ASP.NET Webforms? Yes, huge mistake you'll regret
ASP.NET MVC? Fantastic choice, you will not regret it so long as you're a microsoft based shop
You can't make a blanket statement like that about ASP.NET, since it's effectively a bifurcated ecosystem at this point (and we're all hoping the WebForms fork dies a quick death).
I have a Bachelors in CS
If I had to give a simple, concise answer: Yes, it helped.
If I had to give a longer winded, more precise answer, summed up by a simple, concise answer: It's ultimately debatable, but I'm glad I have it.
If I had to take a stab in the dark, I'm picturing your target audience being someone who owns and manages their condo (not the individual tenants) or a number of condos.
If I had to further guess, these probably aren't the kinds of people who are very technologically savvy, and thus are very unlikely to find your service (even through google awords), let alone realize the potential and why they'd need it.
You say you had a startup before where you physically got in touch with potential customers... this may be the case for another approach like that.
You might consider setting up a demo where you show them an example of a "Condo" already running in your system, the benefits, etc etc, then show them how to get set up on their own. In other words, show them why they'd want to sign up, then show them how easy to get going it is.
But you might still be a step before that process, if you feel you need to improve the app a bit (which is something you'll always need to focus on, anyways). Maybe try reaching out to some people who own / manage condos in your area, explain the service, and offer them a free trial. Draw up some promotional material to give to their tenants, explaining how this will help them get things done, meet neighbors, etc etc, to help those people get going with the system, and then keep a constant and frequent feedback loop with all of them.
Best of luck!
I thought I was the only one...
Thanks for the feedback!
Slightly off topic - would you mind describing how you host and run the python/flask app?
Do you use uWSGI with apache / nginx in front of it? I dabble in python web apps and wanted to get some insight into how other people had them hosted
Receiving a plaintext password via Email is not proof that the password is stored in plaintext in the database.
It is proof that they are not using a non-reversible hash to store it in their database.
They could be storing it using a reversible encryption algorithm, of which there are many, and they are not considered "insecure".
Or, in the worst case, they could be storing it unsecured. It's definitely a possibility.
It's poor practice, for sure, to email someone a plaintext password, as email itself is prone to numerous attack vectors.
But given the overall lack of evidence and insight into their back end, you don't have enough to draw either conclusion.
I'll take a look, thanks!
Wow, thanks for responding!
I hope it didn't come across as negative, it was just something I noticed and wondered if other people saw the same thing, or if I was just being nitpicky.
I hope your project reaches funding, this looks like a really cool idea
This looks interesting, the tabbed effect is a major draw for me personally, but I feel like hes got a bit of a price tier issue with the rewards on the kickstarter...
His target price for the released product is hopefully $10 ( a good deal )
The $20 pledge gets you 2 licenses Cost Per License: $10 Additional Perk: Nothing
The $50 pledge gets you 1 license Cost Per License: $50 Additional Perk: Beta Access
The $100 pledge gets you 5 licenses Cost Per License: $20 Additional Perk: Immediate Access
And that's just a small analysis of those 3 price points. The higher points also seem a little off to me as well. It just seems odd to have the Cost Per License to vary so wildly, in my unsolicited opinion, anyways.
I understand trying to play to the draw of people wanting quicker access to use the tool, but his pricing model creates tiers that are counter-intuitive to people who want to contribute, but do not want to receive what could be perceived as a poor value for the cash they have available to contribute.
It all started with a father who cared enough to get his son involved in something that he could be passionate about.
Don't sell yourself short
I wonder if this odd placeholder site has anything to do with it...
Hindsight is 20/20, but I think a lot of people looked at Color with very skeptical eyes. It seemed like a really strange concept (to me, at least, and I'm sure others) at the time that garnered a great deal of attention out of nowhere (not to mention an enviable amount of cash). I think some people wanted to believe it would be the next big "social thing", and they looked at the folks behind it and thought "Well, there's no way people wont eat this up!".
I mean, they made headlines by blowing a ridiculous amount of cash on a domain name. Why weren't they making headlines with how solid of a concept they had?
Why were we talking about their valuation, and how seemingly overblown it was, instead of how revolutionary their product was going to be, and how it was going to change / disrupt / whatever some existing market or industry?
Having an amazing set of people at the helm of a ship that no one seems interested in boarding doesn't do you much good.
>Why only speak to Apple? Why not Bill Gates and his foundation. Why not the Swedish government.
Couldn't agree more. The focus on this being the "Jobs Cancer" is, in my opinion, a very narrow approach.
I do hope this gets funded, however. It's completely a worthwhile cause.
I think any attempt at curing cancer is to be commended, but the fact that they open with this being "The Cancer that killed Steve Jobs" kinds of turns me off...
They name drop him at least 3 times, and it just seems like they're going off his name to help get their (completely admirable and entirely worthwhile) project funded.
The sad fact is, it will probably be more effective than any approach that doesn't leverage someones famous name.
Apple should fund it, however, because of how much of an impact Jobs had on their success and organization as a whole. Funding research to prevent other people from suffering like he did seems like a socially responsible thing to do, especially for a company with a war chest larger than some economies.
In other words, this guy wants you to submit nude photos to his nude photo collector, so he doesn't have to go looking for porno on his own.
All under the thinly veiled guise of testing out an algorithm... Brilliant
Makes sense
Do you think the server would perform more effectively if they had enabled the Cluster configuration (assuming the server has multiple cores)?
I'm fairly new to toying around with Node, so i'd be interested to know if there are fairly obvious or simple reasons for poor performance here
I found a bug
In the Chasm of Fate, after you defeat B'Joril the TimeMaster, you're supposed to get 1 piece of Titan class armor, and a random roll for 1-3 Peacock Plumes, but every time my group only gets the armor, and never any Peacock Plumes.
The devs really rushed this one out. I can't believe they expect people to pay 12 dollars a month for this.
Good luck, hope to hear of whatever product you work on
I'm wondering if it's the age of the SIM card in use...
A few years ago, I upgraded to a new android phone. A day or two later, the SIM card couldn't be detected. Try as I might, it was as though the thing wasn't plugged in.
I took the phone to the nearest carrier store, and the clerk took a look at my SIM card and told me he knew the problem.
My SIM was an older model, and wasn't designed for the heavy amount of... I'll be honest, I don't remember exactly what he said, but the gist of it was the newer phone was activating and accessing the SIM card at a much higher frequency than my old phone did. It had burned the thing out in a manner of 24-48 hours.
They loaded up a new SIM card (which actually had a slightly different look to the connector pins) and everything worked just fine. I couldn't believe it, even though it technically seems plausible.
I'm wondering if this is a similar issue - the new phones are accessing the SIM more frequently, and thus burning them out?
Just a thought
I would go so far as to say VB.NET vs VB6 is the same as comparing any flavor of C++ to C#. It doesn't really make a lot of sense, even though they share the same pedigree.
VB.NET is effectively a different language entirely. It's programming .NET with VB-like syntax, not the VB language running on .NET (in my mind, anyways)
This looks really cool...
I'd like to add that I've used various parts of the ServiceStack suite of products before and I've always found them to be very easy to use, and reliable. Also, the maintainer was always good about responding to bug requests and following up about them.
Glad to see it's still moving forward.
While I agree with the sentiment you're expressing here on some levels (people don't like it when you insult things they like, as they feel they need to defend their choice or themselves because of it), I don't think that quite applies here.
This is a case where, although the ultimate complaint of the author is the behavior of the product (which is documented, but un-intuitive in nature unless you've read up on the issue), it's the way in which he chose to frame the problem that is getting people upset.
This is a known issue, even if it seems like a completely poor design decision. The issue I think most people here are taking is that because the author did almost no research on the topic, he got himself into a problem, and is trying to blame it on Mongo.