Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Mathwiz

Member
  • Content Count

    1,155
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    35

Everything posted by Mathwiz

  1. I certainly can't claim credit. Many of us were using "Moebius" as an informal name for what eventually became Serpent 55 long before either Matt or I suggested it as a formal brand name. The first use "Moebius" I can find on this forum was in the link to MCP's original UXP platform: So technically, I guess credit for the name should go to Moonchild (M.C. Straver)! Minor language note: The true spelling is Möbius, with an umlaut over the o. But the umlaut isn't used in English and some other languages (English has a "dieresis" which looks just like an umlaut; it's used in words like coöperate, but it's so rare my spell checker balks on that word). Thus the ö is often rewritten as oe for the benefit of those of us with no easy way to type ö.
  2. I think we both hit on it independently. Moebius was the code name for the post-FF 52, pre-Quantum rendering engine, or something like that, it's been used informally for Serpent 55, and it sounded like a cool name with lots of cool artwork opportunities. But I tend to agree with the suggestion that we just have one name for Serpent and append 52 or 55 as appropriate, in which case Moebius would have to go. Let's not make things more complicated than necessary. BTW, after I'd voted in several of the polls, I realized you can vote for more than one name. I think that's a cool option, especially for the browsers with many suggested names on the ballot. Oh, and slightly OT: does anyone know if you can put an animated .gif in the "About <browser>" dialog box, the about:newtab page, or any other relevant place in these browsers? Might be a cool branding trick.
  3. I discovered (too late for most polls) that these polls are set up to let you choose more than one name! So if you like two or more names, go ahead and vote for all the ones you like. (Name with most votes still wins, of course.) Now, if only we Americans could have done that on Super Tuesday....
  4. I don't think @roytam1 was too crazy about RFox either. He objected to RoyFox, and RFox isn't that different.... RFox aside, I'd like to close this and just go with @TechnoRelic's last suggestions. It's past time to come to some sort of consensus and get to work!
  5. Couldn't confirm. EasyList shows up-to-date on mine. A few other filters I use showed errors from the last update attempt, but a manual update fixed them all. Not sure how often updates run, but IIRC most filters are considered "out of date" after a couple of days. So I'd guess it starts an update when the browser starts, as well as daily if you leave the browser open for extended periods.
  6. If you don't want to install Classic Theme Restorer, you can still suppress those warnings by following @VistaLover's instructions here:
  7. Aside from the WebRTC blocking feature I mentioned (which may not be an issue for you; it probably matters only to users behind, e.g., corporate firewalls), the only major change was Convert new shorthands back to legacy syntax when fetching filter lists using firefox-legacy (pull request by JustOff). Basically the syntax for filter lists was updated recently, so older uBO versions like 1.17.4 won't understand filters with the new syntax.
  8. What are you folks trying to accomplish here? Support for TLS 1.2 was added to XP (actually, POSReady '09) long ago by the above mentioned KB, and to IE8 specifically by KB4316682 (later cumulative IE8 updates should work too): TLS 1.2 support is limited though, because native support for ECC (certificates and ciphers) was never added to XP. If it's TLS 1.3 you want (without using ProxHTTPSProxyMII) on IE/Chrome, I'd bet you're going to have to perform some pretty major surgery. Might be better off just migrating to ReactOS, or just using a browser with native TLS 1.3 support like EE 360 or @roytam1's Serpent.
  9. And, done. Also: removed the SSUAO for YouTube to v.42, since it will stop working soon put in a general.useragent.override to version 60.9. Newer versions of MCP's UXP-based browsers (PM/NM 28, Basilisk/Serpent 52) are now reporting 68.9, but that causes more problems than it solves IMO. Updated version is here: As always, feel free to modify the myuseragents.js file (or override in about:config) as desired to fit your own browser and the Web sites you visit.
  10. Apologies if I'm wrong, but it sounds like you're not familiar with the User-agent: header. All browsers identify themselves to Web servers with a user-agent string that identifies the browser, version, and platform (OS). Unfortunately Web sites (such as bbc.co.uk) often just look at that string, rather than checking whether the browser actually has the capabilities the site needs. And they may not even be consistent from one page to the next at the same site! Thus, it's sometimes necessary to override the user-agent string (sometimes called "spoofing") to report a different version, or even a different browser entirely, in order to get particular web sites to work. And it often takes quite a bit of trial and error to find a user agent that will make a particular Web site work. You can find more info at this thread: Of course, the user agent isn't the only possible reason that a video might not play. For example, it could be using a new codec (such as av1) that Adobe Primetime doesn't understand. If that's the case, overriding the user agent won't help - but it's usually a good place to start.
  11. uBO 1.17 and up are WebEx versions. 1.16.4.x is the last version using the legacy API, so it's the last version supported by Pale Moon, New Moon, and (official) Basilisk. Developer JustOff recently took over development of the legacy branch from Gorhill, so Gorhill now works exclusively on the WebEx branch and JustOff works on the legacy branch. Because of the split, 1.16.4.18 is the newest uBO version that will run on FF 52 / Serpent. It's much newer than 1.17.4. (I think the latest WebEx version of uBO is now 1.24, but it won't run on FF 52 / Serpent. BTW, 1.18 will run on those browsers, but it thinks it won't, so you have to jump through some hoops to fool it.) I do use the legacy branch, but not because it's "newer." I use it because one feature (blocking WebRTC from leaking your IP address) doesn't work on FF 52 / Serpent if you use a WebEx version. You can download uBO version 1.16.4.18 from https://github.com/gorhill/uBlock-for-firefox-legacy/releases/download/firefox-legacy-1.16.4.18/uBlock0_1.16.4.18.firefox-legacy.xpi . It's an unsigned extension, so make sure xpinstall.signatures.required is set to false in about:config first! You'll also see a warning that uBO "couldn't be verified" after installing, but you can hide that warning with another extension such as Classic Theme Restorer. You'll probably need to back up your uBO configuration and uninstall 1.17.4 before you can install 1.16.4.18, but once that's done you can restore your configuration and be back to where you were.
  12. I must be missing something. Wouldn't you expect an error if you try to log into a banking site with bogus credentials? Huh? What's not true? I'm not missing anything? You wouldn't expect an error if you try to log into a banking site with bogus credentials? Are we even speaking the same language here? You can do that if you wish, but to me, testing someone's browser issues by trying to log into a banking site with bogus credentials, probably repeatedly in order to test various possible workarounds, sounds like a pretty terrible idea. Most of us aren't particularly interested in prompting an uncomfortable visit from the authorities, so asking for more information and letting the OP test possible workarounds with their real Citi.com account seemed to be the more prudent approach. I'm sorry my caution seems to have offended you, but the OP has let me know they're content to let the issue drop, so I won't pursue it any further.
  13. I must be missing something. Wouldn't you expect an error if you try to log into a banking site with bogus credentials? Or are you saying the error appears whether the credentials are valid or not? If so, try this site: https://www.whatismybrowser.com/detect/what-is-my-user-agent. Try it with both the browser that works and the browser that doesn't, and post the results here. If the results are different, try a site-specific user-agent override; in the browser that doesn't work, set general.useragent.override.citi.com to the value returned by the browser that works. Then try logging on to citi.com and see if that fixes it.
  14. In Firefox, site-specific user agents don't work (well, they can be made to work with some JavaScript sleight-of-hand, but it's complicated.) So you need an add-on in order to feed Slack, YouTube, etc. their own separate user agents. But the default UA for FF 52.9 should work with YouTube without giving you the browser warning Your problem really sounds like a memory leak somewhere. Try it in "safe mode" to eliminate add-ons as a possible source of the problem. If the scrolling slowdowns and full-screen weirdness go away in safe mode, try turning off add-ons a block at a time to isolate the one causing the memory leak. (It's tedious, I know.) For multiprocess mode, try increasing dom.ipc.processCount to 2-4 instead of 1. That will let FF kill processes when you close tabs.
  15. This had all happened automagically so I hadn't even noticed, but I just checked about:addons and sure enough, uBO Updater is up to version 1.6.9 (presumably to handle the new repo) and uBO itself is up to 1.16.4.16 on my browser! I was noticing the referenced WaPo article worked fine on my system, but hadn't a clue why. (Not that I was wont to complain!) But anytime I install a new browser, whether FF, Chrome, or Edge, the first thing I do nowadays is install uBO on it, so this would explain it. (Internet advertising is so out of control nowadays that you just can't go without something to tame the chaos!) I've run into a couple of sites that require (or at least work better with) service workers, so I too have them enabled in about:config, even though the legacy uBO I use doesn't need them. But I restrict service workers to the sites that do need them with a line in My Filters in the uBO dashboard: *$csp=worker-src 'none',domain=~mediafire.com|~html5test.com There are probably a few other sites I should add to that line (mega.nz perhaps?) but I haven't gotten around to it yet. Ironic to say the least, given the article's content: "Don't use Kaspersky AV because the Russians will violate your privacy; let the WaPo do it instead!" I guess Jeff Bezos doesn't think he's rich enough yet; after all, he only has his own space program.... (FWIW, Elon Musk's space program is better though ) The current legacy version is newer, but it's numbered 1.16.4.16, so AMO thinks 1.17.4 is newer and "updates" it accordingly. Perhaps now that it's separate, JustOff should consider bumping the version number to avoid this issue. Meanwhile, you can turn off automatic updates for uBO, or you can install the "uBlock Origin Updater" add-on, which will force the browser to update uBO from the legacy repo instead.
  16. Don't believe everything you read. Almost all Internet logins today are TLS-encrypted and all TLS sessions are end-to-end encrypted; no one in between has unencrypted access to the contents, unless they've managed to compromise the servers and steal their private keys. (And even that only works until the certificate is renewed in a year or two.) You can do man-in-the-middle attacks, but unless the client software doesn't properly verify the server's certificate, the user will just get an error message. They may be able to bypass, but security experts and paranoid types are gonna squeal. Some of the Goog's Android software doesn't do that verification (hence the ability to spy on your phone while it spies on you) but pretty much every Web browser does. Corporations who censor their employees' Internet access (as most do) have to install special trusted certificates on all their PCs to get around this. It's good to be a bit paranoid in our modern world, but don't let your paranoia override your common sense. Almost privacy leaks today come from spyware, especially on smart phones, but also PC software, including - unfortunately - Avast. (Despite Avast's efforts to anonymize the data they sell, they probably have underestimated the Goog's ability to match a user's "fingerprint" to the copious databases collected by Android smart phones.)
  17. The thing is, @roytam1 didn't write and doesn't maintain the installer; @i430VX does! It probably wouldn't be hard for his installer to ask if you wanted a portable install, and add the necessary options to the shortcuts it creates. But @i430VX is the one to ask.
  18. Yes it does. Personally, I think if the broadcasters mandate DRM (as appears likely at this point) it will merely ensure the new standard never becomes the dominant one. DRM would require anyone selling a 3.0 tuner to figuratively sign their business's life away to get a key. Only the biggest TV manufacturers (Samsung, LG, etc.) will be able to afford to do so. TiVo will be the only DVR maker that can do so. SiliconDust, maybe (they managed it for CableCard access), but you can forget about any $40 3.0 tuners, as the 1.0 world now enjoys. And of course the tuners would have to use HDCP, so say goodbye to component video; and the TiVo recordings would be encrypted, as they are for (some) cable recordings now (depending on what channels your cable provider flags with DRM). So we'd be paying more for equipment that does less. And for what? Higher resolutions than most folks can even see? "Interactivity" (which failed with ATSC 2.0)? At best, it sounds like ATSC 3.0 might become a niche market for videophiles, like HD Radio became for audiophiles. OTOH, maybe the broadcasters will force the issue, by (say) lowering ATSC 1.0 picture quality back down to SD and/or dropping some of the subchannels you've come to enjoy. You want to keep what you have now? Then you must "upgrade" (and put up with all the DRM restrictions).
  19. The legal way to get the POSReady '09 updates also required payment (for POSReady '09). I suppose a distinction could still be made: if the POSReady '09 XP hack wasn't published until after POSReady '09 was no longer available for sale, then the hack could be considered not stealing since you couldn't buy it from M$ anyway. But it does seem like a rather fine line we're not crossing. At any rate, perhaps a more acceptable route would be to do what POSReady '09 did: spoof a different Win 7 version, perhaps Server 2008 R2. It would be more challenging than the XP registry hack - I think you'd need to hook GetProductInfo, so it would require some programming - but sounds prima facie doable.
  20. You could also try petrus's suggestion: That idea should work with any FF-derived browser (NM, Serpent, Navigator, etc.)
  21. I haven't read the topic (registration required, and it's not a big enough deal to bother registering) so I'm just guessing that they're following Google's timeline for Chrome, rather than M$'s timeline for Win 7 itself: As to Win 8, it's interesting that it's newer than Win 7, but also hit EoS earlier (since everyone was "supposed" to upgrade to 8.1). So if/when they do stop supporting Win 7, they might just set the minimum required version to 8.1 and we'd all be out of luck. But it may also have to do with programming. Another guess of mine is, it's not really any harder to support Win 7/8 than it is to support 8.1. If so, MCP may not see much advantage in cutting off Win 7/8 support in terms of removing code from the product. The chance to remove code and make the browser package smaller seems to have been one of their motivations to drop XP support (less sure about Vista) back in the day. You were perfectly clear; that's why I said you probably wouldn't like my solution! FF 52 doesn't support SSUAOs (at least, not without considerable tweaking), so an extension like "Good Twitter" is needed to send Twitter a different UA (so their Web server will use the old interface). However, this also causes Twitter to send the audio that @roytam1's built-in support wouldn't have handled correctly, but since you're (of necessity) using Primetime with FF 52, it plays fine anyway. As for getting it to work in NM, his built-in support is probably getting the sampling rate wrong somehow. Unfortunately I don't think anyone yet knows quite how to fix it.
  22. OK, so it appears that, to avoid distorted audio, you have to include Gecko and/or Firefox in the UA - but then, you either get the new Twitter interface or the mobile version of Twitter (depending on the spoofed FF version), neither of which you want. (Side rant: I wish Twitter and other Web sites would quit doing this! Just because your company's marketing geniuses think everyone will love whatever new UI you've cooked up doesn't mean it's true! And obviously you still support the old interface - so is it that hard to give folks a "new/classic" interface checkbox in your user preferences screen, instead of making them fool around with user agent strings?) I think I have a solution, but I'm not sure either of you will like it. This solution requires FF 45 or Serpent. Use the Pale Moon or IE user agent to get the old interface (and distorted audio) To fix the audio, turn off the internal A/V support (in about:config, set media.ffvpx.enabled to false); instead, install the Adobe Primetime CDM. That should play the audio without distortion. (Installation instructions are a few threads below this one.) In Vista and above, you could use the WMF support built into Windows instead, but IIRC, WMF in Vista has bugs of its own with Twitter, so on Vista you may want to use Primetime anyway.
  23. Looks like Cloudflare updated their TLS security. Old versions of wget no longer work (even with up-to-date OpenSSL). New wget versions work fine. Same is probably true of browsers. Which browser is having the problem and what message is it giving you?
  24. That's true. Most folks under 30 probably only watch traditional TV for sports, or maybe because the business they're patronizing has a TV on. Most of them stream pretty much everything else. WMC and similar software is just for old-timers like me who refuse to let go of our dinosaur viewing habits. It's ironic, therefore, that the two biggest features Micro$oft removed from WMC over its lifetime were the sports line and Netflix.
×
×
  • Create New...