6 ms·

I'm of two minds about this. "Stealing" does seem to be a little too harsh given the plugin did say it would take a percentage if you make more than $1K and did

I'm of two minds about this. "Stealing" does seem to be a little too harsh given the plugin did say it would take a percentage if you make more than $1K and didn't buy a license. The 30% seems underhand (only because it's not spelled out in the repo) but I do understand the plugin author's position. Open source work, especially something like Ionic/Cordova/Capacitor plugins, are hard to make any money on and I've seen the GH issues for many cordova plugins, it's /rough/. Also there are so many things you need to support and edge cases that I can't even imagine the patience of someone maintaining one of those plugins. I think it's clear the plugin author was/is happy to let the 2-30% stipulation fly under the radar and sit back and collect which doesn't sit great with me but also I kind of get it. I mean if you are going to take OS work and use it for your own gain (something I'm plenty guilty of myself I'll admit) then don't be surprised if not reading the license bites you in the butt. In a perfect world OS devs wouldn't need to these methods to make it worth their time but we don't live in a such a world, people rarely donate to OS projects and expect issues/features to be added quickly and for free. People need money to exist and they don't owe you anything. Honestly if this plugin author had called out the 30% in their license I would say this blog author has no leg to stand on. As-is I'm glad the app developer got their money back and the plugin author should either stop charging more than 2% or update their license accordingly. But "stealing"? Too harsh, especially since you got your money back.

NKosmatos 5y ago
Yes, a good point. He should update the license (https://github.com/floatinghotpot/cordova-admob-pro/wiki/License-Agreement https://github.com/floatinghotpot/cordova-admob-pro/wiki/Lic...) to state from 2% up to 30%.
Beltalowda 5y ago
I suspect the line of thinking behind the 30% seems to be something along the lines of "they're fiddling their numbers to reduce our 2% cut, so let's just take a bigger cut". I don't think this is entirely kosher for a bunch of reasons, but I'm willing to believe that it was a naïve person doing something naïve after being burned by someone cheating him out of his cut, or something along those lines. At any rate, since the author of this article was unaware of the 2%, it doesn't really matter if the 30% would have been mentioned or not. That they took any cut could have been clearer, perhaps – I don't know how it looked like before on that Ionic plugin site, but it's plenty clear now so that's a solved issue (if it was an issue to start with). That this was added after this exchange (and before it was published) without any pressure further demonstrates the plugin author is essentially acting in good faith.
- yesimahuman 5y ago
  (Ionic CEO here) I think regardless, it's something developers don't expect so we're removing it from our site right now to avoid confusion and surprises (we’re going to be changing the whole design of this list soon anyways so it’s moot). The plugin description came from another project we support and trust plugin authors to write their own descriptions but we're realizing we need to scrutinize those more closely. I have no qualms with a plugin stating they are going to have this kind of revenue share but it doesn't belong on our site and seen as “official” which is confusing, so we're fixing that right now.
  - putlake 5y ago
    The plugin author seems like a standup guy who responded cordially and even returned money, which is something no scammer would ever do. Your platform, your rules. But I feel you're being unfair to him with this knee-jerk reaction.
    - yesimahuman 5y ago
      Unfair to the plugin author? It's moot anyways because we're making a design change to the site and changing how we reference community plugins. We aren't stopping developers from finding and using whatever plugin they want to use, just changing how "official" they look on our website.
  - rat9988 5y ago
    You shouldn't overreact this way. Really it doesn't speak well of your platform.
    - Ansil849 5y ago
      I feel like their response is not at all an overreaction. The plugin author was underhanded in their conduct. I wouldn't want to use a platform which allowed nonsense like that to proliferate, so am happy to see dubious stuff like this removed. To me it signals that the platform owners care about what is on their platform and are concerned about their users. That is a good thing.
Kvirkvelia 5y ago
I would love to see open source developers make a lot of money; I think it's a great future for everyone. But I don't think there is any dichotomy in this case. If the service declares its price in percentages or dollars (as SaaS does), it's terrible to charge 15 times more. Mistakes happen, but in this case, it's a conscious decision by the plugin author; I think stealing is the right word, especially when it turns out you've done it with thousands of apps

NKosmatos 5y ago

Yes, a good point. He should update the license (https://github.com/floatinghotpot/cordova-admob-pro/wiki/License-Agreement https://github.com/floatinghotpot/cordova-admob-pro/wiki/Lic...) to state from 2% up to 30%.

Beltalowda 5y ago

I suspect the line of thinking behind the 30% seems to be something along the lines of "they're fiddling their numbers to reduce our 2% cut, so let's just take a bigger cut". I don't think this is entirely kosher for a bunch of reasons, but I'm willing to believe that it was a naïve person doing something naïve after being burned by someone cheating him out of his cut, or something along those lines. At any rate, since the author of this article was unaware of the 2%, it doesn't really matter if the 30% would have been mentioned or not. That they took any cut could have been clearer, perhaps – I don't know how it looked like before on that Ionic plugin site, but it's plenty clear now so that's a solved issue (if it was an issue to start with). That this was added after this exchange (and before it was published) without any pressure further demonstrates the plugin author is essentially acting in good faith.

yesimahuman 5y ago
(Ionic CEO here) I think regardless, it's something developers don't expect so we're removing it from our site right now to avoid confusion and surprises (we’re going to be changing the whole design of this list soon anyways so it’s moot). The plugin description came from another project we support and trust plugin authors to write their own descriptions but we're realizing we need to scrutinize those more closely. I have no qualms with a plugin stating they are going to have this kind of revenue share but it doesn't belong on our site and seen as “official” which is confusing, so we're fixing that right now.
- putlake 5y ago
  The plugin author seems like a standup guy who responded cordially and even returned money, which is something no scammer would ever do. Your platform, your rules. But I feel you're being unfair to him with this knee-jerk reaction.
  - yesimahuman 5y ago
    Unfair to the plugin author? It's moot anyways because we're making a design change to the site and changing how we reference community plugins. We aren't stopping developers from finding and using whatever plugin they want to use, just changing how "official" they look on our website.
- rat9988 5y ago
  You shouldn't overreact this way. Really it doesn't speak well of your platform.
  - Ansil849 5y ago
    I feel like their response is not at all an overreaction. The plugin author was underhanded in their conduct. I wouldn't want to use a platform which allowed nonsense like that to proliferate, so am happy to see dubious stuff like this removed. To me it signals that the platform owners care about what is on their platform and are concerned about their users. That is a good thing.

Kvirkvelia 5y ago

I would love to see open source developers make a lot of money; I think it's a great future for everyone. But I don't think there is any dichotomy in this case. If the service declares its price in percentages or dollars (as SaaS does), it's terrible to charge 15 times more. Mistakes happen, but in this case, it's a conscious decision by the plugin author; I think stealing is the right word, especially when it turns out you've done it with thousands of apps