history4feed
Before you begin...
We use history4feed in the web version of Obstracts which includes many additional features over those in this codebase. You can find out more about the web version here.
Overview
It is common for feeds (RSS or XML) to only include a limited number of posts. I generally see the latest 3 - 5 posts of a blog in a feed. For blogs that have been operating for years, this means potentially thousands of posts are missed.
There is no way to page through historic articles using an RSS or ATOM feed (they were not designed for this), which means the first poll of the feed will only contain the limited number of articles in the feed. This limit is defined by the blog owner.
history4feed can be used to create a complete history for a blog and output it as an RSS feed.
history4feed offers an API interface that;
- takes an RSS / ATOM feed URL
- downloads a Wayback Machine archive for the feed
- identified all unique blog posts in the historic feeds downloaded
- downloads a HTML version of the article content on each page
- stores the post record in the databases
- exposes the posts as JSON or XML RSS
Install
Download and configure
# clone the latest code
git clone https://github.com/muchdogesec/history4feed
Configuration options
history4feed has various settings that are defined in an .env file.
To create a template for the file:
cp .env.example .env
To see more information about how to set the variables, and what they do, read the .env.markdown file.
Build the Docker Image
sudo docker compose build
Start the server
sudo docker compose up
Access the server
The webserver (Django) should now be running on: http://127.0.0.1:8002/
You can access the Swagger UI for the API in a browser at: http://127.0.0.1:8002/api/schema/swagger-ui/
Useful supporting tools
- Full Text, Full Archive RSS Feeds for any Blog
- An up-to-date list of threat intel blogs that post cyber threat intelligence research
- Donate to the Wayback Machine
Support
Minimal support provided via the DOGESEC community.
License
1 maintainer
Metadata
1 maintainer
Release files for history4feed 1.2.13
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| history4feed-1.2.13.tar.gz | 1.4 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| history4feed-1.2.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 MB
Release files / history4feed-1.2.13.tar.gz
| Download URL | history4feed-1.2.13.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4212f4585eaff240310024aa4184cecb67ee86bb9a4c27e26f54668e866eeed5
|
|
BLAKE2b-256 checksum How to use checksums |
df09dfb367acb7588abeefd6a32ff7604de47d22fac647a0b0c38b4647f1baf2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 25, 2026.
Transparency logRelease files / history4feed-1.2.13-py3-none-any.whl
| Download URL | history4feed-1.2.13-py3-none-any.whl |
|---|---|
| Size | 52.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7d8e449efbd5155fb8a6ea761614c51a07c43e84412e3ddf3dae0ad488249172
|
|
BLAKE2b-256 checksum How to use checksums |
b277883f869b05fb3b974fa80abd4592b6ed262fd4bde7eb839e3e4b68b88c17
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 25, 2026.
Transparency log
