# Pastebin scc0nCi8
Web Service Improvements

We have a WS3 version in Jira with potential breaking changes
Even if/when WS3 happens, we may have to support WS2 for another 5 years or more
First deprecate certain slow request types / inc parameters in WS2?
Example: aliases/tags are outputted for every track artist, even when they're the same as the release artist
Example: /ws/2/release browse requests - can ask for every single recording + on 100+ releases at once!
Process for announcing breaking changes to the WS
Time/visibility?
WS "2.5"
Add a very simple API key system to start?
Tie minor breaking changes to that?
Might allow us to contact people about changes more easily