Ivan Tivonenko

 1. Rippling incorrectly shown for incoming trustlines 2. For just-created incoming trust line limit is not in place - it must be in "Min" 3. Edit turned on for...

@vhpoet It is one table for all trust lines - incoming and outgoing. But "Rippling" column shows incorrect data for incoming trustilines

Issue Status: 1. **Open** 2. Started 3. Submitted 4. Done __This issue now has a funding of 0.1 ETH (69.21 USD @ $692.1/ETH) attached to it.__ * If you would...

Issue Status: 1. **Open** 2. Started 3. Submitted 4. Done __This issue now has a funding of 0.1 ETH (69.21 USD @ $692.1/ETH) attached to it.__ * If you would...

Another possible solution - [joy4](https://github.com/livepeer/joy4)? It already has h264 parsing code, maybe it will be enough for our task? @j0sh what do you think?

@j0sh I'm not familiar with low-lever h264 protocol. So, width/height information is contained only in SPS/PPS NALUs, not inside VCL packets? After your comment in decode PR I thought that...

> Yes - by putting a new SPS in front of each frame. OK, so current joy4 can be used to count pixels for whole segment. Also, for current RTMP...

`nginx-rtmp-module` seems to be unmaintained - last commit made in 2017, it has 906 open issues and 79 open PRs. That means that with this module we will be in...

@ericxtang to clarify - why we bringing this up now? Do we really experience any pain with what we have right now?

@j0sh What do you think about this one? It was hard to reproduce in GCP, but on the rig with 1660s I was hitting this often during my testing on...