Technically, yes. You just copy the same config on both machines.
It's not something that's "supported" yet, but it is a "hidden feature" that already works.
Be careful, it can be trixy and lead to weird things (like half of your requests working and the other half not in-between state changes).
There's a ton of work being done in the "next" branch that will merge into v1 soonish, so let me know if you actually get into making in code changes. I believe "next" is functional right now, but I had to drop it mid-commit-stream to switch to some other work, so it wouldn't blow my mind if there's a small easy-to-fix issue as well.
Technically, yes. You just copy the same config on both machines.
It's not something that's "supported" yet, but it is a "hidden feature" that already works.
Be careful, it can be trixy and lead to weird things (like half of your requests working and the other half not in-between state changes).
There's a ton of work being done in the "next" branch that will merge into v1 soonish, so let me know if you actually get into making in code changes. I believe "next" is functional right now, but I had to drop it mid-commit-stream to switch to some other work, so it wouldn't blow my mind if there's a small easy-to-fix issue as well.
That's unlikely to happen due to the privacy and security concerns.
Telebit Relays don't decrypt the traffic and, therefore, can't peek into the data to create a fingerprint from cookies and whatnot.
It could be implemented just by keeping an IP address cache, but the direction that we're going with Telebit is to create home servers ( https://rootprojects.org ), so the preference would be to help make it convenient for your servers to operate with master-master data synchronization rather than to build more traditional lock-in style cloud infrastructure.
That's unlikely to happen due to the privacy and security concerns.
Telebit Relays don't decrypt the traffic and, therefore, can't peek into the data to create a fingerprint from cookies and whatnot.
It could be implemented just by keeping an IP address cache, but the direction that we're going with Telebit is to create home servers ( https://rootprojects.org ), so the preference would be to help make it convenient for your servers to operate with master-master data synchronization rather than to build more traditional lock-in style cloud infrastructure.
One of the exciting ideas for me about the original mvp was that you could have a hub at 2 locations that be a viable backup solution with 2 locations or more.
One of the exciting ideas for me about the original mvp was that you could have a hub at 2 locations that be a viable backup solution with 2 locations or more.
Yes. And the direction we're heading with the backup solution is master-master redundancy.
Sticky load balancing isn't necessary when you design the system to sync available hosts.
Yes. And the direction we're heading with the backup solution is master-master redundancy.
Sticky load balancing isn't necessary when you design the system to sync available hosts.
Everything that's necessary to open source in order for your data to be in your control and to have the choice to host any external services (i.e. the Telebit Relay) will be open source.
To help us bootstrap to get to the point of selling the hardware we will be offering products and services for those that prefer the convenience of "Just Works" to building it themselves.
Remind me what your skills are?
We're doing Go, Rust, Node.js, iOS, Android, and Browser. There are a number of things that you could help, but first I'd need to know what it is you are personally interested in as well as what you're skilled at.
I'd love to get the Go or Rust version of the open source Telebit client started. I'd love to get the iOS app, which is about halfway done in terribly crappy outsourced code (i.e. fully functional, working, but not pleasant to use or develop with), to the point of publishing it to the App store so that it can be used with Telebit (or self-hosted) to sync photos
Everything that's necessary to open source in order for your data to be in your control and to have the choice to host any external services (i.e. the Telebit Relay) will be open source.
To help us bootstrap to get to the point of selling the hardware we will be offering products and services for those that prefer the convenience of "Just Works" to building it themselves.
Remind me what your skills are?
We're doing Go, Rust, Node.js, iOS, Android, and Browser. There are a number of things that you could help, but first I'd need to know what it is you are personally interested in as well as what you're skilled at.
I'd love to get the Go or Rust version of the open source Telebit client started. I'd love to get the iOS app, which is about halfway done in terribly crappy outsourced code (i.e. fully functional, working, but not pleasant to use or develop with), to the point of publishing it to the App store so that it can be used with Telebit (or self-hosted) to sync photos
Is there a way to load balance between 2 machines running telebit or to connect them?
Technically, yes. You just copy the same config on both machines.
It's not something that's "supported" yet, but it is a "hidden feature" that already works.
Be careful, it can be trixy and lead to weird things (like half of your requests working and the other half not in-between state changes).
There's a ton of work being done in the "next" branch that will merge into v1 soonish, so let me know if you actually get into making in code changes. I believe "next" is functional right now, but I had to drop it mid-commit-stream to switch to some other work, so it wouldn't blow my mind if there's a small easy-to-fix issue as well.
Like it would be nice if we had the option to do sticky load balancing or not when this is officially supported for in between requests.
That's unlikely to happen due to the privacy and security concerns.
Telebit Relays don't decrypt the traffic and, therefore, can't peek into the data to create a fingerprint from cookies and whatnot.
It could be implemented just by keeping an IP address cache, but the direction that we're going with Telebit is to create home servers ( https://rootprojects.org ), so the preference would be to help make it convenient for your servers to operate with master-master data synchronization rather than to build more traditional lock-in style cloud infrastructure.
One of the exciting ideas for me about the original mvp was that you could have a hub at 2 locations that be a viable backup solution with 2 locations or more.
Yes. And the direction we're heading with the backup solution is master-master redundancy.
Sticky load balancing isn't necessary when you design the system to sync available hosts.
Is this solution going to be opensourced, can I help contribute to it?
Everything that's necessary to open source in order for your data to be in your control and to have the choice to host any external services (i.e. the Telebit Relay) will be open source.
To help us bootstrap to get to the point of selling the hardware we will be offering products and services for those that prefer the convenience of "Just Works" to building it themselves.
Remind me what your skills are?
We're doing Go, Rust, Node.js, iOS, Android, and Browser. There are a number of things that you could help, but first I'd need to know what it is you are personally interested in as well as what you're skilled at.
I'd love to get the Go or Rust version of the open source Telebit client started. I'd love to get the iOS app, which is about halfway done in terribly crappy outsourced code (i.e. fully functional, working, but not pleasant to use or develop with), to the point of publishing it to the App store so that it can be used with Telebit (or self-hosted) to sync photos