Re: Rate limiting failed login attempts/failed password changes

2017-11-15 Thread Bernhard Posselt
telimit is very good: https://django-ratelimit.readthedocs.io/en/latest/security.html (thanks to James Socol and contributors!) On 15 November 2017 at 11:07, Bernhard Posselt <mailto:nukeawh...@gmail.com>> wrote: Hi guys, We've received a report from hackerone.com &

Re: Rate limiting failed login attempts/failed password changes

2017-11-15 Thread Bernhard Posselt
erent environments django gets deployed under. The summary in django-ratelimit is very good: https://django-ratelimit.readthedocs.io/en/latest/security.html (thanks to James Socol and contributors!) On 15 November 2017 at 11:07, Bernhard Posselt <mailto:nukeawh...@gmail.com>> wrote: Hi

Rate limiting failed login attempts/failed password changes

2017-11-15 Thread Bernhard Posselt
ts on this? regards Bernhard Posselt -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-deve

Re: Why doesn't the framework provide support for translated database content?

2017-06-13 Thread Bernhard Posselt
The question is how we guess that it fits 80% of all use cases :) IMHO 80% are covered with the two approaches that I listed in the first mail. I mean you reach the limits of the ORM pretty quickly as well but you can always drop down to raw Sql and circumvent the built in API restrictions On 06

Re: Why doesn't the framework provide support for translated database content?

2017-06-13 Thread Bernhard Posselt
Why not build in the most common approach while still allowing people to override it like they do know? They could simply swap out the default manager right? On 06/13/2017 06:54 PM, James Bennett wrote: > Because even if you collapse the number of approaches to just two general > options, there's

Why doesn't the framework provide support for translated database content?

2017-06-13 Thread Bernhard Posselt
Hi guys, I'm running a "hobby" website with translations for roughly 83 languages and I've taken a thorough look at the available options (as in: Django apps): * django-modeltranslation: probably a bad idea to create 83 columns for each translated string * django-hvad: never got this to work *

Re: Django versioning and breaking changes policy

2017-04-04 Thread Bernhard Posselt
Oh wow, haven't seen that yet, thank you :) Just make sure to follow the semver spec closely if you transition to semver, because it can cause issues for parsers. Also the spec is more restrictive than you'd think with regards to syntax (source: working with semver in my current Django project)

Re: Django versioning and breaking changes policy

2017-04-04 Thread Bernhard Posselt
jango over the past few releases that you felt > were too significant or costly to address? > > Tobias > > On Tue, Apr 4, 2017 at 3:15 PM, Bernhard Posselt > wrote: > >> Hi guys :) >> >> I'm maintaining a Django project that uses 6 apps: >> &

Django versioning and breaking changes policy

2017-04-04 Thread Bernhard Posselt
Hi guys :) I'm maintaining a Django project that uses 6 apps: * djangorestframework, * django-parler (database translations), * django-allauth (openid & richer account settings) * django-recaptcha2 (simple recaptcha widget) * django-csp * django-cors-middleware Each time a new Django versio