#sequencediagram
LightNews LightNews
jtsveigdalen.bsky.social
Anyone want to postulate why Mermaid arrows aren't rendering in Microsoft Loop's function specifically for Mermaid?

sequenceDiagram
participant A as Desk
participant B as Kitchen

A->>B: Solid arrow from desk to kitchen
B-->A: Dashed arrow back from kitchen to desk
Ladder diagram showing me going back and forth between the desk and the kitchen. But the ladder diagram is sadly missing the arrowheads on the lines.
December 1, 2025 at 10:25 AM
noamtm.com
I'm pretty sure we're already at this point.
sequenceDiagram Alice->>ChatGPT: Please convert these<BR>bullets into a<BR>formal email for Bob. ChatGPT-->>Alice: Here’s the email<BR>based on your bullets. Alice->>Bob: **Sends the email** Bob->>ChatGPT: Please summarize<BR>Alice’s email into<BR>concise bullets? ChatGPT-->>Bob: Here’s the summarized<BR>version in bullet points.
December 15, 2024 at 10:48 AM
0xrotense.bsky.social
SequenceDiagram or Flowchart ?

What’s your favorite ?
February 13, 2024 at 1:23 AM
threlk.net
let’s not talk about why state diagrams are better for what I’m doing (making sequence diagrams and user journeys) when there are also chart types of sequenceDiagram and userJourney
February 28, 2024 at 1:42 AM
takke.jp
チャッピーにモバイルアプリの場合の OAuth 認証・認可のシーケンス図を作ってもらった。PAR、PKCE、DPoPの組み合わせ方を把握したいので。だいたいあってるかな。
認証・認可のシーケンス図。 sequenceDiagram participant User as ユーザー participant ClientApp as クライアントアプリ participant AuthServer as 認可サーバー participant ResourceServer as リソースサーバー User ->> ClientApp: 認証要求 ClientApp ->> AuthServer: POST /par (client_id, code_challenge, scope) AuthServer ->> ClientApp: request_uri を返す ClientApp ->> User: ユーザーをリダイレクト User ->> AuthServer: GET /authorize (request_uri) AuthServer ->> User: ユーザー認証と認可 AuthServer ->> ClientApp: 認可コードを返す (redirect_uri) ClientApp ->> AuthServer: POST /token (code_verifier, 認可コード) AuthServer ->> ClientApp: アクセストークンを返す ClientApp ->> ResourceServer: GET /resource (DPoPヘッダー + アクセストークン) ResourceServer ->> ClientApp: リソースにアクセス許可
September 18, 2024 at 10:12 AM
pddg.bsky.social
今日はmermaidのsequenceDiagramを書くのがGitHub Copilotくんは上手いことを発見した
September 12, 2024 at 9:38 AM
ted.dev
With the visual part done, the rest of the time was spent on a sequence diagram to figure out the flow of information and which objects would be needed to handle the various bits of behavior. While it took quite some time and thought, that's what the design process is about...
sequenceDiagram Player ->> GamePlay: start() GamePlay ->> Game: start() Game ->> Workspace: createForPlayer()<br/>currentTile = StartingHexTile Workspace -->> Game: workspace GamePlay ->> Broadcaster: gameUpdate() Note over Player,Game: (time passes) Player ->> GamePlay: discard(card) GamePlay ->> Game: discard(card) Note over Game: (other stuff happens, too) Game ->> Workspace: discard() Workspace ->> HexTile: discard() HexTile -->> Workspace: next HexTile<br/>(based on state) GamePlay ->> Broadcaster: gameUpdate() Note over Player,Game: (time passes)<br/>Player clicks on PREDICT card for menu Player ->> GamePlay: actionsFor(PREDICT) GamePlay ->> Game: actionsFor(PREDICT) Game ->> Workspace: actionsFor(PREDICT) Workspace ->> HexTile: actionsFor(PREDICT) HexTile -->> Workspace: [Discard] Workspace -->> Game: [Discard] Game -->> GamePlay: [Discard] GamePlay -->> Player: [Discard]
January 22, 2025 at 3:00 PM
jclem.me
Using @pglite.dev as a cache for Automerge and everything works surprisingly well; all in the browser. Eventually hope to use it for things like client-side full-text search over Automerge docs.
```mermaid sequenceDiagram autoNumber participant U as UI participant A as Automerge participant S as Storage participant P as PGlite participant Q as Query U ->> A: Change handle A ->> S: Emit change event Note right of A: Start here on remote changes S ->> P: Write to cache S ->> Q: Invalidate query Q ->> U: Trigger re-query U ->>+ S: Read S ->> P: Read cache Note right of S: Typically, we read cache first. Queries are<br />keyed on cache primary keys, so we read<br />Automerge IDs from cache. S ->> A: Read handle, doc S -->>- U: Result ```
December 16, 2024 at 1:43 PM
antriel.com
I asked @anthropic.com's Claude whether my ramblings about different timelines in multiplayer games makes sense, and it drew me a useful diagram. Fancy.
sequenceDiagram participant S as Server Timeline participant I as Client Interpolated participant P as Client Predicted participant R as Render Timeline Note over S: Authoritative State Note over I: Past (Stable) Note over P: Future (Unstable) Note over R: Visual Smoothing S->>I: Server State Updates Note over I: Interpolation Buffer I->>R: Stable Non-Player Entities P->>R: Player Actions Note over P: Input Prediction S-->>P: State Reconciliation Note over P: Timeline Correction Note over I,P: RTT Adjustment Note right of I: Timeline Shift<br/>Based on Network<br/>Conditions
January 16, 2025 at 11:04 AM
joergi.chaos.social.ap.brid.gy
but tbh with this #uml #mermaid diagram you have some limits.
I'm not sure if that is the best way to show such complex events.

I'm happy if someone has a better way of showing such things.

feel free to tell me how this could be done with #mermaid

#uml #sequencediagram #problems #ui #ux
screenshot eines bugs in mermaid
October 24, 2025 at 10:07 PM
g-age.bsky.social
sequenceDiagram

User->>API: Submit post (signed)

API->>PolicyValidator: Verify ZK + VDF (nova::verify)

PolicyValidator->>DAG Engine: Create block (with VDF timestamp)

DAG Engine->>SMT: Update temporal state tree
August 2, 2025 at 2:32 AM