timvisee Send instances

github.com · Storage · 1 record · JSON

timvisee Send instances (Firefox Send forks) Storage

caveatemail?card?Rper-object-cap

github.com/timvisee/send-instances · anon-dump · storage/timvisee-send-instances · JSON · compare

Free tier	Per-instance. Public table (read live) includes send.cyberjake.xyz at 10 GiB / 30 days / 100 downloads and send.adminforge.de at 8 GiB / 7 days / 1,000 downloads. The listed send.skylerszijjarto.com at 250 GiB / 7 days / 10,000 downloads and send.hostnetwork.xyz at 2.5 GiB / 999,999 downloads are the two outliers. unit GiB; metered on unstated
Price	none stated
Per-object cap	per-object-cap: the table's Size limit column (2.5 GiB (2684354560 bytes)
Retention	Retention: the Time limit column (3 to 30 days), MAX_EXPIRE_SECONDS on the server (30 days)
Egress	unmetered; direct file URLs on the instance host, no egress pricing.
Identity	email (placeholder) not published
Limits	retention-clamped Retention: the Time limit column (3 to 30 days source per-object-cap per-object-cap: the table's Size limit column (2.5 GiB source per-object-cap: the table's Size limit column (2.5 GiB to 250 GiB). Retention: the Time limit column (3 to 30 days), MAX_EXPIRE_SECONDS on the server. pull-count: the DL limit column — adminforge allows 1,000, hostnetwork 999,999, but most sit at 10-100. The pull cap, not bytes, is the real bind on the E8 workload.
Binding	per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota
Interface	rest, cli rest
Tooling	ffsend (github.com/timvisee/ffsend) — real CLI with --host URL. Server is a self-hostable Rust binary, so the config (MAX_FILE_SIZE, MAX_EXPIRE_SECONDS) is public per instance.
Composes with	15+ public instances in the table, each an independent operator with its own quota => shard across instances rather than accounts. Since the server is self-hostable, the ceiling on an instance you run is only your own disk.
Reliability	Instance-level liveness is genuinely poor: of the three I probed, send.cyberjake.xyz served 200/6176 bytes, while send.skylerszijjarto.com (the 250 GiB one) and send.adminforge.de both returned Cloudflare 530/525 — the two biggest quotas in the table are the ones that are down. All files are E2E encrypted client-side and deleted on expiry; no originals re-encode.
Notes	Per-instance. Public table (read live) includes send.cyberjake.xyz at 10 GiB / 30 days / 100 downloads and send.adminforge.de at 8 GiB / 7 days / 1,000 downloads. The listed send.skylerszijjarto.com at 250 GiB / 7 days / 10,000 downloads and send.hostnetwork.xyz at 2.5 GiB / 999,999 downloads are the two outliers.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers	`$.limits[1].value` limit:per-object-cap 2.5 GiB

Evidence (3)

date	source	what it proved
2026-10-21	github.com/timvisee/send-instances	not published
2026-10-21	send.cyberjake.xyz/	probe: GET -> 200 6176 bytes, page says 'send up to 10GB'
2026-10-21	send.skylerszijjarto.com/	probe: GET -> 530 465; GET https://send.adminforge.de/ -> 525 (both dead at probe time)

Unknown or withheld values (6)

$.evidence[0].proved withheld
$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.per_object_cap.notes not-extracted
$.retention.notes not-extracted

Built from commit 872967ae41, data as of 2026-10-27. Every value links to its source; freshness badges are computed in your browser. How to read this.