lsquic
starlink-coverage
lsquic | starlink-coverage | |
---|---|---|
5 | 3 | |
1,453 | 62 | |
- | - | |
7.2 | 1.3 | |
about 2 months ago | about 1 year ago | |
C | Python | |
MIT 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.
lsquic
-
Avoiding HTTP/3 (for a while) as a pragmatic default
I referred to sockets as an API design, not to express an opinion on whether you should place your protocol implementations inside or outside the kernel. (Although that’s undeniably an interesting question that by all rights should have been settled by now, but isn’t.)
Even then, I didn’t mean you should reproduce the Berkeley socket API verbatim (ZeroMQ-style); multiple streams per connection does not sound like a particularly good fit to it (although apparently people have managed to fit SCTP into it[1]?). I only meant that with the current mainstream libraries[2,3,4], establishing a QUIC connection and transmitting bytestreams or datagrams over it seems quite a bit more involved than performing the equivalent TCP actions using sockets.
[1] https://datatracker.ietf.org/doc/html/rfc6458
[2] https://quiche.googlesource.com/quiche
[3] https://github.com/microsoft/msquic
[4] https://github.com/litespeedtech/lsquic
- The Illustrated QUIC Connection
-
LiteSpeed QUIC (LSQUIC) is an open-source implementation of QUIC and HTTP/3
> the word "thread" does not appear anywhere.
because it doesn't use threads? The library is intended to be used inside an eventloop. I think the same also applies for other typical transport libraries - e.g. HTTP/2 or TLS ones.
> Not sure why one would choose this over QUICHE.
I think there are certainly reasons. lsquic seems a lot more optimized than quiche and most other libraries out there. It makes use of some pretty clever datastructures (e.g. https://github.com/litespeedtech/lsquic/blob/master/src/libl...), and likely has a drastically lower rate of heap allocations than other implementations. Some of those things - like the use of intrusive linked lists - are unfortunately not that easy to apply in Rust.
I wouldn't be suprised if lsquic outperforms various other implementations - and if that's important to users it might be a reason to choose it (but as always: measure for your use-case).
I personally also think Rust is the way to go for system level code. But I wouldn't dismiss a project for not using Rust. And this one at least has a fair set of unit-tests, so it looks to me a lot more sane than a lot of other C based projects.
starlink-coverage
- I made a Starlink Availability map
-
SpaceX's New FCC Filing Requests to Operate Starlink 'In Moving Vehicl
Thanks. I dug around for the answer I was looking at.
> Each cell covers 324.29km^2 on average.
https://github.com/sebsebmc/starlink-coverage
- How bad of an idea is it to order if we are moving 10 miles away?
What are some alternatives?
msquic - Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
h3 - Hexagonal hierarchical geospatial indexing system
ssldump - ssldump - (de-facto repository gathering patches around the cyberspace)
dishy_grafana - Starlink Dishy Grafana Dashboards
mvfst - An implementation of the QUIC transport protocol.
open-location-code - Open Location Code is a library to generate short codes, called "plus codes", that can be used as digital addresses where street addresses don't exist.
netty-incubator-codec-quic
starlink-grpc-tools - Random scripts and other bits for interacting with the SpaceX Starlink user terminal hardware
ENet-CSharp - Reliable UDP networking library
rpn - RPN command-line calculator
yojimbo - A network library for client/server games written in C++
localtileserver - 🌐 dynamic tile server for visualizing rasters in Jupyter with ipyleaflet or folium