The earlier Flutter integration joined a Pusher-compatible connection with Laravel Echo’s event naming. The source’s build and Dart snippets had collapsed into single lines, so this revision explains the flow rather than inventing missing source boundaries.
Connection and authorization are separate
The WebSocket URL included an application key and protocol information. That application key identifies the application; it is not proof that a client may subscribe to any private channel. The source also supplied a separate broadcasting-authorization endpoint. Its environment hostname is omitted here.
Connect once, subscribe deliberately
The old callback created an Echo wrapper after a CONNECTED state and listened to PostCreated on posting. Laravel event namespaces affect how the event name is resolved. Reconnection can run the callback again, so subscription ownership and duplicate listeners need review.
The source declared flutter_pusher_client ^0.3.1 and laravel_echo ^0.2.8. These are historical ranges, not a new compatibility claim. No socket, subscription, or authorization request was created for this revision.