dacort

12 ms·

91.
by dacort 16y ago
http://tweetreach.com will do this. The basic/free version only looks at the 50 most recent tweets, but they gasp charge for more. Amazing...a Twitter app that charges! Novel! ;)
92.
by dacort 16y ago
Wonder how quickly somebody is going to create one about the downfall of the downfall meme...
93.
by dacort 17y ago
Hm, another passing mention of their distributed graph database, FlockDB.
94.
by dacort 17y ago
+1 for the Batman rollerblader. But that's about it. Use what works, some apps do justify nosql off the bat. Many don't.
95.
How to find your seed investor: It's all about the relationships(techflash.com)
1 points by dacort 17y ago|0 comments
96.
The 5 Stages of Being a Twitter Dev(untitledstartup.com)
5 points by dacort 17y ago|0 comments
97.
by dacort 17y ago
This isn't a generic solution, but we (my co-founder and I) actually put something together specifically for us. http://untitledstartup.com/backstage/ - right now it suffers from an abundance of Twitter ideas, primarily because I'm fairly
98.
by dacort 17y ago
I would wager to say a large majority of .asp sites out there are vulnerable to these types of issues. Most were coded before common sanitization and security practices were observed during dev, not to mention built in to frameworks.
99.
by dacort 17y ago
From Tony Wright, a YC alum: "Probably over 100 people came to the YC meetup in Seattle. Crazy success. Note to self: Hackers suck at RSVP'ing." http://twitter.com/webwright/status/9666575618 I couldn't make it, unfortunately.
100.
by dacort 17y ago
I've run TweetStats on EC2 for the past year using the great scalr.net to provision new instances. It's expensive as heck (the smallest instance scalr allows is an EC2 large), but it works great. Scalr monitors one of several stats you can
101.
by dacort 17y ago
Backing out the latest changes we spent the week building because it "wasn't right".
102.
by dacort 17y ago
OK. So you use encryption. +1 Have you had a vulnerability assessment done? Do you protect against SQL Injection? Do you protect against Cross-Site Scripting? How about Cross-Site Request Forgery? What preventative measures have you taken t
103.
Ask HN: Startup Data Security Survey
3 points by dacort 17y ago|1 comments
104.
by dacort 17y ago
I found their documentation absolutely horrendous. Try googling for "recurring paypal" and you get a page that links to a (stated) 682K PDF published in 2006 that in actuality is only 2 pages and includes a link to yet another 300 page PDF.
105.
by dacort 17y ago
We posted our experiences of three of these here - http://www.untitledstartup.com/2010/02/accepting-payments-on... We ultimately chose to go with recurly, but are going to look at chargify again once they stabilize a little bit. Recurly i
106.
by dacort 17y ago
Short answer - They should be listed on the service providers list if you are using them in that capacity and you want to be fully compliant as well. Longer answer (disclaimer: I'm a former PCI QSA). You can, of course, do whatever you want
107.
by dacort 17y ago
Really glad I clicked this link and the first image was of a man doing a strip-tease. I should know better. ;)
108.
by dacort 17y ago
Wow - love the concept and vision here. Were I such a person, I might dub this payments 2.0. This image on their home page gave me chills, though. http://a1.sqimg.com/static/6c1cc3c1ad109e13d0be182c75c470762... But that's likely only beca
109.
by dacort 17y ago
Well every provider has different access methods, of course. Google's is probably the easiest since you can easily just supply a username/password (note: I believe they support OAuth as well, which would be the preferred means of accessing
110.
by dacort 17y ago
Or any of the numerous sites that email you your password when you sign up or do a password "reset". Head -> Desk
111.
by dacort 17y ago
Would be interesting to hear what the trendsmap.com folks think of this development. Ah, the risks of developing on top of Twitter.
112.
by dacort 17y ago
"Let me reiterate that all three of the above uses put me in direct violation of my corporate IT policies." Not to mention several state and federal regulations depending on the data being uploaded...
113.
by dacort 17y ago
Really looking forward to trying this - I've given backgroundrb, BJ, DJ, and workling a go and there's always been something that's frustrated me. It's amazing the number of different things I'm considering using Redis for as well.
114.
by dacort 17y ago
It'd be a little easier to do this by requesting followers/ids ( http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-follow... ) if you have over 100 followers. That'll give you 5,000 id's at a shot and then you can just do a simple diff
115.
by dacort 17y ago
I was under the impression it showed your gateway location as well. I started looking into it at one point and at least a simple whois lookup on the IP didn't reveal much information. Granted, it's easy enough to lookup wifi AP's, but one h
116.
by dacort 17y ago
And it's that former situation where I've seen the performance issues mentioned.
117.
by dacort 17y ago
Definitely agreed. Some of the comments I've seen from the neo4j author definitely lend to the fact that for most cases, the performance of neo4j itself won't be a problem at all.
118.
by dacort 17y ago
Great news for Neo. Most of the comments I see about neo4j are along the lines of "great technology, but doesn't quite cut it from a performance perspective".
119.
by dacort 17y ago
It's not the people saying "hotdog", it's the people saying "Oscar Mayer hotdog". Brands are excited about real-time search because it's the first time that nonsensical chatter has actually propagated beyond people's lips on to the Internet