BillH99999
-
Posts
850 -
Joined
-
Last visited
-
Days Won
2
Content Type
Events
Profiles
Forums
Posts posted by BillH99999
-
-
-
I have all of them installed side by side on my PC.
Edge Chromium just went live as a beta. I'm not sure when it will move from beta to general release. I haven't had any problem with the beta although the dev and canary versions have more features which I'm guessing MS will be rolling into the beta before ii is moved to general release.
To install Malwarebytes Browser Guard in Edge Chromium just open Edge Chromium, go to the Chrome Web Store, and install MBG. Any Chrome extension can be used in Edge Chromium as far as I know.
-
Just as an FYI... you can install the extension in the new Edge Chromium browser which is in beta testing. Just open Edge Chromium, go to the Chrome web store and install it from there just like you would install it into Chrome. I did this several months ago and it is working just fine.
-
Just as an FYI... I have been running the Canary, Dev, and Beta versions of the Edge Chromium browser for several months with Malwarebytes Browser Guard installed and it works fine. So far no problems at all.
-
-
Thanks for the reply. I agree. I use both uBlock Origin and Malwarebytes myself. Today I just turned uBlock Origin off for awhile to see if Malwarebytes would catch things by itself on some sites. This was the only site I tried that Malwarebytes didn't block. Thought I'd report it just to help you build up your database. If I run across others I'll report them as well.
Bill
-
-
I don't know how many times I've looked at that window and not seen that... he says embarrassingly.
Bill
-
I didn't realize only the last 30 days worth of reports were kept. I thought they were kept forever in version 3. I missed that this had been changed in the beta.
I haven't had the beta installed for 30 days yet so hadn't realized the old ones were going to be deleted automatically. This will be just fine with me... I just didn't want them to be kept indefinitely.
Thanks!
Bill -
I used to use these checkboxes to select the reports I wanted to delete and there was an option to delete all the selected reports. I may not want to delete them all, but deleting them one at a time is a pain if there are a lot I want to delete (for example, I may want to delete all but the last 2 weeks worth).
I don't see how to do this now. Rather than removing the check boxes, maybe you could add back the capability to delete all selected reports.
Thanks,
Bill -
No problem. It is much better than it was before. I can live with a couple ads, but I look forward to you being able to suppress the AdChoice ads as well.
Thanks,
Bill -
Oh, I just saw that @AdvancedSetup already reported this ad getting through without being blocked. My report can be ignored.
Bill
-
1 hour ago, Nate-Dogg said:
and due to your most recent update which exchanges data with co-operating websites, please expand on this.
Can you expand on what this new permission is doing? What data is being exchanged? What co-operating websites?
-
I don't know. I've had very poor results with controlling AdChoice ads so I hope MB will block them. It seems like I try to block one and I just get a different one.
-
-
-
No need for apologies. I am just glad you are coming out with a resolution soon.
Thanks,
Bill -
Agreed.
-
I guess what I was saying is the same as what I think you were saying in your earlier post. We were not given the release version after they modified it from the beta version. We were able to test a beta of 1.0, but a lot changed between 1.0 and 2.0. I would have like to have been able to beta test what was released as 2.0 before they released it... maybe beta 1.99. In my day we would have given the users 2.0 to test before we ever released as production. One last chance to catch any problems before going live.
Bill
-
5 minutes ago, exile360 said:
That used to be how we did things. It was a pivotal part of our release process. No untested code was ever to be published as a final release product. Each build had to go through a full round of testing prior to being released, and if any change (even minor) is made to the code (for example, fixing a last minute minor bug or adding a last minute feature/change) then the resulting new build had to go through the entire full testing process prior to being released because we were burned too many times by builds going live with seemingly insignificant changes that resulted in sometimes catastrophic failures and issues due to unforeseen consequences to those changes in the code. I understand that public beta testing is not necessarily a requirement for Malwarebytes product releases and that it may be an optional tool utilized when they are seeking a wide range of test systems, variables and product feedback, however I've always found it to be invaluable in helping to ferret out those elusive bugs that no one in QA ever seems to find until a drove of customers/users start hitting the Support channels with widespread reports of the issue. Public beta testing helps to avoid this by having the product tested on a larger diversity of systems and configurations rather than a number of relatively pristine VMs and test systems.
Again, I completely agree. I was in technical support in an IT department for over 30 years. We ALWAYS did an acceptance test by the customers after our unit (module) and integration testing was completed. We could not move to production without acceptance by our users.
Bill
-
5 minutes ago, exile360 said:
I just wish we would have been able to actually test this version of the extension in beta before it was actually released as the final build/version, because it appears to work very differently from the builds we were testing before it went final and multiple bugs which were not present in the last betas have already been discovered and reported in this final release. Kinda defeats the purpose of beta testing if you are going to make any changes to the code in the final release version because you're basically pushing forward with a completely untested build (I'm sure it was tested by QA internally, but still, that's a minuscule amount testing/systems compared to the full public beta).
I completely agree with this!
Bill
-
This is still broken in Malwarebytes Browser Guard 2.0. Enabling the protection for Ads causes all images on the page to be greyed out rather than displaying them as indicated in my original post in this thread.
As with the earlier beta versions, it works fine in the Edge Chromium browser. Images are displayed even with the Ads protection enabled.
Bill
-
Thank you for the explanation.
I did not enable the extension due to my concerns so I never got this screen. I think there are other people who are not getting the extension because of their concerns. I think you would be doing yourselves a great favor by stating this clearly on the web extension page in the extension stores for each browser.
I removed the extension, added it back, and enabled it and got the screen and was able to input the email address I wanted to use.
If only it had been made clear before the new version of the app was released, I think there would have been much less concern by a lot of folks.
Thanks,
Bill -
That only answers a small part the questions in my last posting.
It would be nice if someone from MB would clarify exactly what email address MBG will access on Chrome. Is it the email address for the Google Account that the Chrome Browser is signed into? If that is the case, what email address will be accessed on Firefox? I don't have a Firefox account. I use Firefox browser without signing into an account. What about when I use the extension on MS Edge Chromium? What email address will you access?
Bill
False Positive?
in Chrome
Posted · Edited by BillH99999
@gonzo
Thanks for the whitelist entry. Why when I click on "I want to continue to the site anyway" does It just open another tab with this same block. I thought this would allow me to continue on to the site.
Thanks.
Bill