patrykcm
Forum Replies Created
-
About restrictions – implementing “features” like this is like eating garlic or pizza with pineapple on it in public transport – not restricted but shows lack of taste and you shouldn’t do this.
And about item 4 – Error not error, but there are testers who hasn’t caught it and pushing untesed software to production is a bit dangerous for reputation – i personally am a bit afraid.Thanks for approving.
1) yes i can deactivate plugin but when i click deactivate expected function of this button is to deactivate plugin, NOT showing an intrusive interstitial. Thats how 99,9% of plugins work after clicking deactivate button
2) Sure i can elaborate:
I may be biased towards privacy because i work for company where every outgoing connection from wordpress is blocked, laptops have disabled usb storage devices and etc.
Here problem is that part of data is diagnostic data and information about this data is clearly stated on privacy policy page – and with this i am ok. But… registration is required when using the API of the plugin, like in the SEO Analysis [and this analysis i mentioned in point 3 on other plugins is done on client side in plugin itself] – there is absolutely no information how this part of data is processed and what is stored and how it is analysed. They say registration is for preventing api abuse – i say to collect data and get email adress. If i wanted to abuse Api – i’d go to stackoverflow and get fist script which can register multiple accounts and query api with proxies so this argument is just stupid explanation.
3) The problem in this point is, that plugin is not an saas [this acronym have more correct name and it is Software As An extort Scam – and gives me headache like hit with a police baton – don’t ask]. Plugin is definitely not an saas but have some functions available by their api. Functions that other seo plugins do on client side (and also this plugin is not a “front for service” like in some plugins where services was created first and later they developed plugins for different cms)4) also – few updates ago there was unpleasant suprise where plugin made “whole WP broken” suprise – sure, it was avoidable by cleaning server cache (like nginx cache) but still – big change, unexpected problems.
- This reply was modified 7 years, 4 months ago by patrykcm.