com.pipobscure.bundle.listing

A bundle the repository's owner makes available under a name: the record key, which is also what it installs as. It is an app, or a plugin for one, as its subject says. The record says only where the bundle is fetched from — a url, or a domain whose 'nzip:' TXT record names one, exactly one of the two. It vouches for nothing, and whatever is fetched is verified like any other download.

Repository @pipobscure.com did:plc:rwypz6edxmzyhob2k3rsl2fw namespace authority
Details · record, key any
Kindrecord
Record keyany
Authoritybundle.pipobscure.com
Indexed

Record

record · key any

Properties

createdAt

requiredstring · datetime

When the bundle was first listed, by the publisher's clock.

What the bundle is, in a sentence or two.

  • maxLength: 3000
  • maxGraphemes: 300

domain

string

A domain whose 'nzip:<url>' TXT record says where the bundle is fetched from, so the publisher manages the URL in DNS: lowercase, no trailing dot. Exactly one of url and domain.

  • maxLength: 253

subject

requiredstring · uri

For an app: 'sha256:aa2e2af5c7e057ae771b9c28543044546b9107216418fbb511d1353fd55c1169', the sha256 of this lexicon's NSID, the same in every app's listing, so that a backlink index can enumerate every app listed on the network. For a plugin: the at:// address of the listing of the app it is for, so that the backlink index finds an app's plugins, and never lists them among apps.

  • maxLength: 2048

title

string

A display name; the record key stands in when it is absent.

  • maxLength: 640
  • maxGraphemes: 64

url

string · uri

Where the bundle is fetched from: an https URL, expected to stay the same across releases. Exactly one of url and domain.

  • maxLength: 2048

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • A set of listed bundles the repository's owner makes available to install together, under a name: the record key. Installing the suite installs each member as it would be installed by itself, and an update follows the suite as members are added and taken out. The suite vouches for none of them: each member is reviewed and verified on its own. What it can do is set a minimum — a signer and attesters a member must carry — below which that member is refused.

  • com.emdashcms.experimental.package.release

    record not from the namespace authority

    Plugin package release record. EXPERIMENTAL: this NSID is part of the experimental phase of the EmDash plugin registry. The stable namespace target is com.emdashcms.package.release.

  • A statement by the repository's owner about a bundle — that they vouch for it, or that it is bad — identified by its whole-file hash — the hash a bundle signature covers — or about a suite, identified by the hash of what it says (see com.pipobscure.bundle.suite). The record key is that hash in lowercase hex, so there is at most one attestation per account per bundle or suite, and a verifier knows which record to ask for. A good attestation of a suite counts for each bundle installed from it; a b