Hello, thanks for checking out my launch. I made this because I couldn't get a Recorder Chrome Extension to work in the last 20 minutes of a hackathon and I had to record the demo with my phone. Afterwards I checked the analytics and the judges apparently didn't even look at the product page. I decided to go ahead and make a recorder that didn't require a download because no download means you don't have to uninstall afterwards.
@michael_muchi Thanks Michael, I was waiting for somebody to ask. This is a 100% frontend project which is why I named it Serverless Cam. There should not be any REST API calls save for perhaps Google Analytics. I used reactjs with a divjoy codebase and RecordRTC.
@bobbyzhang Interesting. I just tried it on Firefox. I have to concur with @gordon_forsythe1. Unfortunately it seems something is a little screwy with Firefox. Is there a formal place you would like us to report issues or is adding them to this thread ok?
@gordon_forsythe1@elindydotcom You can dm me on twitter haha. This is happening because Firefox thinks it's a text file. Strange because I'm setting the mimetype in the header to 'video/webm' and when I print the blob on chrome it's also 'video/webm'. I'm noticing the same problem with a few npm pkg stylesheets as well. RecordRTC is supposed to work for firefox.
Gosh my friend tried this and I only see privacy issues. The recorder was going to record her browser as well as her private files she had open for work.
@tkhonestview Its called serverless.cam because there is no backend, no servers. I understand that the permissions might be off-putting, but the recorded content is not sent anywhere, in fact it is deleted when you close the page.
Safeguard