this post was submitted on 09 Jan 2025
19 points (95.2% liked)
Django
438 readers
4 users here now
Django Project
- Django Project, the web framework for perfectionists with deadlines
- Django Code of Conduct
- Django Documentation
- Django Blog/News
- Support Django
Django Community
- Discord
- Unofficial Django Discord
- Project forum
- StackOverflow
- #django IRC Channel
- Django Users mailing list
- Django Developers mailing list
- Jazzband, a community maintaining Python projects
- Django Commons, organization dedicated to supporting the community's efforts to maintain packages
- Djangonaut Space
Django Ecosystem
- Built With Django
- Django Packages
- Django.WTF
- djangosnippets
- Awesome Django
- Django News
- Django Videos on pyvideo
- Django TV
- Upgrade Django
Jobs
Learning/Docs
- Django Project tutorial
- Django Girls Tutorial
- DjangoBook
- Classy Class-Based Views
- Classy Django REST Framework
- Classy DB
Podcasts:
Related Fediverse communities
- #django on Mastodon
- c/Python on programming.dev
- c/PostgreSQL on programming.dev
Feeds
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's a cool idea, but the way it tightly couples itself to a model, forcing db calls for something like this kinda ties your hands.
For high-content sites like blogs for example, the idea that a template tag would kick out to the db for every post on the page is too much.
Instead, it'd be nice to decouple the bot detection from the gibberish generation so you could do useful things like precache the gibberish in Redis or on your content object directly and then just do
{% if is_bot %}{{ post.gibberish }}{% else %}{{ post.content }}