Re:Telegram for Android is no longer open source
by lucb1e on Tuesday February 28, 2017 @09:14AM
(#13753854)
1) GPL does make statements about the output of it (i.e. binary builds, which is distributed over the Google Play Store). The app itself does not mention it's GPL, but Telegram.org does.
2) The old code was GPL, so the new one (unless they rewrote it) is a derived work.
I'm not sure the second one applies if it's the original author who relicenses it, but I'm reasonably sure it's at least a legal grey area, and the first one would still be a thing.
Re:Telegram for Android is no longer open source
by lolikoisuru on Tuesday February 28, 2017 @03:40PM
(#13757613)
The thing is, Telegram only owns portion of the copyright. There are also a few other copyright holders as a result of their commits having been pulled in. Telegram cannot legally relicense the codebase without first getting approval from those people. I really doubt that they have done that and if I'm true the app is still GPL.
Re:Telegram for Android is no longer open source
by lucb1e on Tuesday February 28, 2017 @09:10AM
(#13753839)
> While I don't know what this article says (it doesn't load for me)
That is strange, first time apache crashed like this in the 5 years I run this blog. Usually it throws an error at least instead of connection refused.
Re:Telegram for Android is no longer open source
by ominous on Tuesday February 28, 2017 @10:35AM
(#13754442)
I recently tried to compile Telegram (for android) and couldn't get it to work. Just wanted to make a small change (not to add the username to the clipboard when sharing messages).
Re:Telegram for Android is no longer open source
by lucb1e on Tuesday February 28, 2017 @10:44AM
(#13754532)
> not to add the username to the clipboard when sharing messages
That would be great, actually. Maybe we should start a fork.. but then we'd miss the latest 6 months of features unless we feel like putting in so much work they switch to us being official. Great fun.
The github repository isn't updated any more since Oct 11, 2016. [1]
Serious question: Is it possible to just stop publishing the source of a GPL2 licensed software?
[1] https://github.com/DrKLO/Telegram/commits/master
Existing code in the wild will keep the license it was distributed with, but nothing obliges you to keep updating it.
2) The old code was GPL, so the new one (unless they rewrote it) is a derived work.
I'm not sure the second one applies if it's the original author who relicenses it, but I'm reasonably sure it's at least a legal grey area, and the first one would still be a thing.
That is strange, first time apache crashed like this in the 5 years I run this blog. Usually it throws an error at least instead of connection refused.
Anyway, kicked it back alive. Sorry about that.
This url works: http://lucb1e.com/?p=post&id=129 It would be nice if it could be replaced.
I may be an idiot, of course, but does anyone have the necessary steps? I did obtain a new api id https://core.telegram.org/api/obtaining_api_id
The apk installs, but the app doesn't start.
edit: Found this
https://github.com/DrKLO/Telegram/commit/64e8ec3fbd26a876b76...Maybe this repo compiles.
That would be great, actually. Maybe we should start a fork.. but then we'd miss the latest 6 months of features unless we feel like putting in so much work they switch to us being official. Great fun.