| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
| |
Add a periodic recovery sweep for Webmentions left in received or
verifying states after worker crashes, lost queue entries, or
interrupted processing.
Use atomic lease-style updates so stale workers cannot overwrite newer
results, and index verification state for efficient recovery scans.
|
| |
|
|
|
|
|
|
|
|
| |
Persist retry state per source revision so temporary delivery failures
survive worker restarts and duplicate queued tasks cannot bypass the
retry schedule.
Use capped exponential backoff, stop after a configurable attempt limit,
and reset the retry budget when a source changes or an admin resends
manually.
|
| |
|
|
|
|
|
|
|
|
|
| |
Fail production startup when required configuration is missing,
normalize allowed hostnames before validation, and move shared request
limits into the default configuration so production does not depend on
testing-only values.
Set secure session cookie defaults while preserving explicit overrides
and document the new rate-limit and notification settings in the example
config.
|
| |
|
|
|
|
|
|
|
|
| |
Reduce login abuse and username enumeration by rate limiting POST
attempts and always performing password verification, even for unknown
users.
Require authenticated, CSRF-protected POST requests for logout so
sessions cannot be terminated through cross-site or accidental GET
requests.
|
| |
|
|
|
|
|
|
|
| |
Batch verified Webmention notifications into a scheduled digest so
bursts of incoming mentions do not generate a separate email for every
verification.
Track which mentions have already been reported and leave them pending
when SMTP delivery fails so a later digest can retry safely.
|
| |
|
|
|
|
|
|
|
|
| |
Protect the public endpoint from abusive request floods and repeated
duplicate submissions that would otherwise trigger unnecessary
verification work.
Add per-client and global limits, require shared limiter storage in
production, and only reverify existing Webmentions after a configurable
cooldown.
|
| | |
|
| |
|
|
|
| |
Restore the SOURCE_BASE_URL setting so scanner configuration uses the
key expected throughout the application.
|
| |
|
|
|
|
| |
Remove the WEBMENTIONS_SSG prefix from application-specific
configuration settings and update validators, tasks, and tests to use
the shorter names.
|
| |
|
|
|
|
|
|
|
| |
Send an email after a newly received Webmention is successfully
verified, with SMTP delivery configurable through Flask-Mail.
Avoid notifications for resubmissions and manual reverification, and
keep the persisted verification result unchanged if notification
enqueueing fails.
|
| |
|
|
|
|
|
|
| |
Add SPDX copyright and license headers to source, test, migration,
template, and static files throughout the project.
Include the maintainer email in copyright notices and fill in the BSD
license copyright holder.
|
| |
|
|
|
|
|
|
|
|
|
| |
Scan generated h-entry documents for Webmention targets and track source
revisions and delivery state in the database.
Discover target endpoints, send Webmentions asynchronously, and reconcile
updated, removed, restored, and deleted sources across scans.
Add authenticated views for inspecting sent Webmentions and make the scanner
schedule configurable.
|
|
|
Add the Flask application setup, database models and migrations,
authentication, and configuration for development and testing.
Implement asynchronous Webmention verification with Huey, including HTML
and plain-text source validation, retries, status tracking, and size
limits.
Add status, login, and paginated received-Webmention views together with
comprehensive tests for forms, views, and receiver tasks.
|