zackb
Joined 16 years ago
Joined 16 years ago
* This is troubling as I've tested it extensively in Hyprland on different machines.
* You are right that the root installation requirements need more clarification. I was so focused on making it as easy as possible for the user that I buried important details.
* The failures to connect are an endless battle given the crazy inconsistencies in bt controllers. ~/.local/state/tether/tetherd.log should have the details I need to debug it, if you are inclined to open an issue.
1. This would be a major subsystem added to KDE Connect and I have no history with the project.
2. The KDE Connect roadmap explicitly lists iMessage / SMS support as "Won't Implement"
3. My project requires a browser extension and mail extension, I can't imagine I have much of a chance of getting a "KDE Connect" extension approved.
4. Time: it would have taken much longer to jump through all the (appropriate) hoops.
5. Choice. While I'm not a fan of Omarchy, I LOVE what it is doing. Having an alternative to the Big Two and embracing "custom" desktops is very appealing to me, and I think it is a good thing for Linux and FOSS.
6. I was going to do this no matter what, it worked better than I expected, I wanted everyone to have it.
Besides messaging it doesn't do any of the other stuff Tether does (author, im biased).
For non-power users OSX is still a no-brainer, but for a programmer I feel like Apple's left us no alternative.