{"id":501,"date":"2008-01-10T08:55:00","date_gmt":"2008-01-10T16:55:00","guid":{"rendered":"http:\/\/multimedia.cx\/eggs\/catchy-name\/"},"modified":"2008-01-14T12:52:28","modified_gmt":"2008-01-14T20:52:28","slug":"catchy-name","status":"publish","type":"post","link":"https:\/\/multimedia.cx\/eggs\/catchy-name\/","title":{"rendered":"Catchy Name"},"content":{"rendered":"

I’ve been working hard on the FFmpeg automated build\/test server<\/a> in the last few weeks. I’m planning new test configurations, plotting the specs for hundreds of different automated tests, and stabilizing the general infrastructure. But I’m missing something key– I don’t want to keep having to refer to it as the FFmpeg automated build\/test server. I need a catchy name for it.<\/p>\n


\n\"Baby<\/a>
\n<\/center><\/p>\n

Any ideas? I realize that free software types are not the most creative lot, but it’s worth throwing the question out there anyway.<\/p>\n","protected":false},"excerpt":{"rendered":"

I’ve been working hard on the FFmpeg automated build\/test server in the last few weeks. I’m planning new test configurations, plotting the specs for hundreds of different automated tests, and stabilizing the general infrastructure. But I’m missing something key– I don’t want to keep having to refer to it as the FFmpeg automated build\/test server. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[101,3],"tags":[],"class_list":["post-501","post","type-post","status-publish","format-standard","hentry","category-fate-server","category-open-source-multimedia"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t