jamilbk

5 ms·

1.
Firezone REST API generally available(firezone.dev)
1 points by jamilbk 26d ago|0 comments
2.
WireGuard-Native NAT Traversal(firezone.dev)
3 points by jamilbk 27d ago|0 comments
3.
by jamilbk 1mo ago
I came here to make a similar comment. It seems like TigerBeetle was built for exactly the type of transactional processing this post is about?
4.
by jamilbk 2mo ago
We just invested a good amount of time restructuring our docs for Diátaxis. It was helpful, but I wouldn't take it as gospel. The important thing to remember is that each piece of content should be one of the four types. If you're
5.
The enterprise identity crisis: Who's Alice?(firezone.dev)
1 points by jamilbk 3mo ago|0 comments
6.
The identity join problem: Linking SSO profiles to directory users(workos.com)
3 points by jamilbk 4mo ago|0 comments
7.
Sans-IO: The secret to effective Rust for network services (2024)(firezone.dev)
1 points by jamilbk 4mo ago|0 comments
8.
Against DNSSEC (2015)(sockpuppet.org)
1 points by jamilbk 4mo ago|0 comments
9.
by jamilbk 5mo ago
Yeah, the weight floor can be hit or miss with regards to striking convos with strangers. Many of the people there want to make friends too, but many just want to focus on their workout. Two related contexts that I've found to be much
10.
by jamilbk 5mo ago
I remember yanking out the onstar unit in my 2015 silverado to physically disconnect the cell antenna. This was (is?) the only practical way to disable cellular in that vehicle. Kudos to Rivian for making this a supported user privacy featu
11.
by jamilbk 8mo ago
At Firezone we started with soft-deletes thinking it might be useful for an audit / compliance log and quickly ran into each of the problems described in this article. The real issue for us was migrations - having to maintain structure
12.
by jamilbk 9mo ago
I don't fully understand the complaints about enshittification of open source permissively licensed software. If the source code is available for you to fork, modify, and maintain as you see fit, what's the complaining really abou
13.
Hard Mode Rust (2022)(matklad.github.io)
3 points by jamilbk 2y ago|0 comments
14.
by jamilbk 2y ago
Yes, the established standard here is known collectively as Interactive Connectivity Establishment (ICE) [1] which WebRTC relies on -- there are a few good libraries out there that implement it and/or various elements of it [2] [3]. li
15.
by jamilbk 2y ago
PRs welcome! We may not have much bandwidth to help, but happy to review anything that comes along. We can discuss further perhaps on a GitHub issue so the rest of the Firezone team can offer input: https://github.com/firezo
16.
by jamilbk 2y ago
I've exposed `Android` as a support OS. Give it a shot now.
17.
by jamilbk 2y ago
Noted! I'll update it to use the Unix instructions in that case. Thanks for the feedback!
18.
by jamilbk 2y ago
Unfortunately the app wasn't designed to intake test results from runs that didn't originate from itself. We wanted to make it harder to submit fake results, and didn't want to add a lot of friction around user auth and such.
19.
by jamilbk 2y ago
Great! Did the test report the block accurately for you?
20.
Show HN: Test your WireGuard connectivity and see global stats, no client needed(probe.sh)
43 points by jamilbk 2y ago|10 comments
21.
by jamilbk 2y ago
We have a few intrepid users self-hosting the entire Firezone stack, but we don't have documentation to support it (yet), and wouldn't recommend it for production. It's something we'd like to write and maintain eventuall
22.
by jamilbk 2y ago
You can read more about how we came up with the current implementation here: https://github.com/firezone/firezone/issues/3553 We didn't invent these techniques. Host candidates are part of standard ICE:
23.
by jamilbk 2y ago
Firezone's DNS-based routing is able to manage access to multiple services independently, even if they share the same IP address. So you could for example allow access to gitlab.company.com but not jira.company.com even if they were on
24.
by jamilbk 2y ago
We don't support full-tunnel yet, but it's just around the corner. Track this issue if you're interested in its progress: https://github.com/firezone/firezone/issues/2667
25.
by jamilbk 2y ago
Thanks! Erlang/OTP has so far been an excellent platform to build on for a product like Firezone. We chose it specifically for its reputation for powering soft realtime systems. Phoenix Channels are an added bonus that allow us to push
26.
by jamilbk 2y ago
Are you referring to the macOS client app? It's built in Swift with an FFI bridge to the Rust-powered connectivity layer. Source is here: https://github.com/firezone/firezone/tree/main/swift/app
27.
by jamilbk 2y ago
Appreciate the feedback! Will certainly plan to take the product demos up a notch going forward.
28.
by jamilbk 2y ago
Thanks for the support!
29.
by jamilbk 2y ago
This is a fairly common scenario and one that we had in mind when building the NAT traversal implementation. The short answer is that you wouldn't need to sign out of Firezone when in the office -- the connection should hairpin off the
30.
by jamilbk 2y ago
Ah yes, don't get me started on all the fun edge cases involved in supporting cross platform network stacks and all their subtle tunnel API differences :-) We're trying to stay focused on keeping policies easy to define and manage

More ›