IMHO, since Chromium is an open source project would be nice if extensions were open source too. It wouldn't hurt nobody if extensions were released under free software license.
my 2 cents. Daniele S. 2009/12/16 PhistucK <phist...@gmail.com> > Alright, someone mentioned accessing manifest through > chrome://theme/manifest.json, I just added that you currently can also look > at the manifest of extensions through this path. > 2 cents, take it or leave it. > > Copyrighted material is still copyrighted material. Using it is illegal. Do > you really think it is an issue for someone to download an MP3 version of > any song they want? It is copyrighted material, but it is easily obtainable. > I am not sure mp3.com still works, but when it did, you could have just > downloaded the 'streaming mp3' by opening the playlist and get copyrighted > material, 128kbps MP3s, easily and for free. Illegal, but easy. > You can also disassemble any software and get into its guts. Java is even > easier. > Almost everything is easily obtainable. But between having it and actually > using it in an illegal way, there is a difference. > > ☆PhistucK > > > > On Wed, Dec 16, 2009 at 13:14, krtulmay <krtul...@gmail.com> wrote: > >> >See the manifest without going searching through the files. >> >> This answer makes no sense at all! >> >> If I am putting chrome-extension://<substitute_extension_id>/ >> manifest.json into the Omnibox, how do I get the extension ID? >> >> Firstly, I already had to go to chrome://extensions/ to look at the ID >> of the extension I am interested in. Secondly, I have to select and >> copy all 32 characters of the ID and then paste into the Omnibox just >> so I can craft a URL of the form chrome-extension:// >> <substitute_extension_id>/manifest.json. Thirdly, entering that URL >> into the Omnibox only results in saving the manifest.json, and I still >> have to open a file browser to go to the saved location before I can >> open to see the manifest.json. >> >> If I need to do all that, I might as well have my file browser already >> open to the ...\User Data\Default\Extensions\ directory, and after I >> get the extension ID from chrome://extensions/ just open that >> directory myself in the file browser and read the manifest.json. It's >> only one level lower inside the version number directory. Do you >> consider that to be "searching through the files" ? >> >> Or am I missing something that makes chrome-extension:// >> <substitute_extension_id>/manifest.json so much better? To me, >> viewing this in the Omnibox is just ridiculously slower. >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> "Chromium-extensions" group. >> To post to this group, send email to chromium-extensions@googlegroups.com >> . >> To unsubscribe from this group, send email to >> chromium-extensions+unsubscr...@googlegroups.com<chromium-extensions%2bunsubscr...@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/chromium-extensions?hl=en. >> >> >> > -- > You received this message because you are subscribed to the Google Groups > "Chromium-extensions" group. > To post to this group, send email to chromium-extensi...@googlegroups.com. > To unsubscribe from this group, send email to > chromium-extensions+unsubscr...@googlegroups.com<chromium-extensions%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/chromium-extensions?hl=en. > -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
