Dollar had purchased, very long.
ThemeProvince saidLike I said, I’ve no problems paying my taxes…. I’m just not sure how this works as Envato has yet to point me towards a Tax Form they way other sites do which is part of my main question?
Hire an accountant or pay full tax rate
Dreamstime is based Nashville,TN, US companies normally pay out affiliate cash with either tax withholding or requiring you to fill out a form. Envato is more offshore than that, it’s not an American company.
I like giving support, and I like that it’s up to me to give support. I like going the extra mile 99% of the time. Assuming I don’t care about 1 stars: if support became mandatory I’d feel the need to refuse service to certain buyers. Actually it is a right. In democracy no one can take your rights away. So if support becomes mandatory you can still just refuse service to anyone, even everyone?
It’s not worth risking a soft disable.
After a second thought, I came to the same conclusion. I’ll push out the update later today.Thanks for your tip that you can use the App ID + Secret as the access token!
FYI source: https://developers.facebook.com/docs/facebook-login/access-tokens
“App Tokens” paragraph.
There is another method to make calls to the Graph API that doesn’t require using a generated app token. You can just pass your app id and app secret as the access_token parameter when you make a call:
http://graph.facebook.com/endpoint?key=value&access_token=app_id|app_secretThe choice to use a generated access token vs. this method depends on where you hide your app secret.
I’m okay with this, but:
Most buyers already thought that support comes with the purchase, so this wouldn’t change much. DS not every purchase comes with a buyer that needs 1 hour support. This is the same analogy of Flickr giving everyone 1TB space, Crashplan giving unlimited backup space: only a minority of buyers you’ll end up having a conversation with, over 1 hour, let alone exchange 1 message in the first place. It’s the cost of doing business and think of it as a 1-2 hour “different” thing to do every day. I’m wondering if we hire someone to do support, what’s an acceptable way of measuring work and paying them?
What if someone decides that they still want to provide lifetime free support (and no buyer in their right mind will blow the wistle – “hey I received free support after 6 months, what the hell”), to gain advandate over those that obey the 6 month rule? The author could either do this deliberately or just because they forgot to give a sh!t and check purchase times.
What will keep people from setting up their own support packs on their own site for sale, after the 6 months? Would this be covered in the exclusivity agreement that you can only see support packs via the system in place?
How will the support pack’s price be set? For busy theme authors with lots of themes the hourly price of extra support would probably be much higher than usual (as time is money) as there will be a large demand for this.
Can I just send off anyone (even required to) after 6 months telling them to buy the support pack if they want any kind of answer via email or comments?
How am I supposed to know of a buyer in the item comments when did they buy the product?
Also in the email I get, I can only see the purchase time if I click on the verification link.
What if someone purchased the product 1 year ago then purchased it again 1 week ago. Do they get new 6 month support? What if they require assistance on the first purchase or a problem regarding their first usage, first site. Does a new purchase renew support? It’ll be a bit awkward.
I believe to make things simpler it should work like this: 6months mandatory. After 6+ you can decide if you still want to provide free support OR send the buyer off to buy support pack OR no support whatsoever (disabling ability to buy packs).
[...] but it doesn’t mean you as a developer can keep using v1 in the latest version.
I sure do understand that. And of course, with each regular update I would have made sure to accommodate for all changes made to the API, etc.However, I was just wondering if I have to release a hotfix update that just changes the Facebook API part right now, or if I could’ve waited for the next planned feature update to make the required changes.
It’s not worth risking a soft disable. If you have to, release a hotfix only because of this. If you already have some progress toward your next update, include that too.
Do I have to update the plugin and thus force users to create an App over at Facebook unnecessarily only to comply with the new rules?
That’s what I did, no one complained so far.
Yeah you’ll need your users to create an app for that because: http://graph.facebook.com/v2.0/envato but you an just use api code and secret combined as a valid token, no need for further authentication steps.
While it may seem easier to create an app yourself and embed the token in the product, don’t do that as you are not supposed to give them out in any form  AND you are not responsible for how people use your product. Having one official app for your product would be something like a shared hosting, if anyone abuses FB api with your access data, your app could come down and crippling it for everyone. Creating an app is relatively easy for your buyers and they don’t need to go though verification for a public app as they are the only ones who will use it.
I strongly believe this thread applies to you too. The change is happening because there is a usualy time that takes everyone or a large enough percentage of users to update in time. E.g. if the deadline was dec 31, then e.g. 20% of users would still use your product by the time v1 api goes down = more frustration. If you do the update now, only like 3% of users would be using an old version next year.. Or something similar
Just make a note for existing buyers that this change is a breaking update. Then, if they conscously choose that, can keep using the old product until the api goes down (and it will), but it doesn’t mean you as a developer can keep using v1 in the latest version.
If you still manage hit the API limits with caching and pre-validation you can create multiple API keys and juggle them.