I have undeleted them for you @digitalpoint.
Thanks... I believe everything should be "disclaimed" properly under the new guidelines now.I have undeleted them for you @digitalpoint.
Just out of curiosity, what sort of scenario could you see where *anything* an addon developer does/doesn't do causes you to lose years of work and data?Someone goes off the deep end and we lose years of work, data, or both?
Suggestion for the addition of a #6, something like;we have published a set of guidelines that all resources listed on XenForo.com must adhere to
While I understand the concern, I don't understand the logic.Where can I submit a request that resources list external activity yes/no on at the top of the resource page, under "Visible Branding"?
Someone goes off the deep end and we lose years of work, data, or both? It's just not possible to reliably vet and track each add-on developer.
Many of us don't feel comfortable with external calls, period.
Just out of curiosity, what sort of scenario could you see where *anything* an addon developer does/doesn't do causes you to lose years of work and data?
While I understand the concern, I don't understand the logic.
External calls would not necessarily be the cause of losing work/data. Any code, written by any author can be the cause. But for an author to do that would mean a complete loss of credibility and an instant death in the add-on world.
Could I or any other author write malicious code? Yes.
Would I? No.
A callback to read something is different than downloading code to execute (which I think is what you are worried about, and also not allowed ever).I may be mistaken, and please let me know if I am. It seems add-ons which include server call(s) could allow them to do something impulsively, effecting past installs. I don't think any add-on is worth the possibility of someone having or gaining access to our systems, possibly without our knowledge.
Executable code (such as PHP or SQL) cannot be downloaded by your add-on unless explicitly requested by the user, as a core function of your add-on. For the avoidance of doubt, your installation or uninstallation routines must not download code to execute.
A callback to read something is different than downloading code to execute (which I think is what you are worried about, and also not allowed ever).
https://xenforo.com/community/help/resource-guidelines/
Resource authors should audit their listings to ensure they meet this.If your resource displays a visible copyright or branding message by default, this must be disclosed in the resource listing. There is a dedicated field to specify this.
Template Modifications category does not have the Visible Branding selection.This should have been clear, but to make it explicit, we have added a new line to the resource guidelines:
Resource authors should audit their listings to ensure they meet this.
I believe this treatment is needed for item #3 too - "Any price listed for your resource must accurately reflect the price paid without taking any other steps (such as enrolling in a subscription service)."This should have been clear, but to make it explicit
We'll consider changing that, though I would suggest that the purpose of that category essentially means that branding isn't something we would suggest should be done with what's in it. The purpose is either tutorials for changing a template or an add-on that is using template modifications (and nothing or very little else) to achieve their goal. If you're powering this with a reasonable amount of PHP code or extended custom UI stuff (options), it's probably not the right category.Template Modifications category does not have the Visible Branding selection.
Worth pointing out that the line you quote was related to a situation that was happening at the time (and still does happen): resources were being listed as free, but they could not be accessed (downloaded) without purchasing a subscription which allowed access to a collection of things. When the resource itself is free but requires payment to a third-party, it's a grey area and something that might need to be considered on a case-by-case basis.I believe this treatment is needed for item #3 too - "Any price listed for your resource must accurately reflect the price paid without taking any other steps (such as enrolling in a subscription service)."
Several add-ons are coming through that are free/unpaid to download/install, but are useless without a monthly subscription service.
We use essential cookies to make this site work, and optional cookies to enhance your experience.