Re: DuckDuckGo Browser Info?

On 6/18/2024 8:51 PM, [email protected] wrote:
> On Tue, 18 Jun 2024 23:52:35 -0000 (UTC), "Auric__"
> <[email protected]> wrote:
> 
>> carney wrote:
>>
>>> On Tue, 18 Jun 2024 17:44:28 -0500, [email protected] wrote:
>>>
>>>> Anyone ever use the DuckDuckGo browser they're advertising on their
>>>> site?
>>>
>>> Can I still have my Firefox functional, or does the DuckDuckGo browser
>>> insist it be the default?
>>
>> All browsers want to be the default browser. You can tell it to shut up and 
>> it'll stop asking.
> 
> I thought I had read in one of the groups someone complaining that
> some browser or other insisted on being the only one installed on his
> computer.
> 
> It might sound ridiculous, but who knows in this day and age?
> 

That's a rather large download.

https://staticcdn.duckduckgo.com/d5c04536-5379-4709-8d19-d13fdd456ff6/0.83.1.0/DuckDuckGo_0.83.1.0.msixbundle

Name: DuckDuckGo_0.83.1.0.msixbundle
Size: 898,246,025 bytes (856 MiB)        (The size of about 16 browsers)
SHA256: 1079C0993F9006EF5BCDBEE5D34684A1F4E4EFF7C2D787B88FC682D12B3B96D1

AV scan 2473 files, clean.

There is a 400 meg x86 and a 400 meg x64 .msix installer inside. I check
download files like this with 7ZIP file manager.

   [Picture]

    https://i.postimg.cc/J4Nq19rx/duckduckgo-browser-engine.gif

The msedge.dll is how they get the "Blink Engine" (Chrome). If installing
on W10 or W11, then the file would already be on the C: drive
(five times). Having it onboard, ensures they have a copy (to install)
if they can't detect a copy already on board. Webview2 is likely
used by other applications already on W10 or W11.

winget.exe install some.msix     # sideload a Metro App, without Microsoft Store.
                                 # Presumably for a universal app on W10 or W11.

And there is this.

https://techcommunity.microsoft.com/t5/windows-it-pro-blog/msix-core-is-now-available/ba-p/1070885

https://learn.microsoft.com/en-us/windows/msix/msix-core/msixcore

   What is MSIX Core?

   MSIX Core enables the installation of MSIX apps on previous
   versions of Windows, provided that the apps are already built
   to work on those versions of Windows. MSIX Core is built for
   the following Windows versions that don't currently natively support MSIX:

    Windows 7 SP1
    Windows 8.1
    Currently supported Windows Server (with Desktop Experience)
    Windows 10 versions prior to 1709

The file manifest somewhere in the package, has XML and text that
indicates "6.1.xxx" is supported. That sort of thing would indicate
legacy support during the build. W10 or Wll would be "10.0.xxx"
kind of thing.

The Asset section has downloads. I was unable to find another asset with a later version number.
If you can't figure out how to install it, I'd try adding one of the MSI that best fits your machine.
Maybe the DDG package already has the assets needed, but you can keep this for future reference.

https://github.com/microsoft/msix-packaging/releases/tag/MSIX-Core-1.1-release

   https://github.com/microsoft/msix-packaging/releases/download/MSIX-Core-1.1-release/msixmgr.zip

   https://github.com/microsoft/msix-packaging/releases/download/MSIX-Core-1.1-release/msixmgrSetup-1.1.0.0-x64.msi

   https://github.com/microsoft/msix-packaging/releases/download/MSIX-Core-1.1-release/msixmgrSetup-1.1.0.0-x86.msi

It could be a UWP, and with msix packaging instead of the older .msi method.

    Paul