-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: Share Links or Plain Text using TailDrop #4996
Comments
This comment was marked as duplicate.
This comment was marked as duplicate.
Related: #4896 |
This comment was marked as duplicate.
This comment was marked as duplicate.
+ 1 I would also love to see this feature. It would really break down the walls of the "Apple ecosystem". I have been using the file sharing feature like no tomorrow since recently breaking one link in my chain of apple when changing to android (MacBook <-> iPad <-/-> Sony phone). I have been using KDEConnect but it has reliability issues on macOS. I have been using ShareDrop to share things to nearby friends. But for super fast file sending for my workflow continuity, Tailscale is the best! |
I really need this too for pushing links. Presently I use Pushbullet which doesn't have an app for iOS, so I resort to use Telegram Saved Messages in those cases. |
I am interested to work on this, I have been following the development / conversation and using tailscale+headscale for about a month, and this is something I would really want to have in tailscale. At headscale, proposals go through a https://github.com/juanfont/headscale/tree/main/docs/proposals directory. Does tailscale have anything similar? |
Sharing links from one tailscale app to another would make this app more than essential, it would make it the first thing installed anywhere. My use case is particularly from ios, start reading on the phone, transfer it to the laptop seamlessly. Apple has it with handoff, but a tailscale experience of that would be amazing! |
I really really want this links sharing usecase to replace Pushbullet from my tools stack. Also, Pushbullet is not on iOS, and I work across an Android, mac and iPadOS. And Tailscale is everywhere... I think this feature makes lot of sense, it would be lovely if pushing can be done even if the device on another end is switched off. |
Let me know if you've made any progress in obtaining the required know-how. I'd be interested in making this feature a reality as well. |
+1 |
What are you trying to do?
In a mixed Linux-Apple-Windows ecosystem of devices, its often very frustrating to start one thing on one machine, and have to transfer to another.
While most usages are device-specific (and should be), URLs are one of the things i'd rather be able to transfer easily between devices, as currently I use intermediaries like Telegram Saved Messages andsoforth to paste, switch, and click on it on another device.
AirDrop between Apple devices supports nearly everything, including links, so it'd be really useful if URL-sharing is included as well. (As this issue has made me urge to switch to apple-only for a while, which i don't think is healthy in the long run)
How should we solve this?
Add the ability to tailscale to share URLs (or plain text), and either display or open them directly (via the system handler) on the remote machine.
This way, I could share some stuff im working on from my linux desktop to my laptop, to then save it in an apple-only notes app that i know i will come across later. Or vice-versa, where i need to copy some information from my laptop to my desktop, which will be prone to mis-input if manually transferred, such as IP addresses, or passwords.
What is the impact of not solving this?
Personally, I use intermediaries like empty social media groups (or airdrop) to solve this, but it adds a lot of friction.
I cant assess the impact this has for others, but I will guess that it would maybe open up a more cross-platform seamless experience to (somewhat) the level that Apple is locking into its own ecosystem.
Anything else?
Nothing specific, just that TailScale looks amazing so far.
The text was updated successfully, but these errors were encountered: