×

Give a tip

bricky149

Members
  • Posts

    490
  • Joined

  • Last visited

  • Days Won

    17

 Content Type 

Profiles

Forums

Release Notes

Bug Tracker

Help page

Help page-CN

Release Note5

Rules and recruitment

Release Note6

Posts posted by bricky149

  1. As ever, Tony's Golden firefox_2016-11-01_17-05-16.png is relevant to this forum.

    I'm at the point where someone writing a WebKit (not Blink) browser in Rust which uses Vim-style keyboard shortcuts instead of a GUI is more interesting to me than whatever happens here disguised as 'progress'. Gone are the quick advances of Mx3, now it's about quick sales pitches to get people to try it for 5 minutes.

    I went back to Firefox a while ago to help with dwindling Nightly users. At least if there's something I want to change/fix in it then I can actually do that.

  2. On 16/08/2016 at 6:06 PM, No.1MaxthonFan said:

    Works just fine here.  

    What they meant was the calling functionality is provided by an extension and a plugin that makes use of that extension. MX5 lacks the extension layer as the Chromium Embedded Framework doesn't provide it.

  3. 3 minutes ago, fOrTune(r) said:

    There is no US office anymore, more then a year ago it was closed. All team is in Beijing.

    I was totally unaware. Ignore me!

    I can also see someone on the Chinese BBS has posted the link to the Chinese alpha version of MX5. If people can't wait for the invite, someone has done the work for you. :p

  4. The "new core" the team have mentioned refers to Chromium 37, which does have support for HTTP/2 (but not fully standards-compliant, the standard was finalised after that release). As Maxthon piggybacks off the progress from the Chromium developers it's up to Maxthon when they'll make use of newer Chromium codebases.

  5. I've decided to completely disable ABP in Maxthon due to the astronomical RAM usage it causes alone. Dinataspace has a clear understanding of how ABP works so I thank them. :)

    On Intel HD systems it's best to disable GPU acceleration. I've found pages to load noticeably quicker since there's no GPU thread blocking anything.

  6. I have mentioned uBlock before on the non-public forum and I see someone has made a thread about it on the public one. I am personally not a fan of AdBlock Plus as I understand how it works; it applies its own stylesheets based on what rules are hit by the page. This increases RAM usage and slows down page loading.

    It's obvious we're never listened to, that's why Maxthon 4.x exists. :p

  7. The way AdBlock Plus works is based around stylesheets. It was designed so it would apply its own stylesheet(s) in place of elements that results in hits on your subscribed filter lists, simple but also drags down performance and memory usage (i.e. ABP in Firefox).

    I've been a long-time advocate of uBlock and is much more efficient at this type of job, a shame Maxthon didn't choose it for replacing AdHunter.

  8. An interesting proposition but I think it's best to use VPNs through the use of OpenVPN. I tend to use Vpnbook since they are a free service which accepts Bitcoin donations.

    But yeah, while VPN add-ons would be a 'good' addition to Maxthon's extensions I don't think it's the 'best'.