znetlive - Slashdot User

Comment stop using the same passwords in other sites (Score 1) 1

by znetlive on Tuesday October 06, 2015 @02:12AM (#50668023) Attached to: When nobody cares about an insecure website, what can I do?

Big sites are not immune to such concerns but there are many websites out there which are storing passwords inaccurately. I highly doubt when some businesses email the passwords to the clients in plain text. What we can do is only to start a protest and stop using such sites. And also immediately stop using the same passwords in other sites.

Comment Dead Links in Wikipedia (Score 1) 146

by znetlive on Wednesday September 09, 2015 @09:26AM (#50485929) Attached to: Wikipedia Blocks Hundreds of Accounts Doing Paid Editing

I have noticed there are so many resource links are dead links which is not removed by wikipedia. Need to re work on it. as now days people are trying to add there websites link in related Wikipedia pages for seo purpose.

Comment Easy to edit wikipedia (Score 1) 146

by znetlive on Wednesday September 09, 2015 @09:19AM (#50485865) Attached to: Wikipedia Blocks Hundreds of Accounts Doing Paid Editing

Now days its easy to edit wikipedia pages.

Submission + - When GPL becomes Almost GPL - The CSS, Images and Javascript Loophole.

Submitted by sobolwolf on Wednesday June 26, 2013 @09:57AM

sobolwolf writes: It has been apparent for sometime that many developers (mainly theme designers) are split licensing PHP based Based GPL distributions, releasing proprietary files alongside GPL files with the excuse that CSS, Javascript and Images are "immunized" from the GPL due to the fact that they run in the browser and not on the server. This is almost always done to limit the distribution of the entire release, not just the proprietary items (most extensions will not function in any meaningful way without the accompanying CSS, Images and Javascript). Some of the more popular PHP based GPL projects like WordPress have gone as far as to apply sanctions to developers distributing split licensed themes/plugins while others such as Joomla have openly embraced the split licensed model, even to go as far as changing their extension directory submission rules to cater specifically to split licensed distributions.

In light of all this I would like to ask the following question: While it seems to be legal to offer split licensed GPL distributions, is it in the spirit of the GPL for a project such as Joomla (who's governing body has the motto "Open Source Matters") to openly embrace such a practice when they can easily require that all CSS, Images and Javascript be GPL (or GPL compatible) for extensions that are listed on the Joomla Extensions Directory?

Slashdot Top Deals