Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/08/2018 in all areas

  1. Hi. There is no need for webextensions. Dedicated extensions can be installed: https://addons.palemoon.org/extensions/ Legacy extensions for Firefox (usually older versions). Other extensions (the best is HTTPS Always) for supported browsers: https://wiki.hyperbola.info/doku.php?id=en:project:iceweasel-uxp_addons https://addons.thunderbird.net/en-US/seamonkey/extensions/privacy-and-security/?sort=popular&page=3
    2 points
  2. Not really-really, to be picky. They changed that for *whatever reasons they saw fit* while telling everyone that it was to improve security. jaclaz
    1 point
  3. I really don't understand why Microsoft doesn't just give us the option to use Aero transparencies. I know it can use more resources on older machines that might not have them, but since Win7 hardware has come a long way. Most consumers get Windows with a new computer. I'm sure most of us here build our own. Anyway, thank you Big Muscle for doing what Microsoft won't.
    1 point
  4. This is what happens when a company relies on amateurs for beta testing instead of trained and experienced professional programmers. Bugs still happened, but they seemed to be much less severe and much smaller in scope (notable exceptions to this exist, I'm sure... I just can't think of any ) There's a lot to be said about waiting a year or more for a piece of software to be tested and properly matured (and thus properly debugging it) before releasing it to the public. All this fast-tracking has been lowering the overall quality of most software considerably over the last 7 years or so. In my opinion, anyway. And long term stability is important too. Having an OS that constantly updates itself, with no way for the user to control or stop the process, introduces a lot of variables that can make the OS inherently less stable. There is an upside, I suppose, in that important fixes or new features that are genuinely useful can be released much more rapidly. Isn't that what monthly hotfixes were for? Somehow, we as users of Windows managed to get by with the old, supposedly inferior OS update/upgrade model for many years. What makes this new, rapid release model so much better? So far, all I've seen are countless examples of why it's broken and more difficult to manage (pretty much every time there's an update now, I've noticed that something important breaks, and the update is withdrawn and re released with fixes, where if they'd take the time to test more thoroughly (like they used to), they could've gotten the updates right the first time). Having monolithic update packs, whose contents are inseparable from one another, doesn't help, because one bad update in the pack can spoil the rest of them. The old model, for any flaws it may have, at least was predictable and mostly reliable. c
    1 point
  5. Hi ; unfortunately, both the current Firefox (53+) full browser extension (at version 3.2.32) and the limited Old Firefox (48+) browser extension (at version 1.0.6) are of the WebExtension type, a format that Pale Moon (hence New Moon) does not support by choice/design ; OTOH, Serpent 52.9.0 comes with a limited set of WebExtension APIs, so you might want to check your luck there I was successful in installing the full extension on both Serpent 52.9.0/55.0.0, but since I don't have the app installed (nor a MyJDownloader account), I can't test the extension is fully functional! Hope I've helped...
    1 point
  6. New build of basilisk/UXP for XP! Test binary: Win32 https://o.rthost.cf/basilisk/basilisk52-g4.1.win32-git-20181006-8860eddce-xpmod.7z Win64 https://o.rthost.cf/basilisk/basilisk52-g4.1.win64-git-20181006-8860eddce-xpmod.7z diff: https://o.rthost.cf/basilisk/UXP-xp-gitdiff-20180606.7z PM28XP build: Win32 https://o.rthost.cf/palemoon/palemoon-28.2.0a1.win32-git-20181006-8860eddce-xpmod.7z Win64 https://o.rthost.cf/palemoon/palemoon-28.2.0a1.win64-git-20181006-8860eddce-xpmod.7z Official repo changes since my last build: - Update upstream URL and update script for libnestegg (d8434bf15) - Update libnestegg from upstream (dad1c31db) - Get rid of the incorrect mechanism to remove insecure fallback hosts. (347aea437) - Update HSTS preload list (778b3c4d7) - Update test files for libnestegg update (704c93539) - Merge pull request #800 from trav90/update-from-upstream (c7e12ca39) - Remove telemetry to find optimal cache entry hash size (0b1600742) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (6d9103276) - Update telemetry whitelists. (ddf29811b) - Clean up a number of unused variables. (81b341a9b) - Remove telemetry probes for cache file system. (3343a4b47) - Remove telemetry probes to get detailed disk cache hit rate. (ab9edfb54) - Remove cache I/O telemetry. (8ba6dd1bd) - [ffvpx] Update ffvp9/ffvp8 to release 4.0.2 (edc124b92) - Clobber for ffvpx update (7d1ee0e5e) - Remove unused telemetry functions/variables. (7b0f3f2f9) - Remove telemetry from cache v1 service locking (part1). (d718e32b5) - Remove telemetry from cache v1 service locking (part2). (ec4c6dd42) - Remove telemetry reporting functions from CubebUtils (38e8ee1e6) - [PALEMOON] Use message manager to detect full-screen HTML5 video in S4E module (35a1adb07) - Merge pull request #804 from JustOff/PR_s4e_FullScreenVideo (ab881a3bf) - Merge pull request #801 from trav90/update-from-upstream (79b00fc33) - Revert "Update ffvpx code to 4.0.2" (45c24f05d) - Merge pull request #805 from MoonchildProductions/revert-801-update-from-upstream (8e8fcee4a) - [ffvpx] Update ffvp9/ffvp8 to release 4.0.2 (ebc8d7e3c) - [ffvpx] Remove unneeded libavcodec symbols and dummy functions (82238ada2) - Clobber for ffvpx update (41ccd52bf) - Merge pull request #806 from trav90/ffvpx-resync (69d83c8fb) - [ffmpeg] Always allocate memory to pass extradata (c0d9931cf) - Merge pull request #808 from trav90/media-work (26975ccf5) - Make all arguments to init*Event() optional except the first (e42166a5b) - Bug 1493900. (ca7ecd37c) - Ensure we got an nsISSLStatus when deserializing in TransportSecurityInfo. (95379e337) - Fix in-tab close button behavior (#775) (d74519372) - Merge pull request #811 from MaxKoll/MaxKoll-patch-1 (8860eddce) My changes besides above changes: - reverted rev ebc8d7e3c...82238ada2 (i.e. 69d83c8fb) in favoring ffmpeg-3.4 branch, since ffmpeg-4.x needs SRWLock and bcrypt changes to be undone which is not yet tested
    1 point
  7. XP is still good today - except for the internet stuff. In relation to Windows 10 with its user unfriendliness, endless complexity and sly telemetry it is a day to the night comparison.
    1 point
×
×
  • Create New...