docs VS namedrop-protocol-spec

Compare docs vs namedrop-protocol-spec and see what are their differences.

docs

Documentations (by madacol)

namedrop-protocol-spec

Specification for the NameDrop DNS delegation protocol (by takingnames)
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
docs namedrop-protocol-spec
1 1
3 17
- -
2.6 3.2
over 2 years ago over 2 years ago
- -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

docs

Posts with mentions or reviews of docs. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-02-23.

namedrop-protocol-spec

Posts with mentions or reviews of namedrop-protocol-spec. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-02-23.
  • Ngrok Alternatives
    13 projects | news.ycombinator.com | 23 Feb 2022
    There's the DomainConnect protocol[0] which has been around for a few years. I didn't find it particularly well matched for open source projects, so I've also done some work on my own protocol[1]. The current draft is implemented by TakingNames.io (as a provider) and boringproxy as a client. You can read more about it and watch a demo here[2].

    That said, I no longer thing DNS is the right layer of abstraction. I think we need an open tunneling protocol[3].

    [0]: https://www.domainconnect.org/

    [1]: https://github.com/takingnames/namedrop-protocol-spec

    [2]: https://takingnames.io/blog/introducing-takingnames-io

    [3]: https://forum.indiebits.io/t/toward-an-open-tunneling-protoc...

What are some alternatives?

When comparing docs and namedrop-protocol-spec you can also consider the following projects:

ngrok-c - ngrok client for c language,Due to the use of GO ngrok language development, porting to embedded devices some inconvenience, such as openwrt, so use C language rewrite a client. Very mini, the need to support polarssl library.

rathole - A lightweight and high-performance reverse proxy for NAT traversal, written in Rust. An alternative to frp and ngrok.

TunSafe - Source code of the TunSafe client

onionpipe - Onion addresses for anything.

jtunnel-netty-client - Create Tunnels and expose local servers to the internet

awesome-tunneling - List of ngrok/Cloudflare Tunnel alternatives and other tunneling software and services. Focus on self-hosting.

Code-Server - VS Code in the browser

tolocal - self-hosted reverse proxy from public dns domain to localhost