gdeglin

46 ms·

451.
Usertesting.com results on Facebook's usability(usertesting.com)
22 points by gdeglin 15y ago|7 comments
452.
Yahoo's assumptions in 2006 about Facebook's future(techcrunch.com)
64 points by gdeglin 15y ago|34 comments
453.
by gdeglin 16y ago
Sorry. It got banned from platform for a few reasons including tagging photos that didn't have people in them. (Similar to the cartoons that people upload and tag their friends as characters). In general the biggest trait is that the app is
454.
by gdeglin 16y ago
I recently built a Facebook application that approached the same kind of growth. Sites like this typically see eCPM between $0.10 and $0.30 for advertising. So you're looking at around $30/day revenue right now. Consider switching to EC2. T
455.
by gdeglin 16y ago
There is also a paper published on this technique here: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.153....
456.
Blueprint - Technology for preventing XSS attacks(sisl.rites.uic.edu)
2 points by gdeglin 16y ago|1 comments
457.
by gdeglin 16y ago
The risk of sending the UID of the user to ad networks is that it's possible an unscrupulous ad network will store and use or sell the data. However, if an ad network wanted to get the UIDs they can still easily get them. Just about all Fac
458.
Security flaws in Facebook's Instant Personalization program(gdeglin.blogspot.com)
31 points by gdeglin 16y ago|5 comments
459.
by gdeglin 16y ago
Thanks! If anyone sees another FB, twitter, or Google worm spreading send it over to me and I'll be happy to see how that one works too.
460.
Reverse engineering the latest Facebook worm(gdeglin.blogspot.com)
12 points by gdeglin 16y ago|2 comments
461.
by gdeglin 16y ago
This is a good overview: https://developer.mozilla.org/en/document.domain
462.
by gdeglin 16y ago
This is my first blog post about web security, and hopefully the first of many. I'd love to hear feedback and I'm happy to answer questions. One of the concerns I had with this post was that it is highly technical, but I feel the issue is e
463.
Careful when hosting 3rd party apps on subdomains, or how I hacked Facebook(gdeglin.blogspot.com)
77 points by gdeglin 16y ago|12 comments
464.
by gdeglin 16y ago
If anyone is curious, these security holes were found in dynamically generated javascript that included a GET parameter that was neither encoded nor run through magic_quotes. They were easy to find to the point where an automated scanning t
465.
by gdeglin 16y ago
It's good to see the poor stability of the Facebook API starting to get some more public attention. Much of the downtime that top Facebook apps have is due to the platform itself and developers are often powerless to do anything about it. I
466.
by gdeglin 17y ago
This is a great change. We almost never use .find() anymore in our rails 2.3 projects and everything uses named_scope() or scoped() (which return relations). This change will discourage really bad practices that I've seen in a lot of rails