On Mon, Mar 23, 2009 at 1:35 PM, Nick Guenther <kou...@gmail.com> wrote: > Also, youtube matters. This is going to get me flamed but a lot of > worthwhile content is in form of video now and not making that work > disenfranchises yourself.
There are methods of fetching just the video off youtube if that's all you want. I think I've even seen at least two scripts in ports that just do that (www/youtube-dl is one and the other I can't recall its names off top of my head). I don't know how well they work; never used them myself. I agree with you on valuable/informative/entertaining content on youtube. Flash is open now, their specification docs were released. If it is important for folks, a truly open, reliable and secure versions should/could be implemented. --patrick > > -Nick > > On 23/03/2009, Ingo Schwarze <schwa...@usta.de> wrote: >> Hi Chris, >> >> very probably, you are not describing a bug, but the following feature. >> >> Chris wrote on Mon, Mar 23, 2009 at 02:15:10PM +1100: >> >>> When I start firefox (3.0.6) from the xterm shell, I get two firefox >>> starting at the same time. >> >> Very probably, you are not getting two firefox processes, >> but one firefox process managing two windows. >> To check this, run >> >> B $ ps ax | grep firefox-bin >> >>> If I close one of them (by doing File - Exit), >> >> By chance, i still have the somewhat oldish firefox 3.0.6 installed >> on a 4.5-current i386 box. B Here, the file menu doesn't contain >> an "Exit" menu entry. >> >>> it closes both of them. >> >> When i do "File - Quit", i get a popup window >> >> B "Do you want Firefox to save your tabs and windows >> B for the next time it starts? >> >> B [Checkbox] Do not ask next time >> >> B Button: Quit >> B Button: Cancel >> B Button: Save and Quit" >> >> Maybe you checked the checkbox and clicked "Save and Quit"? >> When doing that, i can reproduce the behaviour you describe. >> >>> I have the same behavior from two >>> different window managers: awesome and scrotwm. >> >> Probably, what you describe has nothing to do with the >> operating system or the window manger, but with firefox itself. >> >> You can go to "Edit - Preferences - Main - Startup" >> and select "When Firefox starts, Show my home page". >> Actually, you wouldn't believe it from what the dialogue >> texts in the browser say: But that will revert *exactly* >> the effect of checking the box "Do not ask next time". >> I checked this by diffing the prefs.js file before and after. >> >> If you want to keep the behaviour of restoring tabs and windows >> on startup but just want to use only one window in the future, >> just click "File - Close" in one of your two windows. >> >> >> Now don't get me started on firefox. B It has turned so damn >> MS-Windows-ish: B Creeping featurism wherever you look, features >> hidden so well and in so much layers that you simply do not find >> most of them even when you actively search for them, almost >> nothing documented, incomprehensible names of features, >> unintellegible correspondance between UI texts and configuration >> option names, unsecure to insane defaults and bloat, bloat, bloat... >> >> All the same, things you really need are not available, or you >> need obscure plugins to achieve them. >> >> >> So if anybody is going to write a browser that i would like, >> i would probably contribute funding to allow several months of full >> time work. B Yes, i know that a few months will hardly suffice. >> >> I would like the following: >> B * Monolithic, fast, small and readable code; no plugins. >> B * Secure, good privacy, high speed by default, and >> B B no way to move the global default settings away from that. >> B * No useless knobs. B No drop-down menus. B No icon toolbars. >> B * Do not bother about non-POSIX operating systems, i.e. assume that >> B B POSIX external utilities and C library calls are available. >> B * Strict principle of not more than one HTTP request per click or ENTER. >> B * No data ever sent across the wire without an explicit left click or >> ENTER. >> B * Never reuse a tab for a different URL unless explicitely requested. >> B B Always use a new tab for each new URL. >> B * Two URL bars, the upper showing the URL displayed in the current tab, >> B B the lower showing the URL the mouse is currently pointing at, including >> B B the TARGET tag, if any. B Prominently mark POST to distinguish it from >> GET. >> B B The lower URL bar can also be used for keyboard input. >> B * A delete command (d) to close the current tab. >> B * A goto command (g) to open a new tab and set the cursor to the URL line, >> B B such that "ghttp://www.openbsd.org/<ENTER>" gets you there. >> B * An alias command (a) to define a bookmark to the current URL, >> B B for example "aobsd<ENTER>" to make "gobsd<ENTER>" work. >> B * Show meta-information about embedded content, not the content itself, >> B B i.e. content type (e.g. IMG), file name or URL, ALT text, size if it >> B B is large. >> B * Per-site and per-URL configuration database, allowing things like >> B B - embedded image download (off by default) >> B B - CSS download (off by default) >> B B - frame content download (off by default) >> B B - accepting cookies (off by default) >> B B - JavaScript execution (off by default) >> B B Store this DB in plain text, easy to browse with cd, ls and vi. >> B * Do not use any files in the user's home directory except this DB >> B B and the cache explained below. B In particular, no .mozilla-like >> B B configuration directories. >> B * When showing frames, always prominently mark the frame borders, >> B B and in the top line of each frame, always show the frame name >> B B and the current URL. >> B * When asking about cookies, always show the full cookie content. >> B * Always ask about HTTPS certificates, even when signed by commercial >> B B root CAs, always show the full certificate content at once, and one >> B B line stating the supporting chain of trust, if any. >> B B Require exactly one click: "Use once" or "Save". >> B B Cancel is useless as you can just close the tab. >> B B Do not try to explain what this is all about. >> B * When interpreting JavaScript, state what the code is trying to do, >> B B i.e. display some text or control elements, follow some link, >> B B get some content, open some window, but do *not* do it. B Yes, >> B B i know this is much more difficult than most of the rest. >> B * Never ever accept any cross-domain embedded content. >> B * By default, preview the full content of POST requests before submission. >> B * Consistent mouse layout: >> B B - left click: activate, e.g. follow link (in a new tab, of course) >> B B - middle click: show, e.g. download and display embedded image >> B B - right click: hide, e.g. replace the image by a "useless" icon >> B B - with shift: also remeber the choice in the config DB >> B B - with alt: modified functionality, e.g. respect TARGET tag >> B * One-key switch between source (s), rendered (r) and filtered >> B B rendered (f) view, without reloading the page, of course. >> B B Stay at the same point in the document when switching views. >> B * Even in rendered view, show interesting meta information at the top, >> B B e.g. content type, title, generator, keywords, employed techniques; >> B B perhaps make this mildly configurable. >> B B Never use the X window title bar for anything, leave that to X. >> B * To figure out the content type, use both the content type header >> B B and file(1). B Provide a command to manually switch the content type (t). >> B * Try to safely display any content, using appropriate filter utilities >> B B configured in /etc/mailcap, e.g. unrtf, pdftotext, antiword, strings. >> B B Never ever ask whether to download binary content to a file. >> B * Provide a command to start an external viewer (x), e.g. xpdf. >> B * A save command (s) to cache the current URL to disk. >> B * Never cache anything unless explicitely requested. >> B * When opening a new tab for a URL that is still in the cache, >> B B show the cached version if it is large (together with a warning), >> B B but reload and display the version from the Internet >> B B if the cached copy is small. >> B * An update ("u") command to explicitely reload large URLs. >> B * When viewing a newer version of a cached URL, highlight the changes. >> B B Allow one-key switch between highlighting and unified diff. >> B * No difference between save and download. B When downloading, >> B B do not ask for filenames, just use the normal caching tree. >> B B In case the URL is cumbersome, you are free to define an alias. >> B B Or you can use cp(1) or ln(1), if you like. >> B * A watch command (alt-s) to save and mark as watched. >> B * A command to check all watched URLs for changes, opening the changed >> ones. >> B * In source view, easy to use junk filtering, e.g. >> B B - Right click on a font tag, and all font tags are gone. >> B B - Right click on an image tag, and all images are replaced by >> B B B [IMG:filename:alt]. >> B B - Preserve this when switching back to rendered mode, even when >> B B B not saving anything to the config DB. >> B * Of course, left and middle clicks should also work in source mode. >> B * A save config command (c) for the current tab, in case you forgot shift. >> B * An edit config command (alt-c) for the current tab/URL. >> B * A show headers command (h) to show received HTTP headers. >> B * A tweak headers command (alt-h) to manipulate HTTP headers to be sent. >> B * Perhaps a raw HTTP console with tab completion. >> >> Well, that's enough dreaming for today. >> >> Yours, >> B Ingo
