search

joelpt / sidewise

Persistent sidebar extension for Chrome featuring tree style tabs and tab hibernation.
Creative Commons Zero v1.0 Universal
68 stars 13 forks source link

chrome web store policy #90

Open Dboingue opened 2 years ago

Dboingue commented 2 years ago

anyone knows why google took disabled this extension with the "This extension violates the Chrome Web Store policy." stamp?

I think this extension does fill a vertical need that 16:9 ratios combined with lots of wasted vertical space ergonomics has created (think of ribbons, forced tab horizontal layout waste, etc... ).

I find that this recent wave of disabled extensions (which is not the malware invocation btw) is more about web store policy change, than a sudden increase in violations. maybe that is obvious.

anybody knows about what changed, and if the violations are about privacy or security or Else. if Else, then i would start looking for ways to work around. if not else, then any detail known. since the source code is here, maybe somebody has some clue.

I wish the disabling message had some specification and references so we would know the nature of the web store policy obstacle from the user end.

Security is important and not to be used for marketing of features or design choices. So vague claims that could insinuate security or privacy policy related violations should be made precise for us to trust future messages of that nature. otherwise this is cultivating widespread cynicism.... and legitimate concern might be shoved off as corporate speak.

joelpt commented 2 years ago

Here is the reason Google provided:

Violation: Not handling user data in a secure manner "Transmitting over http" How to rectify: Ensure secure transmission of user data.

Most likely this has to do with its ability to do (voluntary, on user demand) log file uploads to http://sidewise.info.

NorseGaud commented 2 years ago

I had originally asked Joel to make this open source thinking that I'd have time to help solve some of these things to get it back into the Web Store, but alas, life happened.

@joelpt , in your mind what would be necessary for you to accomplish this? Is it money, time, etc? I would be more than happy to drive some donations to the project so that the tool gets back into a publishable state (removing the log file uploads feature/code). Or, if you definitely don't want to do anything with it, maybe we could pool some money to hire someone?

I use this tool daily and will continue to do so until it's completely blocked, so for me donating is easy.