<div dir="ltr"><div><br></div><div>Another idea might be to add some sort of module to the main repository containing information about the primary Sword frontends. This would be helpful information for users and app developers that have added value into their clones. However, if an app has merely included adverts and changed an image then this would be a way to make that app's users realise they don't need to put up with ads while they read their Bible.</div><div><br></div><div>It would also provide publicity for the various Sword front ends. Many And Bible users are unaware of the Sword family of applications. App thieves could always block the module, but if the module name changed occasionally then it would be more difficult. App thieves would probably not be willing to create their own repository of modules.</div><div><br></div><div>Martin</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 22 April 2015 at 16:31, Peter Von Kaehne <span dir="ltr"><<a href="mailto:refdoc@gmx.net" target="_blank">refdoc@gmx.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:Verdana;font-size:12.0px"><div>
<div>
<div>I think licenses are exactly that - sticks to stop people doing something you do not want them doing. Many licenses are very tight as the authors do not like their users to do anything really but the most circumscribed things, but this is a place where the GPL bites and I would say, go fo it.</div>
<div> </div>
<div>Peter</div>
<div> </div>
<div> </div>
<div name="quote" style="margin:10px 5px 5px 10px;padding:10px 0 10px 10px;border-left:2px solid #c3d9e5;word-wrap:break-word">
<div style="margin:0 0 10px 0"><b>Gesendet:</b> Mittwoch, 22. April 2015 um 15:04 Uhr<br>
<b>Von:</b> "Jonathan Morgan" <<a href="mailto:jonmmorgan@gmail.com" target="_blank">jonmmorgan@gmail.com</a>><br>
<b>An:</b> "JSword Developers Mailing List" <<a href="mailto:jsword-devel@crosswire.org" target="_blank">jsword-devel@crosswire.org</a>><br>
<b>Betreff:</b> Re: [jsword-devel] [And Bible] Clones of And Bible with adverts</div><div><div class="h5">
<div name="quoted-content">
<div>
<div>
<div>
<div>Hi Peter,<br>
</div>
I'm aware of the context, and that's precisely my objection.</div>
I don't like licenses being used as a big stick to hit people with when the objection is actually over something else, not over the license.<br>
</div>
Jon</div>
<div class="gmail_extra">
<div class="gmail_quote">On Wed, Apr 22, 2015 at 4:46 AM, Peter von Kaehne <span><<a href="http://refdoc@gmx.net" target="_blank">refdoc@gmx.net</a>></span> wrote:
<blockquote class="gmail_quote" style="margin:0 0 0 0.8ex;border-left:1.0px rgb(204,204,204) solid;padding-left:1.0ex">The subject of the thread is how to stop the advertising clones. This is therefore not about how to enforce GPL compliance, but how to use non compliance.<br>
<br>
There are a couple of clones i would consider genuine and decent. People have slapped their church logo on it and distribute it with their own resources. Compliance mamagement would be appropriate.<br>
<br>
But Martin does not seem to be worried about these, but is concerned about rip off ad sellers, possibly distributing illicit bible copies. Harsh approaches here seem appropriate.<br>
<br>
<span><font color="#888888">Peter</font></span>
<div>
<div><br>
On 21 Apr 2015 14:24, Jonathan Morgan <<a href="http://jonmmorgan@gmail.com" target="_blank">jonmmorgan@gmail.com</a>> wrote:<br>
><br>
> Hi Peter,<br>
><br>
> That's the reasoning that said "Apple AppStore is non-GPL compliant". From memory, plenty of pragmatic people kept releasing GPL apps on the AppStore anyway.<br>
> Generally, you shouldn't expect a binary distribution channel to be geared towards source distribution (and most users don't want it to be). So long as the source is made available elsewhere in some form I think most people will accept it.<br>
><br>
> GPLv2 was written in a different world. As software developers, we complain about laws from 20+ years ago (often telecommunications) being applied to the Internet as it is now, because the world has changed. I think the same applies to GPL v2. I suspect plenty of projects obey the spirit but not the letter of the license, and AndBible itself might be one (it's not clear to me from the App Store what license it is other than "open source" - though the Google Code page seems to say LGPL. Nor would I say there is a clear "offer" on the App Store or in the program itself that I could see).<br>
><br>
> Give these other distributors a chance to comply and provide source (in the same way as you would give Martin a chance to comply if you thought he was not meeting the letter of the license). If they don't, then throw the book at them for a genuine offence against the spirit of the license.<br>
><br>
> Jon<br>
><br>
> On Tue, Apr 21, 2015 at 4:08 PM, Peter von Kaehne <<a href="http://refdoc@gmx.net" target="_blank">refdoc@gmx.net</a>> wrote:<br>
>><br>
>> It is not so simple. The code must be clearly offered. If it is not then there is a breach. As we talk about shut down a breach, any breach is sufficient.<br>
>><br>
>> Peter<br>
>><br>
>> On 21 Apr 2015 02:38, "Trenton D. Adams" <<a href="http://trent@trentonadams.ca" target="_blank">trent@trentonadams.ca</a>> wrote:<br>
>> ><br>
>> > Not true, GPL does not imply that they must post code publicly. However, if a user requests the code, it MUST be given to them. So, just request it be given, and you can post it.<br>
>> ><br>
>> > TV manufacturers do this all the time, because they really don't want to share the code. But, they are required to give it to any user that asks for it.<br>
>> ><br>
>> > On 2015-04-19 5:43 PM, DM Smith wrote:<br>
>> >><br>
>> >> Martin,<br>
>> >> Makes me quite angry.<br>
>> >><br>
>> >> Assuming AndBible is GPL. If they modify any part of it they are obligated to post the software. I suggest asking them for their fork of the code. It has to be public. If they don’t, complain to Google that they are violating the license agreement and ask for a takedown on that basis.<br>
>> >><br>
>> >> If they do that, they are free to fork and even make money with it. (I don’t like that aspect of GPL.)<br>
>> >><br>
>> >> The GPL is a distribution license, not governing copyright. The GPL does protect copyright. You’ll want a clear copyright statement in each and every file.<br>
>> >><br>
>> >> Assuming you are the sole author (e.g. code and resources/translations), then as the sole copyright owner of AndBible (not JSword) you can change your license to anything of your choice. It won’t be retroactive. I’m not recommending that, though.<br>
>> >><br>
>> >> I looked at a few of these and it appears that they rip off lots of other programs as well. Not sure how to track down the original owners, but having a joint effort may be of help.<br>
>> >><br>
>> >> Couple of thoughts:<br>
>> >> Have a build time attribute that is manually entered, that does one or more of the following:<br>
>> >> - disables a random timer (or event counter) that causes a program crash/exit without warning.<br>
>> >> - disables a random timer that causes a screen declaring that the program has been ripped off from AndBible.<br>
>> >> - show credits, copyright and license when the program is opened for the first time each upgrade.<br>
>> >> Get everyone you know to leave one star reviews for these apps, declaring them an rip-off (Just like Peter did).<br>
>> >><br>
>> >> Use an obfuscator to make the code that does such a thing impossible to read and hard to reverse engineer. Check it in and appropriately copyright it and license it. Make it such that if it is not called that the program doesn’t work.<br>
>> >><br>
>> >> In Him,<br>
>> >> DM Smith<br>
>> >><br>
>> >>> On Apr 19, 2015, at 5:30 PM, Peter von Kaehne <<a href="http://refdoc@gmx.net" target="_blank">refdoc@gmx.net</a>> wrote:<br>
>> >>><br>
>> >>> DMCA takedown dt licence breach?<br>
>> >>><br>
>> >>> On 19 Apr 2015 21:38, Martin Denham <<a href="http://mjdenham@gmail.com" target="_blank">mjdenham@gmail.com</a>> wrote:<br>
>> >>>><br>
>> >>>> I have been informed of various clones of And Bible on Play Store and other stores with the only addition being adverts, occasionally copyrighted Bibles like NIV, and other oddities like misleading pictures on the Play Store page.<br>
>> >>>><br>
>> >>>> Has anybody got any suggestions what to do about these.<br>
>> >>>><br>
>> >>>> Here are a couple:<br>
>> >>>> <a href="https://play.google.com/store/apps/details?id=com.ayatalkitab.harian" target="_blank">https://play.google.com/store/apps/details?id=com.ayatalkitab.harian</a><br>
>> >>>> <a href="https://play.google.com/store/apps/details?id=com.ian.holybible.android" target="_blank">https://play.google.com/store/apps/details?id=com.ian.holybible.android</a><br>
>> >>>> <a href="https://play.google.com/store/apps/details?id=com.happydev.bible" target="_blank">https://play.google.com/store/apps/details?id=com.happydev.bible</a><br>
>> >>>><br>
>> >>>> Martin<br>
>> >>>><br>
>> >>>><br>
>> >>>><br>
>> >>>> --<br>
>> >>>> You received this message because you are subscribed to the Google Groups "And Bible" group.<br>
>> >>>> To unsubscribe from this group and stop receiving emails from it, send an email to <a href="http://and-bible%2Bunsubscribe@googlegroups.com" target="_blank">and-bible+unsubscribe@googlegroups.com</a>.<br>
>> >>>> For more options, visit <a href="https://groups.google.com/d/optout" target="_blank">https://groups.google.com/d/optout</a>.<br>
>> >>><br>
>> >>> _______________________________________________<br>
>> >>> jsword-devel mailing list<br>
>> >>> <a href="http://jsword-devel@crosswire.org" target="_blank">jsword-devel@crosswire.org</a><br>
>> >>> <a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
>> >><br>
>> >><br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >><br>
>> >> jsword-devel mailing list<br>
>> >><br>
>> >> <a href="http://jsword-devel@crosswire.org" target="_blank">jsword-devel@crosswire.org</a><br>
>> >><br>
>> >> <a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
>> >><br>
>> ><br>
>> _______________________________________________<br>
>> jsword-devel mailing list<br>
>> <a href="http://jsword-devel@crosswire.org" target="_blank">jsword-devel@crosswire.org</a><br>
>> <a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
><br>
><br>
_______________________________________________<br>
jsword-devel mailing list<br>
<a href="http://jsword-devel@crosswire.org" target="_blank">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a></div>
</div>
</blockquote>
</div>
</div>
_______________________________________________ jsword-devel mailing list <a href="mailto:jsword-devel@crosswire.org" target="_blank">jsword-devel@crosswire.org</a> <a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a></div>
</div></div></div>
</div>
</div></div></div>
<br>_______________________________________________<br>
jsword-devel mailing list<br>
<a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
<br></blockquote></div><br></div>