nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q I'm trying to look at the code that you have deployed at yakihonne.com -- it seems to be totally different than this... https://github.com/YakiHonne/yakihonne-web-app/tree/main/client/src .... but you do seem to be recently updating "yakihonne-web-app"... am I right in guessing that this thing on github is your newest version isn't complete or deployed yet? And that the previous version, currently at yakihonne.com, is not currently open source?
Incidentally, this is actually the ethical alternative to existing, centralized services. Because it’s an unspoken thing that when you’re using a centralized service, those residential IP’s are being served up by either computers which have malware or which are running applications which are secretly prostituting their users,l bandwidth.
One first step would be to take a quick look at any shitcoin projects which have tried to do this. I’m sure there are a few and obviously we don’t want to use their Blockchain stuff but they might have already solved what exactly the client in the server are supposed to do.
nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q #yakihonne another request. On both iOS and the web I feel it is now "too easy" to reply to a REPOST instead of the ORIGINAL message. Isn't it true that, given a choice, a user would usually rather add their reply note to the ORIGINAL message and thread, instead of a repost?
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.
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.
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
The server implementation, the one that will run on each users, home computer, Seems pretty straightforward to me. The user run some kind of lightweight application, maybe an electron app but of course that’s too heavyweight so whatever the new hotness is for Desktop applications. This launches, a wire guard process and a Noster 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.
And typically you might actually find that the “client” wants to connect to hundreds, or thousands Of servers. Because these are usually larger businesses that need to do a ton of scraping and need thousands of residential IP addresses.,
So to be clear, the “server” is the user in his or her home running the server software which provides a wireguard vpn service to the “client”.
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’s really benefit from lightning as a payment model and the ability for anybody to serve up either a client or a server.
Really it is wire guard on both client and server with an overlay of some pretty simple management scripts that communicate with other clients and servers over relay
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
So we want to build this so the “control” layer each user’s vpn service communicates with the world via Nostr. Right ?