Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
thomaseizinger created a comment on a pull request on algesten/str0m
> @thomaseizinger you might need to add > > "feature["sha1"]" > > on your side after this change. That is a semver-breaking change then. Is the plan to make the corresponding version bump ...
xnorpx created a comment on a pull request on algesten/str0m
@thomaseizinger you might need to add "feature["sha1"]" on your side after this change.
xnorpx created a comment on a pull request on algesten/str0m
@algesten ok I tested it in our repo and end2end and seem to work fine. So ready for merge unless more comments.
algesten created a review comment on a pull request on algesten/str0m
Not disabled by default anymore :)
xnorpx created a comment on a pull request on algesten/str0m
> I think we should separate the idea of win crypto vs openssl and this. The `sha1` crate is effectively an optimization regardless of which "base" crypto provider you select. > > Ultimately the...
xnorpx created a comment on a pull request on algesten/str0m
> I think we should separate the idea of win crypto vs openssl and this. The `sha1` crate is effectively an optimization regardless of which "base" crypto provider you select. > > Ultimately the...
algesten created a comment on a pull request on algesten/str0m
I think we should separate the idea of win crypto vs openssl and this. The `sha1` crate is effectively an optimization regardless of which "base" crypto provider you select. Ultimately the featu...
xnorpx created a comment on a pull request on algesten/str0m
I will run this change through our CI and deployment and also figure out github
xnorpx opened a pull request on algesten/str0m
Make sha1 crate optional and a feature
For security reasons rust crypto might need to be disabled and one would want use pure OpenSSL. This change adds a feature flag for sha1 crate. - Allows users to not use sha1 and only use Open...algesten pushed 1 commit to main algesten/str0m
- Dedupe remote ICE candidates The changes in `5c4c9d5` caused problems because we'd end up creating new identical pa... 41ce6cf
algesten closed a pull request on algesten/str0m
Dedupe remote ICE candidates
The changes in `5c4c9d5` caused problems because we'd end up creating new identical pairs. For example, if an existing pair, `0-0`, exists as local: 192.168.1.33:5445, remote: 192.168.1.33:63461. T...algesten created a review comment on a pull request on algesten/str0m
Maybe. But let's revise that in another PR.
k0nserv created a review comment on a pull request on algesten/str0m
Maybe this business should be encapsulated in some method `Candidate::equivalent`
k0nserv opened a pull request on algesten/str0m
Dedupe remote ICE candidates
The changes in `5c4c9d5` caused problems because we'd end up creating new identical pairs. For example, if an existing pair, `0-0`, exists as local: 192.168.1.33:5445, remote: 192.168.1.33:63461. T...k0nserv created a branch on algesten/str0m
dedupe-remote-ice-candidates - A Sans I/O WebRTC implementation in Rust.
algesten pushed 1 commit to main algesten/str0m
- Correctly handle per m-line Absolute Send Time 36ead9e