I'm still using Firefox, although quite customized.
- Adblock Plus, with non-intrusive ads disabled (on tablet: uBlock Origin)
- Add to Search Bar
- Black Youtube Theme
- Classic Theme Restorer
- Download Status Bar (set to remove download history)
- DownThemAll
- Exif Viewer
- Flashblock
- Google search link fix
- Grab and Drag (set to grab a web page with the right mouse button)
- Greasemonkey (scripts: "Fanfiction.net - Make text selectable again", 4chan X)
- Image Search Options (searches images in IQDB)
- Image Toolbar (copies/saves images with one click)
- Reddit Enhancement Suite
- Switch to Tab no more
- Tab Mix Plus
- Tree Style Tab
- Video DownloadHelper
I would consider Chrome only if there's something comparable to Tree Style Tab.
It's still available via torrent and other filehoster links set up by users.
Apparently there was also a counter (for a month or so?) and the project was public for several years, so there's no way Nintendo didn't know about this. That they sent the takedown notices a day after the release seems quite deliberate.
Maybe in Nintendo's mind there's the impression that for a fanproject's producers there's a small step between "yay, we did create a thing" and "hey, we could probably make some money with it", and that's what they don't want.
I don't think that "movie" is at all inaccurate: movie files need two pieces of software to be played back, a media player and a codec; if you don't have one of them, you can't play the movie. For TAS movies, the emulator is the media player, and the ROM is the codec; if you don't have one of them, you can't play the movie.
And embedded savestates would be keyframes.
marzojr wrote:
Just as with other movie files, the exact movie format defines the kind of metadata that is contained in the file: GMVs don't support subtitles, for example.
That said, I will agree that it is useful to distinguish between "emulator and ROM" movies from "media players and codec" movies. I don't really like any of the suggested terms, and I don't have a better option.
I think "keypress file", which I have been using here, is a much better term. It's much more accurate, and causes a lot less potential confusion. It gives a much better picture of what kind of file it is. Of course it's not the only option. Maybe "button press file", or "controller input file", or something along the lines.
A movie file can contain much more than keypresses: reset button presses, savestates (comparable to keyframes in video files), author info, comments... Theoretically you could even include instructions for controlling the whole interface, including loading ROMs, connecting controllers etc.
Down to just 2 tests, scnaline and TVpassfail. I'm not really interested in the TV one since it's just a filter, maybe I'll do it eventually.
So it's not important then? I'd like if you could tell me more about TVpassfail (what we'd be missing out if it's not accurate). I like learning about those little things whenever possible.
