Arch manual pages

PBPST_DB(5) pbpst PBPST_DB(5)


pbpst_db - The local, human-readable database and config for pbpst


The local, human-readable (JSON) database and configuration for pbpst.
This database automatically tracks what pastes a user makes to pb deployments. As a result, management of what pastes a user makes should be dramatically simplified. For example, since it will record the UUID for the user, the need to memorize, copy down or otherwise manually record the authentication information is no longer necessary.


The top-level of the database contains a solitary object.
A string equal to the URL of the provider that pbpst should use by-default
An object containing objects (one for each pb provider that has been used). The key for one of these objects is the URL of the provider of the pastes it contains. It may be quite common for there to only be one object beneath: the provider specified by default_provider.
An object containing paste objects. The key for one of these paste objects is the UUID associated with that paste. This level of abstraction is included mostly so that a user can simply use a single database to interact with multiple pb providers.
A paste object.
A string equal to the long identifier associated with the paste. This is a left-zero-padded (to 21 bytes) base64 encoding of the sha1 of the paste contents.
An arbitrary string which may be specified by the user upon creation/updating of the associated paste. If the user choose not to specify a string for a paste, this field defaults to the basename of the file ("-" for stdin).
A string equal to the vanity label associated with the paste (if one was given). If the paste does not have a vanity label, this will be set to null.
A string equivalent to the UTC seconds-since-the-epoch of when the paste will be automatically culled. JS(ON) does not actually support integers, and this future-proofs against the 2038 problem. Note: to avoid the necessity of parsing pb's response, we calculate the time ourself which means that it might not be exact.


    "default_provider": "",
    "pastes": {
        "": {
            "fa3423b6-2c29-4758-a707-bf3f972b93c9": {
                "long": "AFKg4i_J0ssH6sJKdsYCA8WuR542",
                "msg": "-",
                "label": "~random_junk",
                "sunset": "1440960243"

The above snippet is an example database that keeps the default provider and is tracking one paste (which happens to be on that default provider). The msg field is "-" because this paste was created by piping through stdin.


Report bugs for pbpst to


See the documentation on pb, a lightweight pastebin at
19 Feb 2018