Is MEGA legit?

[T]

mega:///#firefox

legit or junkware?

[Chris Ilias]

On 2017-03-01 6:26 PM, T wrote:
> mega:///#firefox
>
> legit or junkware?

Could you please provide more details about what you're referring to?

--
Chris Ilias <http://ilias.ca>
Mailing list/Newsgroup moderator

[Caver1]

On 03/04/2017 12:34 PM, Chris Ilias wrote:
> On 2017-03-01 6:26 PM, T wrote:
>> mega:///#firefox
>>
>> legit or junkware?
>
> Could you please provide more details about what you're referring to?
>

Mega is a cloud storage company, yes it is legit.

--
Caver1

[Good Guy]

On 01/03/2017 23:26, T wrote:

mega:///#firefox

legit or junkware?

If you are talking about MegaUpload then I suggest search for Kim Dotcom.  Kim owns it and he is currently based in NewZealand as he is wanted by FBI for money laundering and piracy.

Apart from this there is nothing more to say.

--

With over 500 million devices now running Windows 10, customer satisfaction is higher than any previous version of windows.

[T]

Thank you!

[Chris Ilias]

So there's no confusion, Mega is not part of Firefox, and it is not
developed by Mozilla.

[Caver1]

On 03/05/2017 11:28 AM, Chris Ilias wrote:
> On 2017-03-04 10:03 PM, T wrote:
>> On 03/04/2017 10:01 AM, Caver1 wrote:
>>> On 03/04/2017 12:34 PM, Chris Ilias wrote:
>>>> On 2017-03-01 6:26 PM, T wrote:
>>>>> mega:///#firefox
>>>>>
>>>>> legit or junkware?
>>>>
>>>> Could you please provide more details about what you're referring to?
>>>
>>> Mega is a cloud storage company, yes it is legit.
>>
>> Thank you!
>
> So there's no confusion, Mega is not part of Firefox, and it is not
> developed by Mozilla.
>

True. Mega does have an extension for Firefox which I don't
use as I see no benefit.

--
Caver1

[T]

The time I tried it, it seemed like a bandwidth hog,
which was what I wanted anyway. I removed the extension
right after I got my ISO downloaded

[VanguardLH]

Caver1 wrote:

> T wrote:
>
>> mega:///#firefox
>> legit or junkware?
>

> Mega is a cloud storage company, yes it is legit.

So what has that to do with a protocol created called mega? Some apps
will create their own protocol definitions. Symantec had one for their
anti-virus program but I forget what it was called. mega:///#firefox is
not connecting to a site. http://<site> is using the HTTP protocol.
mega:///#firefox is a local protocal pointing at localhost but with no
filespec and with a page anchor of firefox (a location in a web page).
So not until I looked in the registry to find the mega protocol
definition could I know what it does. I can find the typical protocols,
like file, ftp, gopher, http, https, mailto, and so on but there is no
mega protocol defined in my registry. So something the OP installed
defined that protocol.

The OP didn't ask about http[s]://mega.<tld>. He asked about a protocol
called mega, the part BEFORE the colon delimiter. It is possible
something added an internal protocol definition (aka internal URI
schema) solely within Firefox, like an add-on. Native Firefox doesn't
have an internal mega:// protocol defined. It has about:, chrome:, and
resource: protocols. For example, and still supported in Firefox
(dropped in Internet Explorer supposedly for security reasons), is the
view-source: URI scheme (e.g., "view-source:http://intel.com). Since
the scheme aka protocol is defined internally, it can be any name (and
possibly even override the protocol defined in the Windows registry).
I've not heard about a mega: protocol.

https://addons.mozilla.org/en-US/firefox/addon/imega/

I don't know if that adds its own protocol within Firefox. T didn't say
what add-ons are installed in his client's Firefox.

https://en.wikipedia.org/wiki/About_URI_scheme
https://www.w3.org/wiki/UriSchemes

This article mentions add-ons can add their own t: URI scheme to
Firefox:

https://mike.kaply.com/2011/01/18/writing-a-firefox-protocol-handler/

That uses the old NSAPI method of writing an add-on. Since Mozilla has
or will drop NSAPI support, such an add-on is doomed to old versions of
Firefox.