Hi there,
First of all, thank you for this amazing project! I really love using sendme for file transfers. However, relying on exchanging extremely long tokens (like blobaagq6jqbwpw...) every single time becomes very friction-heavy, especially for frequent transfers between personal devices.
I know one of the core strengths and philosophies of sendme is "No account required". To perfectly respect this policy while completely eliminating the ticket nightmare, I would love to propose a connection workflow heavily inspired by RustDesk:
Proposed Workflow:
-
Recent Sessions / Trusted Devices List:
- The main UI could feature a "Recent/Trusted Devices" list (just like RustDesk).
- It would display the saved devices with their OS icons, hostname, and an online/offline status indicator (which can be handled via local network discovery like mDNS/UDP broadcast for local use).
- The app can automatically detect the OS type and system hostname (e.g.,
Admin@desktop-windows or User@phone-android) to label the devices clearly.
-
Seamless Pairing & Passwords (RustDesk-style):
- When initiating a transfer for the first time, you just enter the target device's Remote ID.
- On the receiving end, a prompt pops up: "Accept / Allow incoming file" with a checkbox for "Remember this device as trusted".
- The Core Mechanism: Once the user checks the "Remember this device as trusted" box, a password input field appears right there. The user enters the target device's Permanent Password in that box. If the password is correct, the device is successfully saved to the trusted list. From that moment on, future transfers will go through instantly in the background without requiring any manual approval, prompts, or new tickets.
💡 Technical Hint for Implementation (Persistent IDs without Accounts):
To prevent users from losing their Remote ID when reinstalling their OS (and having to repair everything), the app could utilize a hardware-derived fingerprint (HWID) as a seed to generate a persistent Remote ID (e.g., a simple numeric or short alphanumeric string).
This ensures that even after a clean OS reinstall, the device automatically gets the exact same ID (e.g., 123456789) every single time, keeping the project 100% decentralized and account-free while providing the ultimate user experience.
What do you think about implementing a workflow like this? Thank you again for your hard work!
Hi there,
First of all, thank you for this amazing project! I really love using
sendmefor file transfers. However, relying on exchanging extremely long tokens (likeblobaagq6jqbwpw...) every single time becomes very friction-heavy, especially for frequent transfers between personal devices.I know one of the core strengths and philosophies of
sendmeis "No account required". To perfectly respect this policy while completely eliminating the ticket nightmare, I would love to propose a connection workflow heavily inspired by RustDesk:Proposed Workflow:
Recent Sessions / Trusted Devices List:
Admin@desktop-windowsorUser@phone-android) to label the devices clearly.Seamless Pairing & Passwords (RustDesk-style):
💡 Technical Hint for Implementation (Persistent IDs without Accounts):
To prevent users from losing their Remote ID when reinstalling their OS (and having to repair everything), the app could utilize a hardware-derived fingerprint (HWID) as a seed to generate a persistent Remote ID (e.g., a simple numeric or short alphanumeric string).
This ensures that even after a clean OS reinstall, the device automatically gets the exact same ID (e.g.,
123456789) every single time, keeping the project 100% decentralized and account-free while providing the ultimate user experience.What do you think about implementing a workflow like this? Thank you again for your hard work!
