Our great sponsors
| sctp | usrsctp | |
|---|---|---|
| 1 | 2 | |
| 210 | 638 | |
| 3.3% | 1.1% | |
| 7.9 | 7.1 | |
| 10 days ago | 18 days ago | |
| Go | C | |
| MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sctp
-
QUIC is now RFC 9000
I 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.
usrsctp
-
Ask HN: GitHub Download Hash Change?
Today, an issue was raised in one project I use, because their build system rejected an invalid sha256sum while downloading a dependency from a GitHub zip file.
The offending dependency is usrsctp (https://github.com/sctplab/usrsctp) at commit 9d6b99b:
https://github.com/sctplab/usrsctp/archive/9d6b99b10a70f7a63d21cd80d03c353da9ac19d3.zip
This file's sha256sum has always been
d9b7b3350ea0be2a3d1437e404d4852df741c4984b734729c5edc337ff4b7611 -
QUIC is now RFC 9000
I 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.
What are some alternatives?
openmptcprouter - OpenMPTCProuter is an open source solution to aggregate multiple internet connections using Multipath TCP (MPTCP) on OpenWrt
shadowsocks-rust - A Rust port of shadowsocks
openssl - TLS/SSL and crypto library with QUIC APIs
msquic - Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
neqo - Neqo, an implementation of QUIC in Rust
quinn - Async-friendly QUIC implementation in Rust
aiortc - WebRTC and ORTC implementation for Python using asyncio