On 20 Dec 2010, at 06:40, Russell Keith-Magee wrote:
>
> No, there aren't any completely reliable clues -- and in my opinion,
> that's a good thing.
>
> Providing an easy way to identify a Django site serves no purpose
> other than inflating project ego. On the other hand, if I am a black
> hat h
On Monday, December 20, 2010, Yo-Yo Ma wrote:
> UPDATE:
>
> The BuiltWith team has removed Django because there aren't enough
> clues to accurately detect Django in some circumstances, and they
> didn't want to give bad data. Instead, they've added
> http://trends.builtwith.com/cms/Django-CSRF (wh
On Sun, Dec 19, 2010 at 2:55 PM, Yo-Yo Ma wrote:
>
> From the core team, are there any reliable clues to detect Django that
> are more consistent than naming conventions? CSRF doesn't
> always apply. This tool can also be helpful for those contributors who
> run Django showcase sites, etc.
Many
UPDATE:
The BuiltWith team has removed Django because there aren't enough
clues to accurately detect Django in some circumstances, and they
didn't want to give bad data. Instead, they've added
http://trends.builtwith.com/cms/Django-CSRF (which basically is
telling you a site uses Django). They're
I recently worked with BuiltWith to provide a list of methods for
detecting whether a site was using Django, and their team implemented
them. You can now check stats for Django usage at
http://trends.builtwith.com/framework/Django (sparse for now), and if
you get the Firefox plug-in, you can check
