The purpose of this wiki page is to coordinate and combine upstream developers of various FLOSS projects that aim to help and provide services to users in terms of viewing, listening and downloading video and audio content from various places on Internet. Purpose of this is to easy the creation of wider and bigger picture of FLOSS ecosystem surrounding this specific field so interested parties could discuss a possibility of one unique/universal software/library that would benefit developers and in that line all our users. Bonus part is UI front-end for such software.


Package Name

Interface

Language/Framework

Sites

Comment

cclive

command-line

C

encuentro

graphical

Python

Encuentro Argentinian channel

fatrat

GUI

C++, Qt

get-flash-videos

command-line

Perl

many

get_iplayer

command-line

Perl

BBC iPlayer

glyrc

CLI

C

gpodder

GUI/CLI

Python

groovebasin

GUI

?JavaScript, NodeJS

WWW::NicoVideo::Download

library

Perl

Niconico

WWW::YouTube::Download

library, command-line

Perl

YouTube

MediathekView

graphical

Java

German public TV channels

minitube

GUI

C++, Qt

mplayer2

GUI/CLI

C, SDL

mps-youtube

CLI

Python

mpv

GUI/CLI

musique

GUI

C++, Qt

nicovideo-dl

command-line

Python

Niconico

node-ytdl-core

library

?JavaScript, node.js

YouTube

nomnom

graphical

C++, Qt

pafy

library, command-line

Python

YouTube

python-iview

command-line, graphical, web

Python, GTK/Tk

ABC iView

not in Debian, many forks

quvi

library, command-line

Lua, C, C++

several

slimrat

GUI

Perl, GTK

slimrat-nox

CLI

Perl

smtube

GUI

C, Qt

svtplay-dl

command-line

Python

several

tribler

GUI

Python

TunesViewer

graphical

Python

iTunesU

webdl

command-line, console

Python

Australian public TV channels

not in Debian

you-get

command-line

Python

many

not in Debian

youtube-dl

CLI

Python

Notice: Features should be comparable things between listed packages. What things should we compare (so features section doesn't get to big burden to maintain and its easy to scroll through relevant information)?

In Wikipedia, the classic way of doing this is breaking the table in multiple components - say a "General" section that has language, interface, last release date and so on. Then there could be a separate section with a grid of player/site support matrix... -- TheAnarcat