21–30 of 40 posts
You know what I just realized? I couldn't tell you the last time I installed a new app on my phone. Everything there is mostly out to exploit me, or a direct security liability regardless of what app store.
Compile it yourself https://github.com/chatboxai/chatbox
Cool that they did that, but they could also start behaving properly. The app labels itself at GPL licensed, but the most recent releases are not available on GitHub. It's been the situation for quite a while now and it's been raised with the author a few times in the issues. They don't seem to care.
Cool that they did that, but they could also start behaving properly. The app labels itself at GPL licensed, but the most recent releases are not available on GitHub. It's been the situation for quite a while now and it's been raised with the author a few times in the issues. They don't seem to care.
Cool that they did that, but they could also start behaving properly. The app labels itself at GPL licensed, but the most recent releases are not available on GitHub. It's been the situation for quite a while now and it's been raised with the author a few times in the issues. They don't seem to care.
There's a community edition that's GPL, and it does say they're 'going open source' but clearly it's not the exact same app as the official distribution:
This is the repository for the Chatbox Community Edition, open-sourced under the GPLv3 license.
Chatbox is going open-source Again!
We regularly sync code from the pro repo to this repo, and vice versa.
Cool that they did that, but they could also start behaving properly. The app labels itself at GPL licensed, but the most recent releases are not available on GitHub. It's been the situation for quite a while now and it's been raised with the author a few times in the issues. They don't seem to care.
Cool that they did that, but they could also start behaving properly. The app labels itself at GPL licensed, but the most recent releases are not available on GitHub. It's been the situation for quite a while now and it's been raised with the author a few times in the issues. They don't seem to care.
Unless they have GPL dependencies I'm not sure they have to release source for a binary release. If I write some code and grant you a license to use it under the GPL, I would have thought I still am the copyright holder and don't need any kind of license to do whatever I want with it.
I have no idea of the legal implications of all this (I'm not a lawyer), but there has to be some kind of legal thing that prevents the original licensor from being unreasonable in this way, I'd hope?
Earlier quoted context omitted.
Unless they have GPL dependencies I'm not sure they have to release source for a binary release. If I write some code and grant you a license to use it under the GPL, I would have thought I still am the copyright holder and don't need any kind of license to do whatever I want with it.
My understanding is that the GPL specifies that any further redistribution of binary code (by the licensee) has to come with an offer to be able to receive the source code, which they can then modify and redistribute under the original license. If the original licensor doesn't actually allow access to the source code, there's no way for that to happen and I'd argue that the licensor is being unreasonable by asking li…
The license only binds the licensee that received the code under the respective license.
Things get more complicated if there are external contributors that may have contributed under specific legal arrangements, but in the simple case there’s no legal way to force the original copyright owner to publish sources.
Earlier quoted context omitted.
My understanding is that the GPL specifies that any further redistribution of binary code (by the licensee) has to come with an offer to be able to receive the source code, which they can then modify and redistribute under the original license. If the original licensor doesn't actually allow access to the source code, there's no way for that to happen and I'd argue that the licensor is being unreasonable by asking li…
The license does not bind the original copyright owner, who can do anything with the code - fee example relicense and distribute under another license. The license only binds the licensee that received the code under the respective license. Things get more complicated if there are external contributors that may have contributed under specific legal arrangements, but in the simple case there’s no legal way to force th…
For any small to medium sized projects with zero external contributors, it's highly unlikely that anyone would pursue legal action so the person who owns the project does de facto have this right whether or not it's legal according to the license.
> Things get more complicated if there are external contributors
I don't think this is complicated - unless there's a contributor agreement that people have signed that says otherwise, people have copyright on the code they have contributed so the original creator doesn't have a right to relicense their code.
However, again it comes down to whether anyone would bring a legal fight and the answer is almost certainly no. Forking the code is much more likely at that point.
Do I need to use the API key, or it uses my subscription?
Earlier quoted context omitted.
On average 90% of time spent on mobile devices is in native apps.
That's.. how is that relevant?
Users want apps and it’s important not to assume that the majority of users will think like HN users. Even if your app is mostly just a webview wrapping your website, being in the App Store matters.