HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
pion
dtls
Go2020–2026
pion / dtls

dtls

DTLS 1.2 / 1.3 implementation for Go

3Distinct people
7Mentions
0Explicit recommenders
714GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

DTLS 1.2 / 1.3 implementation for Go

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:59:52 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year7 dated mentions

Observed mentions: 2020-04-21 08:22:53 UTC to 2026-10-16 20:59:02 UTC.

01232020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC312
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC110

What Hacker News says

3 sources
I am super happy that I invested in Go. I ended up working on TURN, WebRTC and DTLS and feel I made the right choice. The impact vs time spent was worth it. I don't think there is any other language I would have had a better experience. Either it is too niche, or it is so popular that the community is anemic. * https://github.com/pion/dtls * https://github.com/pion/webrtc * https://github.com/pion/turn Go is really great as a 'teaching language'. I have seen lots of software pop up that was inspired by reading the Pion code. I think that is great, it is much harder to read and learn from other languages. Also really great for contributions. I get so many people making their first Open Source commit. The languages simplicitly really makes it easy. The most frustrating thing about Go isn't even the language, it is the community for me. It i
Read the rest
s very business/corporate focused. Everything is all about Kubernetes/cloud. I apply for conferences/meetups non-stop, but never have any luck. It is always the same company reps. I am envious of the Rust community here, but maybe grass is always greener on the other side?
In Eleven Years of Go
This is a cool utility that someone contributed to Pion! I get lots of questions around why certain calls need TURN, or how P2P works in general. When you run it you will get output like sean@siobud:~/stun$ ./stun-nat-behaviour 2020/05/29 23:18:31 Connecting to STUN server: stun.voip.blackberry.com:3478 2020/05/29 23:18:32 Local address: 0.0.0.0:56304 2020/05/29 23:18:32 Received xormapped address: 165.227.221.230:56304 2020/05/29 23:18:32 Received xormapped address: 165.227.221.230:56304 2020/05/29 23:18:32 NAT mapping behavior: endpoint-independent 2020/05/29 23:18:32 Local address: 0.0.0.0:41265 2020/05/29 23:18:32 Received xormapped address: 165.227.221.230:41265 2020/05/29 23:18:32 NAT filtering behavior: endpoint-independent If you aren't familiar with Pion it is a collection of libraries to solve WebRTC/VoIP/Io
Read the rest
T problems. It is by a diverse set of contributors, and we are always looking for me! I personally want to get this space to be more like the web, owned by individuals instead of companies. Check out our other popular libraries * https://github.com/pion/webrtc * https://github.com/pion/ion * https://github.com/pion/dtls
In Show HN: pion/stun-nat-behaviour. Do you know your NAT rules?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.