I really hope "banged" is a typo for "banned"...
482 karma · joined July 12, 2020
Writing https://devtails.xyz
Started with just recording the canvas using MediaRecorder (https://devtails.xyz/@adam/how-to-record-html-canvas-using-m...). This was super simple and I wish could have left it at that...But unfortunately Chrome gives you a webm file back and IG doesn't let you upload webm.
So then I went the route of ffmpeg.wasm in the browser to convert the webm to mp4.
I've finally landed on an approach that uses the WebCodecs API and mp4-muxer library (https://devtails.xyz/adam/how-to-save-html-canvas-to-mp4-usi...).
I'm working on a similar tool https://kaizen.place/reel-generator . Moved the video rendering onto the client which helps keep rendering times quick and avoids the headache of managing an extra service.
+1 to the suggestion I saw for some kind of sound visual to make it even more clear there's audio.
As for music licenses, we are seeking out legal advice as how to best approach. I'm hopeful we can land on something as simple as Github licenses.
Nothing requires an artist to receive tips through the platform, so if they preferred buymeacoffee they can use that. We will be adding additional features to our Pro plan that will enhance the experience on top of bringing the fees to a comparable 5%.
Again, still early days. Appreciate the feedback, we will work with artists on the platform to find what works well for everyone.
Bandcamp, for comparison, charges a 15% fee.
We are still early days and will continue to solicit feedback on our pricing model.
Writing forces me to break things down into manageable chunks. I’ve seen much more consistent progress this way.
Mainly focused on learning rust while streaming. Streaming forces me attempt to explain what I’m doing which often shows me what I don’t properly understand.
I would probably condense my definition to how quickly can you go from new code added to someone seeing that code running (in web dev terms essentially available on some URL). So even if you had different layers of pipeline, the build artifact stage would still be included, because you can't deploy without it.
I'm still getting familiar with all the different tools involved. You mention Turbopack as something that will speed up production builds, but I'm seeing similar build times (using npm run build) with that demo project (npx create-next-app --example with-turbopack) as I was with the normal Next.js toolchain.
Is there any way to have the production build re-use build artifacts from a previous build so that my 1 line code change doesn't trigger an entire rebuild?
I'll update the article with a production build. I originally planned to do it, but then copped out (partially because I wasn't sure how to, so thanks for the pointers).
I agree with your final statment, but have begun to wonder whether there's a simple enough way to accomplish the same goals, while being performant by default. We'll see where I land after further explorations.
I'll see if I can give this a try this evening
I may give this a shot when I have some spare time.
It appears to turn on briefly and then turn off again. This seems to break my understanding of the browser security model as that domain is definitely not allowed access to my camera.
Any thoughts?
A long time ago I sketched out a note-taking app that I was excited about. About a year later I stumbled on Notion and saw that the core idea of hierarchical notes was accomplished wonderfully.
I figured there was no point building something that would essentially end up becoming a Notion clone. I proceeded to use Notion regularly (and still do) - but I have come to see that with flexibility comes other challenges.
I often found myself on a walk or at the gym wanting to capture a random idea that just came to mind. Unfortunately, doing so in Notion (and pretty near most notes apps) was laborious. The app would open to the last page I had open - which was usually not where I wanted this new random idea to go. Even if I was in the right place, the text editor on mobile was clunky.
engram organizes notes by day and type (note, task, and event). I've found with these primitives, I don't need to fumble to get things organized. Instead, ideas can be submitted independently and out of order. Storing them by date keeps recent and relevant data within reach.
Final thought - engram is not intended to replace all note taking capabilities. Instead, it acts as a place to capture the unfiltered thoughts before you lose them. From there they can be further fleshed out in a more organized fashion using your preferred method.
Dubsado helps businesses stay in motion. Build relationships, schedule appointments, and create workflows to streamline projects from start to finish.
Looking for talented people all across the stack. Mongo, React, Node, GraphQL are some of the main technologies we are using.
Who we are: https://www.youtube.com/watch?v=PyCv4wtu0ik
Apply at: https://www.notion.so/Dubsado-Job-Board-d122c307a4bb4025a9c4...
After struggling to find a digital version that I liked, I decided to build my own. It's still quite early in development, but it focuses more on bottom up thinking which I've found particularly helpful when brainstorming.
Engram - Open source knowledge management app
Still pretty early on, but I'm excited about the possibilities. This is the first time I'm using an app I built daily.