Love this website! The comments here are perfect for a quick browse whilst getting my shows. I don't do MAL or Plebbit anymore as an intended 5 minute browse can easily become 5 hours of faffing about!
What about a page here for general comments and recs on the current season as it unfolds?
Really looks like that. I would've bet, nobody uses a unpatched oldstable mkvtoolnix for such an environment. Should have several vulnerabilities up to arbitrary code execution with rights of current user. Their user service seems to fit the same level of laziness, I guess.
I think the uploads are going through, but I'm seemingly getting a lot of missing articles. The uploader does slow down and retries posting when it encounters these issues, so the uploads are going slow.
If the file is wrapped in a 7z archive, after extraction, it should be identical to the file AT downloads. If you find a discrepancy, please do let us know. If the file isn't wrapped in a 7z archive, it likely won't be identical, but probably is fine otherwise.
back to normal? go4up has been fiddling with crc for years, one way or another. It's generated no complaints except by those who worry about crc. You probably read admin's note about wrapping those media files in a 7z. I haven't seen any reports about the effects of that.
if you worry about crc you've probably not been using go4up. If you've been using go4up you've probably not been worried about crc.
Is Go4up back to normal? Like, If I DL from solidfiles through Go4up, is the file going to be exactly the same as one DL'd from eg openload? Like same filesize and hash and so on?
Well the theme is called Yoshino, so that's probably her name. Then just narrow it down to characters named Yoshino in shows that aired that season. Obviously not something I watched, but give me a little time to do the groundwork and I'll see if I can figure out which show it is.
you should've at least say what client you use. For tixati: 1. CLick "Layout" button, click "select columns", tick "UL Ratio" then click "Close" 2. or click on the torrent you want to check, then click "Details" tab
Thanks for enabling the 7z archive container. Relating mkvmerge, yes probably not a good idea to mux recent formats (Opus, h.265) with a version released nearly five years ago. Not to mention, that there were also h.264 fixes all over the place: https://mkvtoolnix.download/doc/NEWS.md It's likely, that they use the old version to get some tempering by bugs and missing features.
This is interesting - thanks for bringing that up. I believe Go4Up have been applying their "MD5 changer" for a few years now. A few years ago, it was just appending '0' bytes to the end of the file, which should be harmless and not cause anything noticeable other than a size increase and hash difference. If you're seeing reprocessing by mkvmerge though, that's something completely different, and BetaMAX seems to suggest the same below.
I haven't really looked into it yet, but from the sounds of things, I'll probably wrap Go4Up uploads in archives, as you suggest. --- Downloaded a random file and did a bit of a comparison. Extracted video and subtitle streams, as well as attachments were identical. Audio didn't hash match, however, I couldn't find a difference comparing the audio data itself (maybe older mkvmerge had issues with Opus muxing or similar?). So I can't really find anything obviously wrong, apart from the fact that they've just remuxed the file for whatever reason. I'd say that the files are likely fine most of the time (except where there have been issues with older mkvmerge versions), but I have no idea why they'd go to the effort of doing this. Looking at their news, they claimed some streaming support - perhaps something related to that?
Regardless, I've enabled 7z wrapping for Go4Up. If it works well, I may also enable split uploads to Go4Up (disabled when they started padding their files, as joining becomes non-trivial).
I got a screen of 3 boxes of php errors and a box that asked to use my processor for download, then my Norton Security popped up with a High Security warning of an intrusion attempt that it had blocked:
IPS Alert Name: Web Attack: Unwanted Extension or Scam Sites Redirection -No action was required because Norton had blocked it. Norton also notes that it matched the signature of a known attack.
Has their site been hijacked?
Anyways, I wouldn't use go4up for now.
(I clicked on the go4up site name. There was no drop down menu at that time.)
Having been an computer admin at a research university, from an administrative point of view:
1. Make minimal assumptions 2. Don't screw things up for other people.
Because you personally have multi ddl-service options, don't assume everyone does. I recall complaints in Feedback when go4up was not available.
At this point a warning is all that seems warranted, pending additional info. If you don't need to make decisions for other people, like removing a service, don't. You'll generally be happy you didn't.
Doesn't look system/browser/IP related to me. I'm using a bash script in linux, that fetches the final DL url and downloads via wget or aria2. Same behavior in this case. I've tried to run wget with a current chrome user-agent and/or a proxy. Downloaded file stays the tempered version.
So it seems rather clear, the files are manipulated by go4up (only). All hosts most likely deliver what they get. If this is a try to avoid multi-deletes (deletion of all links that refer the same storage blocks), this is more than poor. Aiming unclear.
Comment in Feedback 30/03/2019 09:31 * — Anonymous: "Lizette Hoskins"
There might be the question if just a certain condition (Land, ISP, OS, Browser, Date, Go4upSub, Host + Hash Method/Result) is causing this. Your post, trough a legit suggestion seems too early. It just seems since yesterday and we don't know which users it act. does affect. (If all users using go4up could report all these details with their results we might get some indication.) Due to the missing information it might be a bit to early for admin to change scripts too. FE I did test 2 files with incl crc + AT sha256 (Problematic using VPN in SWE, -.-, Win 10 1809, 17763.379, Basilisk 19.3.27 + Jdownloader 19.3.29, 19.3.29, Zippy+ Openload: Hash ok // go4up->solidfiles + tusfiles fautly). So if some1 could test some linux system with non ff-based browser. If it's still the same, we don't know if it's some go4up temp problem, persistent or even intended. Even if it's persistent or esp just if that's the case a request to change the upload technique is legit.
Can you cite a modern example of an actual infection/Trojan problem in the field with an mkv? Silly question for you. There would be headlines and references to spare.
If you want to yell something in a crowded theater, specify whether it's smoke, fire, or hot soup you are bothered by.
And let's add the last factor: That whatever this is, it is not from a random source, it is go4up, part of the ddl-service industry. Go4Up would be cuttings its own throat and its clients as well if it did something malicious to their own customers. But that must be the "beta" theory.
-------------------------------------------------
This exchange I think was useful in that users can now decide for themselves. No harm in moving to a different aggregator like MultiUp or Jheburg if you can get the ddl-service you want. As to giving up your favorite service, your call. And I expect admin will remove go4up if he feels he should.
I care about files integrity, nothing more nothing less. No need for speculation. It's probably not related here, but "And media files are not dangerous." LOL Ever looked into the commits in ffmpeg git? Silly question, I know.?
So you're just worried about a blip or failure in playback. A blip in playback is nothing. To most of us, dangerous is what makes something unusable. And media files are not dangerous.
Since there have been no complains here about files that have blips or don't play from go4up or anywhere else, your concerns are clearly without basis or merit.
Well, should be obvious, but just for you: If you don't care about data integrity, it might still be usable. Adding some bytes at end of file, that can be removed to perfectly restore the file, is totally different from current behavior.
This is so sad, I don't even have words to describe how sad this news is D : Thanks for all the work on the ddls, I got some rarities and other impossible to find files from here.
Is go4up messing with MKVs? I noticed bad CRC, and the file was reprocessed by mkvmerge 7.3 (original file was made by 31.0). Maybe they are doing something sneaky like inserting ads (though I couldn't find anything in the file I looked at)?
Anyway I suggest wrapping the MKVs in ZIPs or whatever if go4up is screwing with us...
05/04/2019 15:03 — Anonymous