fshy

fshy / Storage

misskey.io registration

misskey.io · Storage · 2 records · JSON

misskey.io registration (as opposed to its capacity) Storage

fails: identityemail?card?R

misskey.io/api/meta · rejected-provider · storage/misskey-io-registration · JSON · compare

Free tierIts numbers are good (10 GiB, 500 MiB objects) but signup is closed indefinitely — the operator states it cannot add server capacity because their cloud provider was breached. Capacity witho
unit none; metered on none
Pricenone stated
Per-object capnot recorded
Retentionnot recorded
Egressnot recorded
Identityemail (placeholder) not published
Bindingnone the quota is real and unreachable: identity is the binding constraint, and it is not one of the six limits kinds
Interfaceunknown
Toolingnot recorded
Composes withnot recorded
ReliabilityIts numbers are good (10 GiB, 500 MiB objects) but signup is closed indefinitely — the operator states it cannot add server capacity because their cloud provider was breached. Capacity witho
NotesIts numbers are good (10 GiB, 500 MiB objects) but signup is closed indefinitely — the operator states it cannot add server capacity because their cloud provider was breached. Capacity witho
Evidence rungreported
Checked2026-10-21 (inherited); stale on 2026-11-04
Evidence (1)
datesourcewhat it proved
2026-10-21misskey.io/api/metaIts numbers are good (10 GiB, 500 MiB objects) but signup is closed indefinitely — the operator states it cannot add server capacity because their cloud provider was breached. Capacity witho
More fields (1)
{
 "dead_end": {
  "failure_class": "identity",
  "why": "Its numbers are good (10 GiB, 500 MiB objects) but signup is closed indefinitely — the operator states it cannot add server capacity because their cloud provider was breached. Capacity witho",
  "retry_when": "if the registration gate opens to a foreign individual",
  "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

misskey.io — 10 GiB drive, 500 MiB per object (largest per-object cap in the family) Storage

fails: quotainstitutionno cardRper-object-cap

misskey.io · fediverse-misskey · storage/misskey-io-10-gib-drive-500-mib-per-object · JSON · compare

Free tier10240 MB = 10 GiB per user; maxFileSize 524288000 bytes = 500 MiB per object.
unit GiB; metered on unstated
Pricenone stated
Per-object cap500 MiB per object (524288000 bytes)
Retentionnot stated
EgressFree, served from misskey.io's own CDN (Cloudflare + object storage). No egress charge.
Identityinstitution derived from the record's prose, not from an identity field, and no signup was executed: key instance in existence (~600k users) so the best-tested API, BUT registration is CLOSED: the /api/meta description states in Japanese that new signups are suspended because the cl
Limits
  • per-object-cap 500 MiB per object source
per-object-cap 500 MiB; per-user 10 GiB; request-rate is the real constraint here (huge shared IP pool, aggressive per-IP limits).
Bindingper-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
Interfacerest rest
ToolingMisskey API / MiAuth.
Composes withThe largest Misskey instance in existence (~600k users) so the best-tested API, BUT registration is CLOSED: the /api/meta description states in Japanese that new signups are suspended because the cloud provider for their servers suffered unauthorised access and they cannot add capacity. Only useful with existing accounts or an invite if the operator reopens.
ReliabilityRegistration closed as of this probe; operator explicitly cannot expand capacity. The 500 MiB per-object number is still the useful data point: it proves the family's per-object ceiling.
Notes10240 MB = 10 GiB per user; maxFileSize 524288000 bytes = 500 MiB per object.
Evidence rungreported One page read moves it to documented.
Checked2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers
  • $.limits[0].value limit:per-object-cap 500.0 MiB
Evidence (2)
datesourcewhat it proved
2026-10-21misskey.io/api/metaprobe: POST -> 200, policies.driveCapacityMb=10240, maxFileSize=524288000, disableRegistration=true
2026-10-21withheldprobe: description field (ja) — '現在、利用しているクラウド事業者への不正アクセスによりサーバーの増設が出来ないため新規登録を停止しています'
More fields (2)
{
 "verdict_note": "PLAN.md §3.2 rules fails-quota by default, because no row in this set clears 500 GiB per unit for a user.",
 "dead_end": {
  "failure_class": "quota",
  "why": "10240 MB = 10 GiB per user; maxFileSize 524288000 bytes = 500 MiB per object.",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}
Unknown or withheld values (6)
  • $.evidence[1].url private-url
  • $.extras.dead_end.retry_when process
  • $.free_tier.notes process
  • $.per_object_cap.notes not-extracted
  • $.retention.notes not-extracted
  • $.retention.stated not-extracted