essays: add Matrix Communication Platform (2020, historical)#3
Merged
Conversation
The oldest known post in the candidate list (July 2020). Documents
the long-arc decision narrative from self-hosted XMPP/Prosody (2011)
through Skype and Slack to a federated [matrix] platform (2019).
Front-matter status: 'historical' — that flag was designed exactly
for this case: the decision narrative is still valuable, but specific
operational details have aged (Synapse defaults, Element renaming
from Riot, Facebook bridging crackdown, federation/spaces evolution,
E2EE-by-default). A top-banner blockquote sets the 'Stand: 2020'
expectation so a reader doesn't take 6-year-old ops claims as
current. The status pill rendering on this essay also gives
.lighthouserc.json's category-1.0 assertion coverage of the
status-pill code path, which the existing 'current' essays don't
exercise.
Light edits in the port:
- Top disclosure on the implicit 'we' (then a ~12-person Netresearch
engineering team).
- Replaced the laundry-list of internal tools with generic
categories ('issue trackers, wikis, source-hosting platforms,
monitoring systems'). Kept 'we' where it carries narrative voice.
- Inline annotation on the Riot→Element rename in the references
list (rename was contemporaneous with the original post).
Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The oldest known post in the candidate list (July 2020). Documents the long-arc decision narrative from self-hosted XMPP/Prosody (2011) through Skype and Slack to a federated [matrix] platform (2019).
Status:
historical— that's exactly what this status flag was designed for. The decision narrative is still valuable, but specific operational claims have aged: Synapse defaults, Element renaming from Riot, Facebook bridging crackdown, federation/spaces evolution, E2EE-by-default. A top-banner blockquote sets the Stand: 2020 expectation so readers don't take six-year-old ops details as current advice.Bonus: the status-pill rendering on this essay also gives Lighthouse-CI coverage of the status-pill code path, which the five existing
currentessays don't exercise. Updated.lighthouserc.jsonto include this URL.Light edits in the port (per the agent report):
No customer names, no internal Jira keys, no internal URLs were present in the source — nothing else to strip.