I'd suggest https://aws.amazon.com/elastictranscoder/details/, its quite affordable and much easier than doing it yourself, assuming it does what you need.
From the research I've done, I'd suggest MPEG-DASH for reasonable cross-ish platform adaptive streaming without requiring fancy video servers. Your requirements and platforms might be different than mine though. Research is required.
Licenses are always complicated, but when I contribute to a project GPL licensed, I expect any changes to be GPL too.
I'm not a lawyer, but studied licenses to understand which projects I can use.
About a year ago I started getting into photography and wanted to buy a good DSLR or mirrorless camera. I found the process of researching cameras and lenses to be far from optimal.
There were lots of review sites with extensive reviews, but it required lots of time Googling around and separating the wheat from the chaff. Later I wanted to buy a wide-angle lens and had to repeat the process. I found bits of useful info here, and some more there, but in between found loads of misinformation and useless sites inundated with obtrusive ads.
Through my research I found it very useful to look through sample images taken with the equipment I was considering for purchase. I found the process of finding images taken with a particular camera or lens also to be very time-consuming.
So my goal for this site is to build a database of useful resources for camera equipment. Right now all of the equipment I've listed myself along with reviews that I found to be useful. However I've built in methods for submitting equipment for review as well as submitting links to useful resources. My next task is to add voting for resources to help surface the best reviews and image galleries and bury those that are a waste of time.
I'd very much appreciate feedback, positive and negative to help me shape the site.
I feel like something that simply 302'd the user to the most recently posted URL would make more intuitive sense, but with obvious drawbacks.
It's really only useful for a small list of file formats. Doesn't really do much for you if you primarily use s3 for binary data or static web hosting.
If you're selling iOS apps, you have no choice but the app store. You could try giving the app away for free on the iOS App Store and shunting people to a website to purchase the license after a certain amount of time, but I'm certain that breaks Apple's rules. Same goes for the Mac App Store.
You'd get shut down pretty quickly if you ever managed to squeak through the approval process.
Based on the code examples provided on the website, I don't see any of the most popular languages use for apps that go in an "app store" of any kind (Obj-C, Swift, Java)
I'm sure intent is not to be misleading, but I don't see how this can recoup a 30% app store take. Could you explain that in more detail, since you are replying in this thread?