Ingon

12 ms·

1.
by Ingon 2mo ago
4-week battery life, if you don't go outside. Solar charges the watch relatively slow (e.g. it takes 3 hours of just sitting under the sun to charge a day), but if you get out frequently it just pushes the battery day just a little fur
2.
by Ingon 3mo ago
I've been running GrapheneOS for over an year now. Bought a Pixel 6a last year as a cheap way to test waters, but pretty soon I upgraded to discounted Pixel 9. It took a while to set the basics (coming from iPhone), and I'm still
3.
by Ingon 3mo ago
Amazing, congrats on the release. I've been drawing a lot of inspiration from Iroh, while working on my own https://github.com/connet-dev/connet . While peers in connet communicate peer to peer, I have a long way t
4.
by Ingon 5mo ago
I've been working on a similar tool for a while - connet ( https://github.com/connet-dev/connet ). It builds upon QUIC (instead of wireguard), but I think from an enduser perspective the results ends up looking pret
5.
by Ingon 8mo ago
Termux is great - one of the ways I use it is to install the golang toolchain and compile/run connet.
6.
by Ingon 8mo ago
I'll take a look at what twingate does for sure, thanks for pointing that out. A few things that worth mentioning for connet's current state - you can technically bind to any local IP, not just loopback (or listen to them all). Yo
7.
by Ingon 8mo ago
I've been thinking a lot about this case specifically. And you are right, phones are largely not supported right now - I've been researching how to make that happen. One case I've found that works for me currently is running
8.
by Ingon 8mo ago
I've been working for a while on https://github.com/connet-dev/connet . It gives a different twist at the same problem - instead of an overlay network at L4 (wireguard, etc) or publicly accessible endpoint at L7 (l
9.
by Ingon 8mo ago
connet [1] works in p2p fashion and is pretty quick if it can establish direct connection. Most other solutions do route through a separate node, so if your direct to node latency is low it should be comparable to directly hitting that node
10.
by Ingon 8mo ago
Continue to work on my project for remote private access: https://github.com/connet-dev/connet Just released v0.12.0 which has a lot of package cleanup and some important bugfixes. Next, is making the relay infrastruct
11.
by Ingon 9mo ago
Actually, I realized that I've used `/s` incorrectly. I've been thinking about rewriting the clients in Rust, mostly to allow simpler embedding in other languages - java and swift for example (I think it would be great if con
12.
by Ingon 9mo ago
https://github.com/connet-dev/connet Just finished a major (v0.10) revamp of the API (you can use connet as part of an application, not through the CLI) which also fixed a few issues I've been seeing before. Now,
13.
by Ingon 10mo ago
I am excited for having a new version of NixOS. Few days ago I realized that November is almost gone and went looking for when I can expect the new release. And right on schedule it popped out (was checking throughout the day). Big props to
14.
by Ingon 10mo ago
Tunneling p2p with relay fallback is essentially what connet [1] aspires to be. There are a lot of privacy/security benefits exposing endpoints only to participating peers. You can either run it yourself or use hosted version [2]. [1]
15.
by Ingon 11mo ago
Been using profiles for some years now and they are great. I usually start with the default profile, then navigate to "about:profiles" to open all I need. Thanks to profiles, when my manjaro install broke, I migrated to NixOS and
16.
by Ingon 11mo ago
When I adopted mmap in klevdb [1], I saw a dramatic performance improvements. So, even as klevdb completes a write segment, it will reopen, on demand, the segment for reading with mmap (segments are basically part of write only log). With t
17.
by Ingon 11mo ago
I also started self-hosting more and more. But instead of making services available on the internet/intranet (e.g. VPS reverse proxy/tailscale), I'm binding them to localhost and using connet [1] (cloud or self-host [2]) to c
18.
by Ingon 11mo ago
I used QUIC extensively to implement https://github.com/connet-dev/connet and while I'm super happy with how it turned out, I think QUIC currently suffers from some immaturity - most implementations are still ongo
19.
by Ingon 1y ago
In some ways this reminds me of what I'm trying to do with connet [0] - give users the choice to completely self-host (all is open source), identity host (e.g. control server as cloud solution, host relays themselves) or even full clou
20.
by Ingon 1y ago
I have to double check, but I believe this is server-side/exit node configuration. In case of mulvad, something similar might be on their servers.
21.
by Ingon 1y ago
Endpoints visible to the internet is one of the main reasons I created connet [1] - with it you can choose when and where to realize the other end. Another benefit is that endpoints talk to each other directly (under many conditions) withou
22.
by Ingon 1y ago
Thanks for the correction, I'm still new to iroh and looking to learn more! Seems that the relays in iroh play the role of STUN and TURN (maybe even implement these)? I'd have to read more about DNS discovery (and dht), very inter
23.
by Ingon 1y ago
I work on connet [1] and from what I've seen iroh seem pretty cool. A few random thoughts I had while watching the presentations/reading the docs: * the relays serve both for discovery and relay. In connet these are separate respo
24.
by Ingon 1y ago
Looks very cool. Another self-hosted, open source, and private solution in this space is my own https://github.com/connet-dev/connet/
25.
by Ingon 1y ago
connet itself doesn't have a notion of public share at all - you need clients/peers on both ends (destination and source) to "project" a remote service. connet.dev do enhance this, by running the source clients publicly,
26.
by Ingon 1y ago
If I understand correctly the terminology/case, all shares in connet a private. You access a remote resource as it was local, but that doesn't mean the resource is publicly visible. For example, my local network clients, do not ne
27.
by Ingon 1y ago
Thanks, it would be great to hear if you tried connet and how it went! In any case, homegrown solutions are great, they offer the most flexibility, but also require the biggest time investment (and knowledge of course).
28.
by Ingon 1y ago
Very cool comparison, thank you! One new feature I haven't highlighted yet, is that you can, in addition, encrypt traffic as it goes through relays (both via tls or noise-inspired protocol, dhxcp). This enhances privacy, even when you
29.
Connet.dev – high performance reverse proxy to connect devices privately(connet.dev)
10 points by Ingon 1y ago|14 comments
30.
by Ingon 1y ago
Hi All, This is a hosted version of connet[1]. In addition, it allows users to expose their endpoints directly on the internet (optional and still in progress) [1] https://github.com/connet-dev/connet

More ›