diff options
Diffstat (limited to 'packages/meshbay-common/src/meshbay_common/__init__.py')
| -rw-r--r-- | packages/meshbay-common/src/meshbay_common/__init__.py | 18 |
1 files changed, 17 insertions, 1 deletions
diff --git a/packages/meshbay-common/src/meshbay_common/__init__.py b/packages/meshbay-common/src/meshbay_common/__init__.py index 027c38a..80e6d92 100644 --- a/packages/meshbay-common/src/meshbay_common/__init__.py +++ b/packages/meshbay-common/src/meshbay_common/__init__.py @@ -165,5 +165,21 @@ __version__ = "0.14.0" # `client.minimum` and the client checks it *before* connecting, and says "this # version can no longer connect" rather than showing a handshake refusal nobody # can act on. -MNP_VERSION = "3.0" +# +# **3.1 (2026-09-16): per-account blobs the node holds and cannot read.** +# +# `user_blob_store` / `_fetch` / `_list` / `_delete`, modelled on +# `keypair_bundle_*` in every respect including that the node stores and returns +# an opaque byte string. Playlists are the first payload (docs/playlists.md +# §8.1); `kind` is validated against a pattern rather than an enum, so the table +# does not become an arbitrary key/value store for whatever a client feels like +# writing. +# +# **Additive, and MINOR because nothing is required.** A 3.0 peer never sends +# any of these and loses nothing it had; a 3.0 *node* answers `unknown message +# type`, and a client that cannot store a playlist on one node stores it on the +# next one it reaches and keeps its own copy meanwhile (§6.4). `MNP_MIN_SUPPORTED` +# does not move. That is the difference from 3.0, where the requirement — not the +# messages — is what made it MAJOR. +MNP_VERSION = "3.1" MHP_VERSION = "0.1" |