Re: Wget for MP3 streams
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Ginger wrote: > On Friday 30 November 2007 01:03:06 Micah Cowan wrote: >> David Ginger wrote: >>> What I'm looking at wget for is saving streamed mp3 from a radio station, >>> crazy but true.. such is life. >> Isn't that already possible now? Provided that the transport is HTTP, >> that is? > > Yes and No . . . > > Yes I can save a stream, > > But, not everything works as expected, some of wget's features kick in. > > Like, I cant get the quota to work no matter how much I fiddle and tinker. Not too surprising, since the documentation points out that the quota never affects the downloading of a single file. :\ - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHT4XN7M8hyUobTrERArmZAJ4kY1KrbxZIupOuku348q1rydzj8wCfQ53H UndgZwl089jS5WtDxgtASL0= =Ecc6 -END PGP SIGNATURE-
Re: Wget for MP3 streams
On Friday 30 November 2007 01:03:06 Micah Cowan wrote: > David Ginger wrote: > > What I'm looking at wget for is saving streamed mp3 from a radio station, > > crazy but true.. such is life. > > Isn't that already possible now? Provided that the transport is HTTP, > that is? Yes and No . . . Yes I can save a stream, But, not everything works as expected, some of wget's features kick in. Like, I cant get the quota to work no matter how much I fiddle and tinker.
Re: Wget Name Suggestions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alan Thomas wrote: > How about: > -- "JustGetIt"? > --"GoFetch"? > --"SuckItUp"? > -- "Hoover"? > -- "DragNet"? > -- "NetSucker"? Feel free to add those to the Wiki page. I'd prefer short simple names, though. And I'm not a fan of CamelCase (the actual command-line tool should, in particular, not require use of the shift key in typing the name). - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHT3ff7M8hyUobTrERAsSkAJ9LZKiCmBTHH0WTuaBuaFeY3Ojw7ACdFVzX iLSZPgU7ZBl+fV+4i/kWnss= =zQ9u -END PGP SIGNATURE-
Re: wget2
On 11/29/07, Alan Thomas <[EMAIL PROTECTED]> wrote: > Sorry for the misunderstanding. Honestly, Java would be a great language > for what wget does. Lots of built-in support for web stuff. However, I was > kidding about that. wget has a ton of great functionality, and I am a > reformed C/C++ programmer (or a recent Java convert). But I love using > wget! I vote we stick with C. Java is slower and more prone to environmental problems. Wget needs to be as independent as we can possibly make it. A lot of the systems that wget is used on (including mine) do not even have Java installed. That would be a HUGE requirement for many people.
Re: Wget Name Suggestions
How about: -- "JustGetIt"? --"GoFetch"? --"SuckItUp"? -- "Hoover"? -- "DragNet"? -- "NetSucker"?
Re: Wget Name Suggestions
On 11/29/07, Micah Cowan <[EMAIL PROTECTED]> wrote: > A new discussion page on the wiki: > > http://wget.addictivecode.org/Wget2Names > > (Does it sound a bit too much like something that extracts names from > wget output? :) ) I really like the name `fetch` because it does what it says it does. It's more UNIX-like than the other names :-)
Wget Name Suggestions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new discussion page on the wiki: http://wget.addictivecode.org/Wget2Names (Does it sound a bit too much like something that extracts names from wget output? :) ) - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHT3Kf7M8hyUobTrERAvl0AJ9f8HOMTNDVrHQKvS/afFGU4rhQCgCdEz4X 2sTiYMiSoQSbobCFLjsKz1s= =fRdV -END PGP SIGNATURE-
Re: wget2
Sorry for the misunderstanding. Honestly, Java would be a great language for what wget does. Lots of built-in support for web stuff. However, I was kidding about that. wget has a ton of great functionality, and I am a reformed C/C++ programmer (or a recent Java convert). But I love using wget! Alan
Re: .1, .2 before suffix rather than after
On 11/29/07, Micah Cowan <[EMAIL PROTECTED]> wrote: > Yeah... of course they won't be able to edit the wiki that way. I doubt you'd get the slashdot effect from just the people who're interested in editing the wiki. You may get a handful of developers and a few thousand people who only want to read it :-)
Re: .1, .2 before suffix rather than after
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Josh Williams wrote: > On 11/29/07, Micah Cowan <[EMAIL PROTECTED]> wrote: >> Well, the trouble with that is that I'm running all of Wget's stuff >> (plus my own personal mail and whatnot) on a little VPS. I'm rather >> concerned that the traffic will kill me. I'm already worried about it >> potentially hitting SlashDot or Digg because it's the first Wget release >> in quite a while. D: > > Tada! http://en.wikipedia.org/wiki/Coral_Content_Distribution_Network > > There's also archive.org. Yeah... of course they won't be able to edit the wiki that way. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHT24z7M8hyUobTrERAprHAJ4gCaeiel8UPINXAa2wiept/ZsvFwCeLy0f 7SLzgXI6Jzcgmyy6GpyMH7k= =MZaQ -END PGP SIGNATURE-
Re: .1, .2 before suffix rather than after
On 11/29/07, Micah Cowan <[EMAIL PROTECTED]> wrote: > Well, the trouble with that is that I'm running all of Wget's stuff > (plus my own personal mail and whatnot) on a little VPS. I'm rather > concerned that the traffic will kill me. I'm already worried about it > potentially hitting SlashDot or Digg because it's the first Wget release > in quite a while. D: Tada! http://en.wikipedia.org/wiki/Coral_Content_Distribution_Network There's also archive.org.
Re: .1, .2 before suffix rather than after
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Josh Williams wrote: > On 11/29/07, Micah Cowan <[EMAIL PROTECTED]> wrote: >> I dunno, man, I think our current wget2 roadmap goals are already pretty >> wild-and-crazy. ;) > > I agree. I think we should create an announcement asking for > developers to help and submit it to digg and slashdot. The new > features may get some excitement going and start rumors. :-P > > ^^ in all seriousness ^^ Well, the trouble with that is that I'm running all of Wget's stuff (plus my own personal mail and whatnot) on a little VPS. I'm rather concerned that the traffic will kill me. I'm already worried about it potentially hitting SlashDot or Digg because it's the first Wget release in quite a while. D: - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD4DBQFHT2vG7M8hyUobTrERAiOAAJd6Htrtd2i9oxjJoK5ww+DFafzkAJ4lSiJR qtT8LHghRuxYlkcdznnlmQ== =ddEY -END PGP SIGNATURE-
Re: wget2
On 11/29/07, Micah Cowan <[EMAIL PROTECTED]> wrote: > Well don't look at _me_; I'm not the one who brought it up! ;) heh. I wasn't looking for some grand unveiling. It just seems that it seems to be attracting a lot of attention, and we should probably start putting more effort into it. I'm going to re-read some of the current Wget code tonight and start playing around with my own attempts of a wget2. I think we should simplify the name for this release to something like the `fetch` command (which is available, btw ;-).
Re: .1, .2 before suffix rather than after
On 11/29/07, Micah Cowan <[EMAIL PROTECTED]> wrote: > I dunno, man, I think our current wget2 roadmap goals are already pretty > wild-and-crazy. ;) I agree. I think we should create an announcement asking for developers to help and submit it to digg and slashdot. The new features may get some excitement going and start rumors. :-P ^^ in all seriousness ^^
Re: wget2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Josh Williams wrote: > On 11/29/07, Micah Cowan <[EMAIL PROTECTED]> wrote: >> - Alan has prior history on this list. Check the archives: > > yeah, I remember him. And is it just me, or does it seem that > something's going to go down tonight with wget 2? ;-) Well don't look at _me_; I'm not the one who brought it up! ;) - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHT2pZ7M8hyUobTrERAqRdAJ9Kn5c0Ik6tbBmm5cddaCX74GhJPwCgkou2 wQ8xmM6cDbxmT25BQ00bpT4= =Aa2u -END PGP SIGNATURE-
Re: .1, .2 before suffix rather than after
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tony Godshall wrote: > ... >> At the release of Wget 1.11, it is my intention to try to attract as >> much developer interest as possible. At the moment, and despite Wget's >> pervasive presence, it has virtually no user or developer community. >> Given the amount of work that needs to be done, this is not good. The >> announcement of the first new release of GNU Wget in two years seems a >> great opportunity to solicit help! > ... > > That's sort of the nature of older tools with a well-defined mission- > they do their > job so well there's little itch to tweak them. If it ain't broken, > you don't fix it. > Freshmeat lists wget as "mature", which basically means the same thing. Yeah, I imagine that's it. Except that Wget _is_ broken in several important ways... but I think it works for the vast majority of users. In particular, I think the most widespread use of Wget is for fetching single files, which Wget seldom has any problems doing. It's when you try tricky things that Wget can sometimes break your expectations. Even so, of course, I have rarely if ever run into problems using it, personally. > I guess wget will have to get a bit immature to get some buzz going. Some > pretty insane goals in a wget2 roadmap would probably do the trick. How > about announcing plans implement DHT and make bittorrent obsolete? That > should make slashdot ;-) I dunno, man, I think our current wget2 roadmap goals are already pretty wild-and-crazy. ;) - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHT2ni7M8hyUobTrERAvh2AJ4hEcCzAF5vdpuflFJ1P7GyzPzjxgCfeaHh /GVTxx+vFcm9PcE3a8P21qM= =Hkhj -END PGP SIGNATURE-
Re: wget2
On 11/29/07, Micah Cowan <[EMAIL PROTECTED]> wrote: > - Alan has prior history on this list. Check the archives: yeah, I remember him. And is it just me, or does it seem that something's going to go down tonight with wget 2? ;-)
Re: wget2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tony Godshall wrote: > On Nov 29, 2007 4:02 PM, Micah Cowan <[EMAIL PROTECTED]> wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Alan Thomas wrote: >>> What is wget2? Any plans to move to Java? (Of course, the latter >>> will not be controversial. :) >> Java is not likely. The most likely language is probably still C, > ... > > I think he's a troll because one of the top google hits for "wget2" is a > short little java program he's apparently trying to draw attention to. Wow. I thought you were joking, because of the Java bit (plus you added a winking smiley: mixed messages, man). That Alan is trolling seems very unlikely, as - The "Java program" you refer to is about 20 lines of code, and will bring no one any useful traffic. - Alan has prior history on this list. Check the archives: http://www.mail-archive.com/[EMAIL PROTECTED]&q=from:%22Alan+Thomas%22 - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHT2lr7M8hyUobTrERArUSAJwLn+LdR7z9TNsqNWFQZquOA1ATMQCfRkBK 8JugIDSZ0d1K/B58qh3Fhbk= =3cL9 -END PGP SIGNATURE-
Re: .1, .2 before suffix rather than after
... > At the release of Wget 1.11, it is my intention to try to attract as > much developer interest as possible. At the moment, and despite Wget's > pervasive presence, it has virtually no user or developer community. > Given the amount of work that needs to be done, this is not good. The > announcement of the first new release of GNU Wget in two years seems a > great opportunity to solicit help! ... That's sort of the nature of older tools with a well-defined mission- they do their job so well there's little itch to tweak them. If it ain't broken, you don't fix it. Freshmeat lists wget as "mature", which basically means the same thing. I guess wget will have to get a bit immature to get some buzz going. Some pretty insane goals in a wget2 roadmap would probably do the trick. How about announcing plans implement DHT and make bittorrent obsolete? That should make slashdot ;-) Tony -- The above is not to be taken seriously.
Re: wget2
On Nov 29, 2007 4:02 PM, Micah Cowan <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Alan Thomas wrote: > > What is wget2? Any plans to move to Java? (Of course, the latter > > will not be controversial. :) > > Java is not likely. The most likely language is probably still C, ... I think he's a troll because one of the top google hits for "wget2" is a short little java program he's apparently trying to draw attention to.
Wget for MP3 streams
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Ginger wrote: > What I'm looking at wget for is saving streamed mp3 from a radio station, > crazy but true.. such is life. Isn't that already possible now? Provided that the transport is HTTP, that is? - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHT2FK7M8hyUobTrERAscGAJ9vaxR9adUubUctMgcEq564lvrELwCdEkEC loXnJOWjMTKKUKpQimiCJ0o= =Hh0b -END PGP SIGNATURE-
Re: wget2
On Friday 30 November 2007 00:02:25 Micah Cowan wrote: > Alan Thomas wrote: > > What is wget2? Any plans to move to Java? (Of course, the latter > > will not be controversial. :) > > Java is not likely. The most likely language is probably still C, > especially as that's where our scant human resource assets are > specialized currently. I have toyed with thoughts of C++ or Python, > however - especially as the use of higher-level languages could allow > more rapid development, which is nice, given our (again) scant assets. I'd vote for Python :-) > :) The truth is, it's too early to say, given that work hasn't even > > begun to have... begun. :D > > C still remains by far the most portable language (though of course, > writing it portably is tricky ;) ). But that's a bigger issue for the > existing Wget's purposes probably, than "new-fangled Wget 2". > > For information on what is planned for "Wget 2", check out the "Next > Generation" and "Unofficially Supported" sections of this page: > http://wget.addictivecode.org/FeatureSpecifications, and particularly, > this thread: http://www.mail-archive.com/wget%40sunsite.dk/index.html#10511 Thanks for the links:-) I really liked this idea - "An API for developers to write their own dynamically-loaded plugins" What I'm looking at wget for is saving streamed mp3 from a radio station, crazy but true.. such is life.
Re: wget2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alan Thomas wrote: > What is wget2? Any plans to move to Java? (Of course, the latter > will not be controversial. :) Java is not likely. The most likely language is probably still C, especially as that's where our scant human resource assets are specialized currently. I have toyed with thoughts of C++ or Python, however - especially as the use of higher-level languages could allow more rapid development, which is nice, given our (again) scant assets. :) The truth is, it's too early to say, given that work hasn't even begun to have... begun. :D C still remains by far the most portable language (though of course, writing it portably is tricky ;) ). But that's a bigger issue for the existing Wget's purposes probably, than "new-fangled Wget 2". For information on what is planned for "Wget 2", check out the "Next Generation" and "Unofficially Supported" sections of this page: http://wget.addictivecode.org/FeatureSpecifications, and particularly, this thread: http://www.mail-archive.com/wget%40sunsite.dk/index.html#10511 - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHT1MR7M8hyUobTrERAme+AKCLZMI3z+BDFTnm79u9iamLeb3D4QCePntr 0K1Be3gM/BkL0k8lswD1fu8= =pg5N -END PGP SIGNATURE-
Re: .1, .2 before suffix rather than after
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Josh Williams wrote: > On Nov 29, 2007 6:20 PM, David Ginger > <[EMAIL PROTECTED]> wrote: >> So can I ask is a wget2 actualy being developed ? > > Go ahead, but I'll answer that question before you do ;-) > > The answer is no - not at the moment. But we've been discussing it for > several months. It will be a while before any code is actually > written. Specifically, it will probably be years, unless we can get a much-needed influx of developers in here. The list of issues targeted at Wget 1.12 are many, and most of them really should be resolved before we begin work on the "beefier" Wget. And, as I am (1) by far the most active current Wget developer, and (2) not all that terribly active, given that it's all just in my spare time ;) - work is liable to be a bit slow. The good news is, once the Wget 1.12 stuff is out of the way, we can move almost all focus to the new thing, as Wget will be almost completely in bug-fixes-only mode. Given that's the case, one might argue that Wget 2.0 is in fact a reasonable name for the new package. I'm still thinking about that stuff, and will probably add a Wiki page for the purpose of names discussion soon. At the release of Wget 1.11, it is my intention to try to attract as much developer interest as possible. At the moment, and despite Wget's pervasive presence, it has virtually no user or developer community. Given the amount of work that needs to be done, this is not good. The announcement of the first new release of GNU Wget in two years seems a great opportunity to solicit help! - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHT1FT7M8hyUobTrERAswMAJ9rNSv2kC1MIy3vErblMfcqBmcWdQCgjT2z C8kgh5b4msWnw0ORb8x0Jl8= =VMV+ -END PGP SIGNATURE-
Re: wget2
On Nov 29, 2007 3:48 PM, Alan Thomas <[EMAIL PROTECTED]> wrote: > What is wget2? Any plans to move to Java? (Of course, the latter > will not be controversial. :) Troll ;-)
wget2
What is wget2? Any plans to move to Java? (Of course, the latter will not be controversial. :) Alan
Re: .1, .2 before suffix rather than after
On Nov 29, 2007 6:20 PM, David Ginger <[EMAIL PROTECTED]> wrote: > So can I ask is a wget2 actualy being developed ? Go ahead, but I'll answer that question before you do ;-) The answer is no - not at the moment. But we've been discussing it for several months. It will be a while before any code is actually written.
Re: .1, .2 before suffix rather than after
> i totally agree with hrvoje here. also note that changing wget > unique-name-finding algorithm can potentially break lots of wget-based > scripts out there. i think we should leave these kind of changes for wget2 > - or wget-on-steroids or however you want to call it ;-) So can I ask is a wget2 actualy being developed ?
Re: .1, .2 before suffix rather than after
On Sunday 04 November 2007 22:54:24 Hrvoje Niksic wrote: > Micah Cowan <[EMAIL PROTECTED]> writes: > > Christian Roche has submitted a revised version of a patch to modify > > the unique-name-finding algorithm to generate names in the pattern > > "foo-n.html" rather than "foo.html.n". The patch looks good, and > > will likely go in very soon. > > foo.html.n has the advantage of simplicity: you can tell at a glance > that .n is a duplicate of . Also, it is trivial to remove > the unwanted files by removing .*. Why change what worked so > well in the past? i totally agree with hrvoje here. also note that changing wget unique-name-finding algorithm can potentially break lots of wget-based scripts out there. i think we should leave these kind of changes for wget2 - or wget-on-steroids or however you want to call it ;-) -- Aequam memento rebus in arduis servare mentem... Mauro Tortonesi http://www.tortonesi.com University of Ferrara - Dept. of Eng. http://www.ing.unife.it GNU Wget - HTTP/FTP file retrieval tool http://www.gnu.org/software/wget Deep Space 6 - IPv6 for Linux http://www.deepspace6.net Ferrara Linux User Group http://www.ferrara.linux.it
Re: How to change the name of the output file
On Tuesday 20 November 2007 20:38:13 Micah Cowan wrote: > Be advised, though, that -O doesn't simply mean "make the name of the > downloaded result `filename'"; it means "act as if you're redirecting output > to a file named `filename'". In particular, this means that such things as > timestamping, and multiple URLs, may not work as you expect. micah, i believe this text is a good candidate for inclusion in the man page. -- Aequam memento rebus in arduis servare mentem... Mauro Tortonesi http://www.tortonesi.com University of Ferrara - Dept. of Eng. http://www.ing.unife.it GNU Wget - HTTP/FTP file retrieval tool http://www.gnu.org/software/wget Deep Space 6 - IPv6 for Linux http://www.deepspace6.net Ferrara Linux User Group http://www.ferrara.linux.it
