[TV] South Park S20E05 | Megalinks MegaDB

[-] indigo6alpha | 10 points | Oct 20 2016 03:14:40

key | Megalinks MegaDB key: XFLSZcWVa9yZvQ8mYzJE9oF1kiXPhy8pfwsfRBh4v8Y

[-] indigo6alpha | 10 points | Oct 20 2016 03:59:34

720p x265 | Megalinks MegaDB 720p x265:

Link

key | Megalinks MegaDB key: G7JfbT1QvMMx1XaYVg4Mj2pKJLvN7T-bJMcA31fWtOg

[-] Glenn20 | 3 points | Oct 20 2016 04:09:59

Thanks. I appreciate the 265 so much more having limited net speed.

[-] TheGoodSheep | 1 points | Oct 20 2016 09:55:59

Thanks, mate, my internet is pretty slow atm so I really appreciate small uploads, especially for TV shows.

[-] 95teetee | 1 points | Oct 20 2016 18:14:45

thanks from me too- I have good internet speed but still like to keep smaller files for everything, especially TV shows.

[-] MaxIsGreat29 | 1 points | Oct 20 2016 03:15:55

Great, thanks for uploading this!

[-] conchordz | 1 points | Oct 20 2016 03:17:13

you are the man!

[-] aaa9953a1ea2 | 1 points | Oct 20 2016 03:17:25

thanks famlam

[-] davil124 | 1 points | Oct 20 2016 04:29:27

ty

[-] JHG722 | 1 points | Oct 20 2016 06:01:59

Why is Firefox blocking Mega links?

[-] Ultra-Rider | 1 points | Oct 20 2016 06:44:37

I had the same problem come up. I got an error that said: "The address wasn't understood. Firefox doesn't know how to open this address, because one of the protocols isn't associated with any program or is not allowed in this context. You might need to install other software to open this address." Did some poking around and found some advice here: https://support.mozilla.org/en-US/questions/1022232

It suggests to 1) Reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files. 2) Clear the cache and remove cookies only from websites that cause problems. 3) Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem. (the instructions for those processes are at the link if you need them.)

2 worked like a charm, so it might be just a bad cookie/cache file

[-] JHG722 | 1 points | Oct 20 2016 07:12:18

Thanks. It was my cache for some reason.