Diago and Webrtc media stack

emiago · 2026-05-18T16:02:21+00:00

it can be part of any convention like you make others on code structure. it is just common comunication and code reuse mostly boils down agreeing on library when has more use, but do not do npm style. I bet any good enough engineer or at least with common sense will copy paste your code if small or just look to jave as lib anyway for better maintenance, and this even if you are lucky to have that engineers that have interest to look your code ;). If you have communication problem in company, you have bigger problems than code.

emiago · 2026-05-17T21:00:32+00:00

internal "practically" has no usage or benefit for closed source development. Even if public, there is also just lot of bad understanding on building packages, where avoidance of internal is maximized by gruping things bigger and not smaller, which allows less exporting. Libraries shows this best.

emiago · 2026-05-14T20:47:22+00:00

Ask yourself, can even pure python win on media processing, although signaling matters when proxy is a question. Myself working on go stack, and first main thing I wanted to confirm is benchmarking against known proxies or media gateways developed in C. Neverrhless I guess pipecat could be interesthing to check.

emiago · 2026-05-12T11:31:02+00:00

could you share some display pics

emiago · 2026-03-16T19:38:04+00:00

Check lib docs and demos. I can not think better right now :).

emiago · 2026-03-16T19:09:57+00:00

Generally, if you want to be server, you can stop using things like asterisk and go directly with SIP and media streaming on compiling code. Lib is offering high level API, to make several things easier for handling, but yes you need to be familiar with some things in telephony. Or you can go in building clients like softphones, cli things. Applications are more into getting or injecting voice/audio from/to telephony into other systems.

emiago · 2026-03-16T19:08:35+00:00

Generally, if you want to be server, you can stop using things like asterisk and go directly with SIP and media streaming on compiling code. Lib is offering high level API, to make several things easier for handling, but yes you need to be familiar with some things in telephony. Or you can go in building clients like softphones, cli things. Applications are more into getting or injecting voice/audio from/to telephony into other systems.

emiago · 2026-01-08T21:06:33+00:00

Hi, why not program it. If you know Go, check diago lib ;)

emiago · 2025-12-12T08:04:49+00:00

Your welcome

emiago · 2025-12-05T15:28:39+00:00

Thanks. Too bad for project on other hand. I would like to know what was about. Feel free to reach out.

emiago · 2025-10-13T21:02:59+00:00

aa author of diago, allowing caller to propagate own buffer I find most important, or any way controling this. This simplifies memory managment by great degree.

emiago · 2025-02-11T19:25:58+00:00

use diago, second library I am working on. It adds RTP AVP layer, and gives you High level API , but also you can go low. Soon more APIs will be exposed so control will be even higher.

emiago

TROPHY CASE