Rizful.com on Nostr: Yes. There is huge demand for residential proxies. We would be interested in working ...
Yes. There is huge demand for residential proxies. We would be interested in working in this with you.
So we want to build this so the “control” layer for each user’s VPN service communicates with the world via Nostr. Right?
Napkin sketch: Control layer, where clients pay for, start, stop, and monitor is all via Nostr. Payment by lightning. actual VPN services will be provided by some kind of wire guard server running on each users’s computer.
Really it is Wireguard on both client and server with an overlay of some pretty simple management scripts that communicate with other clients and servers over relays.
It’s such a great fit for Noster because it’s a relatively straightforward problem that has already been solved in a centralized manner and it will really benefit from lightning as a payment model and the ability for anybody to serve up either a client or a server.
So to be clear, the “server” is the user in his or her home running the"wireguard server" which provides a wireguard VPN services to "clients".
And typically you might actually find that the “client” wants to connect to hundreds, or thousands of servers. The demand for residential proxies is usualy only among businesses that need to do a ton of scraping and need thousands of residential IP addresses.,
The SERVER implementation, the one that will run on each user's home computer... seems pretty straightforward to me. The user run ssome kind of lightweight application, maybe an electron app (but of course that’s too heavyweight, so we use whatever the new hotness is for Desktop applications.) This desktop application launches a WIREGUARD SERVER PROCESS a Nosr process that is always looking for new clients. It offers client services ......with parameters for price, bandwidth limit, probably a bunch of other things, but not like a zillion things.
We can just study the existing centralized residential IP providers (I know them well) and see what our options are.
The CLIENT application will only be actually run by probably not more than a few hundred or thousand people in the world... organizations that really have demand for these these kind of proxies... which makes it YET ANOTHER great fit for nostr, because these are relatively SOPHISTICATED consumers who could probably be convinced to try it out if they realized it was cheaper or more efficient, or whatever.
The key is to not try to over-engineer this... we are talking about a couple thin layers on top of Wireguard and Nostr. I need to learn more about DVMs.
So we want to build this so the “control” layer for each user’s VPN service communicates with the world via Nostr. Right?
Napkin sketch: Control layer, where clients pay for, start, stop, and monitor is all via Nostr. Payment by lightning. actual VPN services will be provided by some kind of wire guard server running on each users’s computer.
Really it is Wireguard on both client and server with an overlay of some pretty simple management scripts that communicate with other clients and servers over relays.
It’s such a great fit for Noster because it’s a relatively straightforward problem that has already been solved in a centralized manner and it will really benefit from lightning as a payment model and the ability for anybody to serve up either a client or a server.
So to be clear, the “server” is the user in his or her home running the"wireguard server" which provides a wireguard VPN services to "clients".
And typically you might actually find that the “client” wants to connect to hundreds, or thousands of servers. The demand for residential proxies is usualy only among businesses that need to do a ton of scraping and need thousands of residential IP addresses.,
The SERVER implementation, the one that will run on each user's home computer... seems pretty straightforward to me. The user run ssome kind of lightweight application, maybe an electron app (but of course that’s too heavyweight, so we use whatever the new hotness is for Desktop applications.) This desktop application launches a WIREGUARD SERVER PROCESS a Nosr process that is always looking for new clients. It offers client services ......with parameters for price, bandwidth limit, probably a bunch of other things, but not like a zillion things.
We can just study the existing centralized residential IP providers (I know them well) and see what our options are.
The CLIENT application will only be actually run by probably not more than a few hundred or thousand people in the world... organizations that really have demand for these these kind of proxies... which makes it YET ANOTHER great fit for nostr, because these are relatively SOPHISTICATED consumers who could probably be convinced to try it out if they realized it was cheaper or more efficient, or whatever.
The key is to not try to over-engineer this... we are talking about a couple thin layers on top of Wireguard and Nostr. I need to learn more about DVMs.