This release is a pre-release and may not be stable for production use.
BSN
Python application, running in Docker to deliver consitent, low-latency notification when new content is posted on social networks like YouTube and Twitch
Notice
This application has been placed on the back burner, I will merge depdency update PR submitted by Rennovate, but don't currently plan on adding new features/ fixing bugs.
Setup
Simplest setup is to start from compose.yml and sample.env, which should be renamed to .env
Import YouTube Channels
Follow the steps found in docs/setup.md
Environment Vairables
YOUTUBE_API_KEYS- List of YouTube Data V3 API Keys. The more keys provided, the quicker BSN can check for new uploads.APPRISE_URLS- Apprise is how we send notification, follow the documentation here on how to set up the URL(s)
1 maintainer
Metadata
1 maintainer
Release files for better-social-notifications 20261021230241.dev0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| better_social_notifications-20261021230241.dev0.tar.gz | 41.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| better_social_notifications-20261021230241.dev0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 72.8 kB
Release files / better_social_notifications-20261021230241.dev0.tar.gz
| Download URL | better_social_notifications-20261021230241.dev0.tar.gz |
|---|---|
| Size | 41.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24252cd2de32701effbdd1aa8e8b3979db5ac9c313c5c2569f2cebe58877ec93
|
|
BLAKE2b-256 checksum How to use checksums |
404909c7741d8ee94acfed75614aafffc28f4e79d29d60f489ca3d40326513ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 21, 2026.
Transparency logRelease files / better_social_notifications-20261021230241.dev0-py3-none-any.whl
| Download URL | better_social_notifications-20261021230241.dev0-py3-none-any.whl |
|---|---|
| Size | 30.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ef8dae9d6c9546382bb66b1a04163ebe3864a493bf5349f8ba3382d808de104f
|
|
BLAKE2b-256 checksum How to use checksums |
3df7ee77e528cc36182f1b7883f2b91dde3033fcfd3e56dd4ab1460b9096a0a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 21, 2026.
Transparency logSecurity for better-social-notifications 20261021230241.dev0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for better_social_notifications-20261021230241.dev0.tar.gz
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 Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
