Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/21/2019 in all areas

  1. There's no point to this. Thread Locked
    1 point
  2. Not yes, not no: on the contrary.
    1 point
  3. Really it's mostly a matter of taste. The main difference is the UI: BOC looks very much like SeaMonkey; Serpent looks very much like (pre-Photon) Firefox; NM 28 looks like older (pre-Australis) Firefox. They're all based on UXP though. If you have an older, pre-SSE2 PC, you may want to look at @roytam1's Firefox 45 or NM 27 builds instead.
    1 point
  4. I'd wager you need to install the Visual C++ redistributables? Here's a Microsoft article listing the latest versions of each: https://support.microsoft.com/en-us/help/2977003
    1 point
  5. I’d like an IRC channel with a link to the Discord server too for those who want to chat there on older MS OSes or don’t accept Discord’s monopolistic takeover of Internet culture (as has Twitter).
    1 point
  6. yeah it is possible to build 64bit editions, but since there is no demand (I don't use them, and no user requesting 64bit builds) so I don't build 64bit BOC-related builds by default.
    1 point
  7. It does. 2.8.6/2.8.7 is not pushed for automatic download.
    1 point
  8. Through AU, it doesn't list any specific number. It is known IE9 depends on it, however - best bet would be to fire up a clean SP2, and check what's installed after IE9. Also AU on a clean Vista SP2 still works and everything's there as of 8am GMT+1 today when the "speedup" patches are applied, so that at least gives us time.
    1 point
  9. Please elaborate, to figure out solutions? The prob is, K-Meleon may be missing some essential things, but it also has lots of hidden features which simply aren't visible to unexperienced users. For example most buttons have a handy right-click menu, which most people never discover just because they have no little-arrow as indication (example Home or Go-buttons) A killer feature is the hidden privbar (View > Toolbars) with buttons for 1-click toggle of javascript, cookies etc. Or the "about:about" page has lots of working links to more settings, incl. about:addons, which are not found anywhere in the menus, just because the GUI hasn't been updated in the last ten years or so, only the engine (install macro aboutabout to get at least a makeshift-menu) Copy+search: select a text in a webpage and hit the search button (or similarly: select a text LINK and hit the Go-button) Duplicate a tab: pull the tab into an empty space on tab bar (if any left ;-), or right-click on Go-button If you want a closing cross on tabs: guess for this there's actually a GUI somewhere, perhaps in F2... (would have to look it up, am myself stuck on old version) There are also macros for easy useragent-toggling, I recommend my "useragents2018" which also helps for easier managing site-UAs.
    1 point
  10. just found a typo in my modified code, archives are updated to fix this bug.
    1 point
  11. You can enable or disable SSL/TLS ciphers according to your own security preferences. Go to about:config and filter for security.ssl3 and you'll see all available cipher suites for SSL 3.0 through TLS 1.2. Filter for security.tls13 to see the available cipher suites for TLS 1.3. Set to true to enable or false to disable. Changes are stored in your profile so they'll "stick" between browser updates; but you have to do this for every browser profile you use. A few Web sites may not yet use newer, more secure ciphers; if you visit any of those, you'll need to leave a less secure cipher enabled to access it. If you disable some ciphers, then can't connect to a site, that's probably the reason. Create a new, "clean" profile, restart the browser specifying it, and try again. If it works, check which cipher your browser uses with a particular site by clicking the padlock, then the right arrow, then "More Information." Then restart your browser with the default profile, and re-enable the cipher your browser used with that site. Your communications with that site are probably still reasonably secure, but be aware that they could eventually be decrypted by someone determined enough; perhaps even years later, and act accordingly. Ideally, you should contact the Webmaster and ask them to enable newer, more secure ciphers. (The Web site may choose to leave some older ciphers enabled as well, for compatibility with older browsers. That's fine as long as the newer ones are preferred.)
    1 point
×
×
  • Create New...