galaxy zoo

zooniverse.org · Storage · 2 records · JSON

galaxy zoo / foldit / seti@home Storagefails: quotaemail?card?R
Zooniverse (Panoptes) Storagefails: quotaemailno cardRwrite-gated

galaxy zoo / foldit / seti@home Storage

fails: quotaemail?card?R

static.zooniverse.org/www.citizensciencealliance.org/downloa · rejected-provider · storage/galaxy-zoo-foldit-seti-home · JSON · compare

Free tier	Pure volunteer-compute. Galaxy Zoo runs inside Zooniverse (so the same 10,000-subject / review gate applies) and Foldit distributes protein-puzzle clients; neither exposes any user-addressab unit none; metered on none
Price	none stated
Per-object cap	not recorded
Retention	not recorded
Egress	not recorded
Identity	email (placeholder) not published
Binding	none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
Interface	unknown
Tooling	not recorded
Composes with	not recorded
Reliability	Pure volunteer-compute. Galaxy Zoo runs inside Zooniverse (so the same 10,000-subject / review gate applies) and Foldit distributes protein-puzzle clients; neither exposes any user-addressab
Notes	Pure volunteer-compute. Galaxy Zoo runs inside Zooniverse (so the same 10,000-subject / review gate applies) and Foldit distributes protein-puzzle clients; neither exposes any user-addressab
Evidence rung	reported
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (2)

date	source	what it proved
2026-10-21	static.zooniverse.org/www.citizensciencealliance.org/downloa	Pure volunteer-compute. Galaxy Zoo runs inside Zooniverse (so the same 10,000-subject / review gate applies) and Foldit distributes protein-puzzle clients; neither exposes any user-addressab
2026-10-21	help.zooniverse.org/getting-started/lab-policies/	cited as the basis of the rejection: Pure volunteer-compute. Galaxy Zoo runs inside Zooniverse (so the same 10,000-subject / review gate applies) and Foldit distributes protein-puzzle clients; neither exposes any user-addressab

More fields (1)

{
 "dead_end": {
  "failure_class": "not-storage",
  "why": "Pure volunteer-compute. Galaxy Zoo runs inside Zooniverse (so the same 10,000-subject / review gate applies) and Foldit distributes protein-puzzle clients; neither exposes any user-addressab",
  "retry_when": "never; it is not storage",
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (14)

$.chaining not-recorded
$.confidence_note withheld
$.egress.terms not-recorded
$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.interface interface-unknown
$.interface_detail withheld
$.limits_note process
$.per_object_cap.notes not-recorded
$.per_object_cap.stated not-recorded
$.retention.notes process
$.retention.stated not-recorded
$.tooling not-recorded

Zooniverse (Panoptes) Storage

fails: quotaemailno cardRwrite-gated

www.zooniverse.org · citizen-science classification platform · storage/zooniverse · JSON · compare

Free tier	Stores contributor classifications, not contributor uploads — and the upload side is capped at 10,000 subjects per user. Zooniverse Help, Lab Policies, verbatim: 'there is a limit of 10,000 subject uploads per user. Please contact us if you'd like to upload more.' unit mixed; metered on stored-bytes
Price	none stated
Per-object cap	not stated
Retention	not stated
Egress	free read, but only per-subject image URLs — no bulk export endpoint without project-owner credentials
Identity	email email for a volunteer account ('Only your name and email are captured'), but publishing a project is `write-gated` — internal review + beta test + launch scheduling, typically weeks.
Limits	write-gated review and a one-week beta before launch source 10,000 subjects/user; every project passes a two-stage review and a one-week beta before launch; media must be licensed and rights-clear
Binding	write-gated the write is a queue with a person or a rule in it, so the upload rate is set by somebody else
Interface	cli Panoptes API (api.zooniverse.org); project builder; subject sets
Tooling	panoptes-client (Ruby/JS); subject uploader UI; no bulk CLI
Composes with	None. Each project's subjects live in a project-scoped S3 bucket; the data exports are CSV manifests, not a filesystem.
Reliability	Dead as a storage target for a user. It is a volunteer-compute platform: the storage is incidental to the classification task and cannot be addressed as a bucket.
Notes	Stores contributor classifications, not contributor uploads — and the upload side is capped at 10,000 subjects per user. Zooniverse Help, Lab Policies, verbatim: 'there is a limit of 10,000 subject uploads per user. Please contact us if you'd like to upload more.'
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (4)

date	source	what it proved
2026-10-21	help.zooniverse.org/getting-started/lab-policies/	'there is a limit of 10,000 subject uploads per user'; two-stage review before launch
2026-10-21	zooniverse.freshdesk.com/support/solutions/articles/44001770	'Only your name and email are captured'
2026-10-21	developer.zooniverse.org/en/latest/science/subject_uploads.h	external subjects count against 'the upload limit for that [project]' (host DNS now dead: 530/dns-failure via the fetch broker)
2026-10-21	www.zooniverse.org/about/faq	'Your classifications are stored in the Zooniverse's secure online database'

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "Stores contributor *classifications*, not contributor *uploads* — and the upload side is capped at 10,000 subjects per user. Zooniverse Help, Lab Policies, verbatim: 'there is a limit of 10,000 subject uploads per user. Please contact us if you'd like to upload more.'",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (6)

$.extras.dead_end.retry_when process
$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted