brndnbuilds
Joined 3 years ago
Joined 3 years ago
Edit: How many machines would you expect to run it on? What would be your expectations for the licence use on multiple machines?
You're free to run WireSock in the terminal. It's linked to in this post and in the github repo. TunnlTo aims to make WireSock more accessible and to add some quality of life features. I'm collaborating with the WireSock creator and while it may seem simple at the moment it is early days... we had to start somewhere.
> I would actually say it's pretty dangerous to have something installing .msi from git, touching registry etc ...
Did you look at this code?: https://github.com/TunnlTo/desktop-app/blob/main/dist/setup....
It tells the user why it needs to install the msi, explains what it is, and gives them the option to proceed. The msi is signed by the same EV code signing certificate as the TunnlTo app. There is also information about WireSock and links in the GitHub readme.
> installing .msi from git
The .msi doesn't come from "git", it is included in the TunnlTo installer which is standard practice.
> touching registry etc ...
I'm not sure why there would be a concern if a msi interacts with the registry? That is pretty standard stuff.
Well it's not finished yet :)
The reasons for choosing Tauri:
- With new projects I try to learn something new but not everything all at once. This helps to not get overwhelmed and ship something in a reasonable timeframe.
- I'm comfortable with HTML, CS, JS and I wanted to learn Rust which Tauri uses.
- I figured the UI is going to change a lot in the early days and I wanted to be able to iterate on it quickly, so choosing something I know already for the UI made sense to me.
- If the project gets bigger, I can move to a JS framework easily enough and will have access to all the ecosystem it provides.
- I thought it would be easier to attract contributors with a web framework UI and Rust.
- While I want it to be as lightweight as possible, it is not going to be run on low spec machines so I feel like the tech stack is fit for purpose.
That is a cool trick. Can you actually define which Firefox tabs use the proxy? Does it highlight the tab in some way to show you which connection you're on?