Loads a conversation's or topic's artifacts and keeps them current.
A conversation's or a topic's artifacts are revised while the event (or the series) runs,
and every appended version is announced to the container's own room as artifact:version;
a background generation that errors or finds nothing worth writing is announced the same
way as artifact:generationFailed. Either notice carries only ids, never content: the room
is joined with no passcode at all, so nothing that arrives in it is proof of anything, and
the content is re-read through the REST route, which checks the artifact passcode. The
room join presents no channels because the bare room needs none, and a reader holding only
the artifact passcode has no chat credentials to offer.
A socket isn't guaranteed, though — a reader can be on a page that doesn't hold one, and
one that does can still drop a notice (a disconnect, a reconnect gap). Either way, a
generation left pending is also caught by a poll that re-reads any artifact still
pending, so the status shown always eventually matches the server's even with no live
push at all; the socket, where it exists and stays connected, only makes that happen sooner.
Loads a conversation's or topic's artifacts and keeps them current.
A conversation's or a topic's artifacts are revised while the event (or the series) runs, and every appended version is announced to the container's own room as
artifact:version; a background generation that errors or finds nothing worth writing is announced the same way asartifact:generationFailed. Either notice carries only ids, never content: the room is joined with no passcode at all, so nothing that arrives in it is proof of anything, and the content is re-read through the REST route, which checks the artifact passcode. The room join presents no channels because the bare room needs none, and a reader holding only the artifact passcode has no chat credentials to offer.A socket isn't guaranteed, though — a reader can be on a page that doesn't hold one, and one that does can still drop a notice (a disconnect, a reconnect gap). Either way, a generation left
pendingis also caught by a poll that re-reads any artifact stillpending, so the status shown always eventually matches the server's even with no live push at all; the socket, where it exists and stays connected, only makes that happen sooner.See UseArtifactsParams for parameter details.