this information broadcast system would be split in 2:
The console, where an authorized user can:
* write news
the goal is to broadcast this to ezQuake clients, thru ezquake console. details below. the news can have these attributes: nick, description, start date/time, end date/Time
example of content: "Next sunday, 31Mar, don't miss qw draft 2nd round! games start at 18cet!"
* configure qtv live commentary
The goal is to advertise live commentary (when available) when connecting to a qtv stream. In the website, the authorized user would write the event, the mumble server to connect to, the qtv stream and the start/end date and time.
This information will come to the end user, between the start and end date, when:
* he connects to the specific qtv stream, by printing in the console "live commentary at...", the event and mumble server.
* at qtv.quakeworld.nu, next to the "watch now" button, an image of a speaker, with a link to //mumble live comentary
the message would be broacasted between the start and end date/time. it would appear on the console of the client, preceded by a flashy lime "** qw.nu announcement****" (the message is to be read, and not lost between other text in the console). Ezquake would know when there's an unread message on the website, and if the time window is valid. If it is, once the client received the message, ezquake would physically write on the user's harddrive that information, so the same client won't receive the same message over and over.
about live commentary:
when connecting to a qtv server, advertise in the console that there's a live commentary for that specific stream, in a similar way of the news