TOtosh·Jun 11, 2026Submission
2 points · Open discussionpion
sctp
Go2019–2026
pion / sctp
sctp
A Go implementation of SCTP
3Distinct people
6Mentions
0Explicit recommenders
263GitHub stars
What to know before exploring
What it is
A Go implementation of SCTP
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year6 dated mentions
Observed mentions: 2019-04-08 17:07:47 UTC to 2026-06-11 03:58:29 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
6 sourcesAmazing debugging, I loved reading that. HN doesn't get enough good posts like this anymore :)
If https://github.com/pion/sctp/issues/12 had happened (not just in Pion but across all implementations) this could have been fixed years ago. The hardcoding we all settle for is tragic.
In The iPad was on Tailscale: a WebRTC debugging storyI am sure there are even more implementations that I am not aware of.
* https://github.com/pion/sctp
* https://github.com/aiortc/aiortc/blob/main/src/aiortc/rtcsct...
* https://source.chromium.org/chromium/chromium/src/+/main:thi...
* https://github.com/sctplab/usrsctp
People don't make these decisions for technical reasons only. Career wise it is a bad choice to spend your time working on pre-existing technologies. You don't become a distinguished engineer by iterating on existing technologies. You become one by being the creator of something new.
I think QUIC is great and does a good job solving the problems it was designed to solve. It is disingenuous to pretend these decisions were made only for technical reasons.
In QUIC is now RFC 9000I think SCTP has everything we need, just more knobs need to be exposed [0]
I have gotten feedback about the performance about Pion's SCTP implementation as well. It is a hard problem. The amount of people who care about SCTP performance + WebRTC and are able to work on it is very small.
If anyone is interested in more about this [1] is a fun issue to read.
libwebrtc is also planning to stop using libwebrtc soon. That would mean all browsers (Chrome, Safari, FireFox) will be on something new. Could be good no idea yet. The ongoing work is here [2]
[0] https://github.com/w3c/webrtc-extensions/issues/71
[1] https://github.com/pion/sctp/issues/62
[2] https://webrtc.googlesource.com/src/+log/refs/heads/master/n...
In Send: A Fork of Mozilla's Firefox SendLots of people use WebRTC DataChannels for this! The real tech here is SCTP, and it is pretty amazing. It runs over UDP, and allows you to send messages larger than MTU. You can also choose ordered/unordered and lossy/non-lossy depending on what you are trying to do.
We worked on a Pure Go implementation[0]. If you are interested in learning more. Most people (all browsers) use libusrsctp the C implementation.
[0] https://github.com/pion/sctp
In QuakeJS – A Quake Port to JavaScript with EmscriptenTransfer is done via DTLS, a protocol on top of UDP, so we have to deal with packet loss and retransmission, which itself is controlled by SCTP.
gfile uses pion/sctp[0] (via pion/webrtc[1]), and there has been some work going on to improve performances. :)
The performances used to be far worse, but with the recent improvements on pion/sctp, I felt gfile had become fast enough to be useful to some people.
[0]: https://github.com/pion/sctp
[1]: https://github.com/pion/webrtc
In Show HN: Gfile, a WebRTC based file transfer utility in Go