An RSS-Feed basically gives an Update about new and changed
Articles. Most Webpages, Blogs and News portals offer a RSS- or Atom Feed. Add any RSS-Feed
to your BlueSoybean Account,
and we will list all the updated articles for you. You can find out about Feeds by making a search and put
the
feed URL in your Account, or if you enter a Webpage, we try to find feeds for you. Also
we give some recommendations,
when your Newsfeed is empty.
languageUse in your Browser on any Computer, Laptop or Phone
tell me more...
There is no need to download an App.
Simply Bookmark this Page, or select "Add to Desktop" from your
Browser's Menu. No matter which Device you're using.
The Basic Version of BlueSoybean is free. We don't send you spam and we never will
sell
your data.
mouseScroll and skim through a lot of Articles super fast
tell me more...
With BlueSoybean no matter to how many Feeds you are Subscribed, you can always
go through your
new Articles super fast. Just Scroll down and we mark the articles you pass as seen. When you find
an Article
you want read, just click and it will open in a new Tab. When you get back to BlueSoybean, all the
articles you
haven't seen yet, will be there for you.
You can try it right here!
keyboardKeyboard Shortcuts help you be more efficient yet.
tell me more...
When you are using a Device with keyboard, we have keyboard shortcuts for
you: k or ↑ select the previous Article. j or ↓ select the next Article. o or →open selected Article in new Tab. rreload your Newsfeed e adds the selected Article to your Recommendations Feed. t opens the Tag Area of the selected Article. s opens the sharing area of the selected Article.
You can try it right here!
labelOrganise and easily find again interesting articles using Tags.
tell me more...
By assigning Tags to Articles you find, you can organise your Articles. You
can even Turn your
tags into new RSS-Feeds other BlueSoybean- and RSS-Users can Subscribe to!
From each Articles share area, you can share Articles directly to Facebook, Whatsapp,
Xing,
Telegram and LinkedIn. By Using the "Recommend" Button, you add an Article to your
recommendation RSS-Feed, which
can be subscribed to by other BlueSoybean Users (search for an E-Mail Address when adding new Sources) and any
other RSS-Feed user.
In accordance with , the Django team
is issuing
,
, and
.
These releases addresses the security issue detailed below. We encourage all
users of Django to upgrade as soon as possible.
CVE-2024-27351: Potential regular expression denial-of-service in django.utils.text.Truncator.words()
django.utils.text.Truncator.words() method (with html=True) and
truncatewords_html template filter were subject to a potential
regular expression denial-of-service attack using a suitably crafted string
(follow up to CVE-2019-14232 and CVE-2023-43665).
Thanks Seokchan Yoon for the report.
This issue has severity "moderate" according to the Django security policy.
Affected supported versions
Django 5.0
Django 4.2
Django 3.2
Resolution
Patches to resolve the issue have been applied to the 5.0, 4.2, and 3.2
release branches. The patches may be obtained from the following changesets:
On the
On the
On the
The following releases have been issued:
Django 5.0.3 ( | )
Django 4.2.11 ( | )
Django 3.2.25 ( | )
The PGP key ID used for this release is Mariusz Felisiak: .
General notes regarding security reporting
As always, we ask that potential security issues be reported via
private email to security@djangoproject.com, and not via Django's
Trac instance or the django-developers list. Please see for further
information.
Happy birthday, Django accessibility team! 🌈
The team has been up and running for , and is now looking for new members. With a lot happening in this space, we thought we were overdue for an update on what we’re up to.
Django accessibility in 2023
We’re very happy with the work done to date. There have been a lot of efforts to improve the accessibility of core Django features such as forms, and of the administrative interface. Beyond Django core, there has also been progress on , Django packages, and community awareness via talks and events.
Django core
We made a lot of improvements this year. Django forms saw big fixes, which :
With forms being such a core feature of Django, reused across countless websites, those changes will lead to accessibility improvements across big parts of the web.
The admin interface also saw a lot of fixes and improvements:
Some of those improvements will reflect for everyone, and some will only be beneficial for users of specific assistive technologies, such as Contrast themes in Windows:
Can you spot the five issues in this screenshot? Though Contrast Themes isn’t well known, it’s a built-in feature of Windows which is essential for people with low vision. There is a lot of room for improvement to better support it in Django.
We’ve also made a lot of progress on documenting accessibility considerations, though there is still work to be done there:
FAQ:
In progress:
In progress:
And finally tooling improvements such as running is still a big topic for us, with in-progress efforts to add and .
Django website
In 2023, the website saw its first ever with a focus on the homepage, as well as a good number of accessibility improvements. Those are all very welcome iterative steps in the context of , led by 20tab.
Thank you to our website contributors Sarah Abderemane, Thibaud Colas, ontowhee, Sanyam Khurana, Hana Burtin, Paolo Melchiorre, and Tom Carrick ❤️.
Accessibility in our community
We’re elated to see accessibility being such a prominent topic in our community. In 2023, there were a lot of accessibility talks at Django events. There were accessibility contributors at the sprints for DjangoCon Europe, and DjangoCon US. The #accessibility channel on the was also very active, and we got a new .
There were a lot of accessibility-focused talks at Django events:
– DjangoCon Europe 2023, by Lauren Parsons
– Django Day CPH 2023, by Michael Nicholson
– DjangoCon US 2023, by Scott Cranfill
– DjangoCon US 2023, by Thibaud Colas
– PyOhio 2023, Dmitriy Chukhin & Janelle Bouchard
Our very own accessibility team member Sarah Abderemane was also featured on 🎉, while Tom and Thibaud signed up for .
Behind the scenes, the accessibility team also started maintaining a backlog of , and also publish their .
Django accessibility in numbers
This year, we were able to produce statistics on the accessibility of Django projects, thanks to reports from the . There is clear room for improvement, with Django websites generally scoring lower than sites built with other technologies:
There is also clear data to establish exactly which accessibility issues are common on Django websites:
We see those numbers as a good challenge for the Django community to explore ways in which the framework could be improved. There is clear room for improvement, and we have a lot of ideas on how to go about it.
Accessibility plans for 2024
There are a lot of ways in which the accessibility of Django could be improved in 2024. Here are a few ideas that have been discussed so far, where our is looking for help:
Django ecosystem accessibility audits: Testing Trac or the Forum; or popular Django packages.
Creating an official Django demo site: converting Tom’s to a ready-to-use official demo.
Stylesheets linting: To catch and fix common issues such as small font sizes or poor focus states.
Accessibility in docs: A possible big docs overhaul as a project.
New, accessible admin components: Addressing big gaps in the admin interface.
User testing: Working directly with users of assistive technologies.
An official Django accessibility statement: On the website, loud and clear.
New members
With this roadmap of improvements in mind, our accessibility team is looking for six new members in 2024. If this sounds like the type of valuable, high-purpose work you want to contribute to – reach out on the in #accessibility, or .
Thank you
Thank you to everyone who took part in making Django more accessible in 2023 and early 2024. You rock!
,
,
,
,
,
,
,
,
,
,
, , ,
,
, ,
Come say hi
In accordance with , the Django team
is issuing
,
, and
.
These releases address the security issue detailed below. We encourage all
users of Django to upgrade as soon as possible.
CVE-2024-24680: Potential denial-of-service in intcomma template filter
The intcomma template filter was subject to a potential denial-of-service
attack when used with very long strings.
Thanks Seokchan Yoon for the report.
This issue has severity "moderate" according to the Django security policy.
Affected supported versions
Django main branch
Django 5.0
Django 4.2
Django 3.2
Resolution
Patches to resolve the issue have been applied to Django's main branch and the
5.0, 4.2, and 3.2 stable branches. The patches may be obtained from the
following changesets:
On the
On the
On the
On the
The following releases have been issued:
Django 5.0.2 ( | )
Django 4.2.10 ( | )
Django 3.2.24 ( | )
The PGP key ID used for this release is Natalia Bidart:
General notes regarding security reporting
As always, we ask that potential security issues be reported via private email
to security@djangoproject.com, and not via Django's Trac instance, nor via
the Django Forum, nor via the django-developers list. Please see for further information.
After five years as part of the , Mariusz Felisiak has let us know that he will be stepping down as a Django Fellow in March 2024 to explore other things. Mariusz has made an extraordinary impact as a Django Fellow and has been a critical part of the Django community.
The Django Software Foundation and the wider Django community are grateful for his service and assistance.
The Fellowship program was started in 2014 as a way to dedicate high-quality and consistent resources to the maintenance of Django. As Django has matured, the DSF has been able to fundraise and earmark funds for this vital role. As a result, the DSF currently supports two Fellows - Mariusz Felisiak and Natalia Bidart. With the departure of Mariusz, the Django Software Foundation is announcing a call for Django Fellow applications. The new Fellow will work alongside Natalia.
The position of Fellow is focused on maintenance and community support - the work that benefits most from constant, guaranteed attention rather than volunteer-only efforts. In particular, the duties include:
Answering contributor questions on Forum and the django-developers mailing list
Helping new Django contributors land patches and learn our philosophy
Monitoring the email alias and ensuring security issues are acknowledged and responded to promptly
Fixing release blockers and helping to ensure timely releases
Fixing severe bugs and helping to backport fixes to these and security issues
Reviewing and merging pull requests
Triaging tickets on Trac
Being a Django contributor isn't a prerequisite for this position — we can help get you up to speed. We'll consider applications from anyone with a proven history of working with either the Django community or another similar open-source community. Geographical location isn't important either - we have several methods of remote communication and coordination that we can use depending on the timezone difference to the supervising members of Django.
If you're interested in applying for the position, please email us at describing why you would be a good fit along with details of your relevant experience and community involvement. Also, please include your preferred hourly rate and when you'd like to start working. Lastly, please include at least one recommendation.
Applicants will be evaluated based on the following criteria:
Details of Django and/or other open-source contributions
Details of community support in general
Understanding of the position
Clarity, formality, and precision of communications
Strength of recommendation(s)
Applications will be open until 1200 AoE, February 16, 2024, with the expectation that the successful candidate will be notified no later than March 1, 2024.