Contact
Email, and only email
There is no ticket system, no chat widget and no phone number. Five volunteers read a shared mailbox when they have time. Replies typically arrive within a few days, faster if something is actually broken.
| Address | For |
|---|---|
| hello [at] eu-media-relay.xyz | New station requests, general questions |
| ops [at] eu-media-relay.xyz | Technical problems with an existing mount |
| nodes [at] eu-media-relay.xyz | Offers to host a relay node |
| abuse [at] eu-media-relay.xyz | Reports of misuse of the network |
Addresses are written out to slow down harvesters. Replace [at] with @.
Asking for a mount
Tell us, roughly:
- Who the station is and where it broadcasts from.
- What the programming is — live, automated playout, or a mix.
- Peak concurrent listeners today, and what you expect in a year.
- What encoder you use.
- Whether you are commercially funded. If you are, the answer will be no, but it saves everyone a round trip.
We do not need a formal application, a letterhead, or a description of your mission. Four sentences is usually enough.
Reporting a problem
Include the mount name and a timestamp in UTC. We keep no per-listener records, so reports of the form "a listener said it was broken last week" cannot be investigated — by the time it reaches us there is nothing left to look at. If a problem is ongoing, say so explicitly; that changes who picks it up.
Abuse
If traffic from one of our nodes is causing you a problem, write to the abuse address with the node hostname and the time window. We respond to these first, ahead of everything else. Note that our nodes originate only outbound audio streams to listeners who requested them; we do not run crawlers, mail, or general-purpose proxies of any kind.
Press and research
We are happy to talk to researchers looking at community media infrastructure, and less happy to be a case study in a vendor's marketing material. Either way, use the general address and say which one you are.