Dan
Well-known member
He means he would like to see a configuration setting explicitly opting IN as opposed to having to add a setting opting OUT.Anyone know what Lawrence actually means by this?
He means he would like to see a configuration setting explicitly opting IN as opposed to having to add a setting opting OUT.Anyone know what Lawrence actually means by this?
Isn't the law in Canada just to do with spam, or is there some other law I don't know about?On a side note, it is illegal in Canada for any company to do this.
The people in question have said that they're happy with that by installing an add-on that necessitates that to provide the functionality and that clearly explains what will be sent.You can list all your add-ons you use or not, it is up to you.
You mean the add-on that is explicitly designed for checking whether you have add-ons that can be upgraded? The one whose explicit purpose is to use the data needed to provide the exact purpose that the people using it have asked for? It is opt in by definition of someone installing the add-on and it being explained on the resource page what data it collects.My concern is that a developer is dictating that his add-ons, if you choose to use them, will track specific data, and it is up to you to "opt out". On a side note, it is illegal in Canada for any company to do this.
Seriously? If you want your argument to be taken seriously, calling me some sort of racist is clearly not a good way to do it.What seriously concerns me, is that XenForo is alright with this, and by reading Mikes reply in another thread, he is not only is alright with this but endorses it. Why? Because Jon is from the UK?
The Canadian law is around opting users into behavior that they didn't initially sign up for. That doesn't apply here, the users signed up for the behavior when they initially installed the add-on. Again: they installed the add-on for this purpose.On a side note, it is illegal in Canada for any company to do this.
I don't really see any reason why you can't put that request in your resource listings, but you demanded it in your first post, and putting it in your license agreement is similarly blunt. Since it's likely unenforceable, I think you'd do better to just politely state your thoughts and request, and let users choose for themselves - since they'll be doing that anyway.What I am strongly requesting is that you respect my feelings on this
You're doing nothing here to protect privacy rights. At all.I respect a forum owners right to privacy, and no developer should be allowed to take that right from any forum owner.
This is utterly ridiculous.You want to use this add-on? Sure, go for it, that will be x dollars per year plus any information I choose to take from your site... don't worry, the add-on will do what you need it to do.. well until I decide you are not paying enough for it.
We are talking about one add-on, not a business model.While I don't agree with Jon's business model, it is his model and I don't have any say about how it works.
The other thread was referenced, that's the only reason I mentioned it.We are talking about one add-on, not a business model.
I requested the edit.Edit - Nice OP post edit mods, but you gotta admit the original deleted sentence is infact very true![]()
I wouldn't say that. There's a lot of bugs that I haven't yet had time to fix and really its method of collecting data is far from optimal to the point that @Mike will probably start docking my pay to cover all the bandwidth it sucks upNot sure why all the fuss, when Chris D's addon installer is far superior anyway. No fancy callbacks, no collection of data. Just does what it is supposed to. Bloatware be gone.
Perhaps add-on developers who don't want their add-on information sent to Waindigo servers can provide some sort of API that can be checked against for their add-ons?
it is what I will do to protect the privacy of my add-ons and those who choose to use them.
We use essential cookies to make this site work, and optional cookies to enhance your experience.