I am learning how to #draw by spending time every day with a #reference render 🎨 #DailyArt Production #107 🖼 Theme(s): #nature #calm #scenery ✨ Reference Source: #Midjourney generation ⏰ Time spent: 30 minutes 🎶 Listening to: youtube.com/watch?v=dUg2rKVi… 📝 Notes/thoughts: "Back into nature after a few days off" #DigitalArt #Illustration #sketch #pencils #GetLeonardo

.@StarbeamOne Daily Status - Woof, I swear product (and software) development is 99% grief and 1% bliss. Creators, you know it's that 1% that keeps us going. Case in point yesterday I finished the fifth step on the New Publishing Wizard and was so very happy to see what is taking shape. 🤩🙏 To start, it's beneficial to mention that when I started sb1 I wanted to create something that offered a productized experience. You aren't just purchasing an image (or video, as shown below), you're purchasing a product. Much like in the days of purchasing a cassette tape, CD, or album, you get the content (media) but you also get the packaging around it, which may have its own artwork. As far as I know, no other marketplace does this. And I didn't want to stop there, either. The other fundamental value to me was to protect the content. Every NFT marketplace right now exposes the source file for public download. To me (and others such as NFT Bay -- link in the comments -- which expose this), this is a design defect and greatly reduces the fundamental value proposition of the offered experience. It turns out that protecting the content is monumentally more expensive and time-consuming, but I have been up to the challenge. If you don't expose the source file, then how do you know what you are purchasing? 🤔 Well, you offer sample files. But if you don't have a way to do this, how do your users make sample files? All sorts of confusion abounds. Especially when most of your customers are NFT artists anyway and are used to selling source files (because culture). In v1 of sb1 I don't think one artist got the upload experience correct, particularly with video files. This was a sore point for me as it reflected on me to get it right, which was not the case. So for this next version, I wanted to make sure we got it right and reduced the amount of confusion involved around the process, up to and including the sample files, which I demonstrate below. If you'll notice, there is very little work being done here, and both a storefront and a product are generated for you, along with the necessary files to demonstrate what is being sold. While very little work is done I still would like to optimize the process even further at some point, reducing the clicking in the wizard and simply having a "drag and drop" publishing experience. That may have to wait until v3, however. 😅 Until then, please enjoy the progress below. I know I have. 🙏 Finally, a quick shout-out to @JohannaNyqvist for the wonderful art that I have been using to test this new feature. It's a worthy and appropriate product if I do say so myself. 😊 youtu.be/A5NB9DugJ2s?si=0gxw… #DailyDeveloper #Status #BuildingInPublic

.@StarbeamOne Daily Status* - Did you know that Firefox cannot play .mvk files natively? I have been running an application that utilizes this format for over two years now and learned this yesterday. 🤦‍♂️ I guess there are perks to debugging in Firefox after all. 😁 All this to say that bug-crunching continues here on the New Publishing Wizard. I feel like I have another day or so to get this completed. I know I have been saying this for several days now already but I still have hope. 😅 #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `space station in another universe made of shiny neon glowing metal , in the style of found object art, epic lighting`