Closed saerdnaer closed 9 years ago
Nice idea. We could introduce a short URL field for events.
The VOC API client would have to send this field for new events. Someone would have to edit all the old events, though.
And we'd have to modify the write every file twice to disk, we should evaluate if that's possible with nanoc rules.
What's about a redirect file for the webserver? What kind of webserver software are we using currently?
Nginx, but I don't want to install 1800 redirects as root.
For new events, now the url looks like this: https://media.ccc.de/v/gpn15-6678-babelbee_-_das_open_source_stromnetz_analyse_projekt ... So I think we can close this issue, or should we also shorten the slug for the older events like https://koeln.media.ccc.de/v/gpn14_-_5853_-_de_-_medientheater_-_201406221300_-_spaceautomatisierung_-_schinken ?
It should be possible to access a recording via it's (local) event id and not only via the full slug.
e.g. http://media.ccc.de/browse/conferences/gpn/gpn14/gpn14_-_5853_-_de_-_medientheater_-_201406221300_-_spaceautomatisierung_-_schinken.html
should also be accessible with
http://media.ccc.de/browse/conferences/gpn/gpn14/5853