Tether: iMessage, SMS, etc. on Linux
zackbartel.com
Tether: iMessage, SMS, etc. on Linux
1–10 of 231 posts
Re: Tether: iMessage, SMS, etc. on Linux
#2Huh, haven't thought of it. Just relicensed ancs4linux to MIT.
Re: Tether: iMessage, SMS, etc. on Linux
#3What's a feature not in KDE connect that the writer wanted and it didn't have?
They could always submit a pr.
Beeper exists you know....
I have a question. It's fine to build for your own self but is it okay to release something in public when the environment is a moving target and you are just a one-man team keeping it afloat?
Wouldn't it be better to go behind established FOSS products and not reinvent the wheel when you don't have to?
I understand no one can tell you how to or why to do certain things but there comes a time, when youw want to help, not build the next temple os and instead help manjaro or whatever is cool these days?
Re: Tether: iMessage, SMS, etc. on Linux
#4I don't know. What's a feature not in KDE connect that the writer wanted and it didn't have? They could always submit a pr. Beeper exists you know.... I have a question. It's fine to build for your own self but is it okay to release something in public when the environment is a moving target and you are just a one-man team keeping it afloat? Wouldn't it be better to go behind established FOSS products and not reinven…
Re: Tether: iMessage, SMS, etc. on Linux
#5> Personally, I think putting an interoperability protocol implementation behind a copyleft license is a little unfortunate! Huh, haven't thought of it. Just relicensed ancs4linux to MIT.
[0] copyleft-licensed library that could be legally linked into non-copyleft code base.
Re: Tether: iMessage, SMS, etc. on Linux
#6I have had a iPhone for 15 years, and I have only ever been able to back it up with iTunes on windows (as I will never buy a Mac).
Apple’s refusal to provide interoperability borders on criminal. I wish there was a better option.
Re: Tether: iMessage, SMS, etc. on Linux
#7I don't know. What's a feature not in KDE connect that the writer wanted and it didn't have? They could always submit a pr. Beeper exists you know.... I have a question. It's fine to build for your own self but is it okay to release something in public when the environment is a moving target and you are just a one-man team keeping it afloat? Wouldn't it be better to go behind established FOSS products and not reinven…
Even features that do exist don't always work reliably. I can't send files between devices, most of the time clipboard sharing doesn't work either, and there's loads not implemented.
> What's a feature not in KDE connect that the writer wanted and it didn't have?
From TFA:
"And Tether now supports: iMessage, SMS, Notifications, Contact sync on Linux. In addition to its previous: File Transfer, Clipboard Sync, OTP handling."
> Wouldn't it be better to go behind established FOSS products and not reinvent the wheel when you don't have to?
From TFA:
"Before you ask, I know KDE Connect exists. It's great! If you're on Android you should definitely use it. The problem is that it didn't do what I wanted and it's roadmap indicated it never would."
Maybe next time read the article before commenting?
Re: Tether: iMessage, SMS, etc. on Linux
#8> Personally, I think putting an interoperability protocol implementation behind a copyleft license is a little unfortunate! Huh, haven't thought of it. Just relicensed ancs4linux to MIT.
It’s things like this that give me hope for the world.