A client-neutral convention for embedding a small, versioned, human-readable metadata record inside an F-List profile description. Chat clients that understand the record can offer features the site does not: portrait overrides, name colors, accurate local time. Clients and browsers that do not understand it render nothing.
[i=fpm1://avatar=static.f-list.net/images/charimage/44262665.png;namecolor=cyan;timezone=America/New_York][/i]
Status: draft, see fpm-standard.md.
| File | What it is |
|---|---|
fpm-standard.md |
The specification. Sections 3 and 4 are normative. |
KEYS.md |
The key registry. Authoritative for key semantics. |
keys.json |
Machine-readable mirror of the registry, for tooling. |
Update keys.json in the same change that edits KEYS.md; the JSON is a mirror
of the registry. A spec version bump touches three files: the fpm-standard.md
title, the KEYS.md title, and keys.json specVersion.
The Horizon organization hosts the specification and registry. This does not
delegate ownership. The wire format carries no client branding, a registry
decision that affects another client's published extension requires that
client's agreement, and clients that ship FPM support are offered maintainer
access. New keys land by pull request against KEYS.md; see "Proposing a key"
there. Section 3.6 of the specification is the full statement.
Please reach out to dev@horizn.moe or to /c/Zheam
Lucewing. Once you are verified to be compliant, you will be included in the
list of clients that support FPM. If you are a client developer, you may propose
new keys for the registry by pull request against KEYS.md. See "Proposing a
key" in that file.
Developers may join the registry as a maintainer by reaching out via email. This is exclusive to larger clients, or well trusted and established developers.
The specification and registry are licensed under CC-BY 4.0, and are free for all to use.