.@StarbeamOne Daily Status* Notes: Alright, feeling a little better about progress here. Not full throttle just yet, but I was able to dig into the model and start hashing out how the artist signature feature will look. Thankfully there's a lot of work already completed in this area, as we currently have a template/control used throughout the application for global settings, topics, sub-topics, and of course the actual product when it is created for publishing. So it's really a matter of fleshing out this control and adding a sub-component to it that will represent this new feature. Hopefully by the end of today I will have a frame in place to at least have some of the controls together to display. #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `a detailed halloween starship in hyperspace, prominently featuring bright bold glowing contrasting neon colors, made of red and blue paper, in the style of origami`

.@StarbeamOne Daily Status* - I was able to finally track down the cross-origin issue. Seems like it was a bug in FireFox. 🤦‍♂️ Good thing I was developing/testing with that as that would have been most challenging running to this in a later date. I ended up addressing this by creating a new #Blazor component which I share in the comments. 👀👇 The good news is that my fix also addressed a few more issues. A lot still remain, however, and I hope to tackle as many as I can get to today. 👍 #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `starship in hyperspace, using dramatic shadows and chiaroscuro lighting to add mystery and an ominous atmosphere, in the style of metaphysical painting, featuring epic lighting, bold glowing vivid contrasting neon colors`

.@StarbeamOne Daily Status - Wow, two demonstrations two days in a row? Indeed, that is a "frist." 😎 I'm feeling a bit of downhill momentum here as features seem to finally be popping into place here with the New Publishing Wizard. 🤞🙏 The final task here was steering users to properly share files to their purchased product. As I mentioned yesterday, I don't want to be draconian about this and it's more of guiding than anything. In the end, if someone wants to get the source file it's very easy to do so. Ultimately, we want to have watermarking and more sophisticated tagging, but for now it's more proof-of-concept than anything, and demonstrate intention+direction. So you can see here we show a "Share" for the Share feature (duh 😀) but it's also available for downloading and viewing the source files. The share screen also shows up now when you try to right-click the file now. Hopefully with these pieces in place we can mitigate having users inadvertantly share source files on social media and they can share the preview files instead, thereby maximizing value to both buyer and seller. Believe it or not this step is now done and is ready to test. I will spend some hours this morning testing the different file types and then move onto the 6th and final step of the New Publishing Wizard. 👍🙏 #DailyDeveloper #Status #BuildingInPublic

.@StarbeamOne Daily Status - As mentioned yesterday there are about 3-4 days of identified cleanup tasks now that the file upload story is (finally 😊) completed. Today I will start on these and try to make it more 3 days than 4 days. 😅🤞 #DailyDeveloper #Status #BuildingInPublic

.@StarbeamOne Daily Status - SO very happy to demonstrate the video clipping feature of the Sample File section in our new file upload step within the New Publishing Wizard. Seen below, I move the start time and adjust the duration from 2 to 5 seconds. 👍✨ I am also happy to announce that the audio clipping feature is also completed, which means the primary features of this step are finally completed. 😌 This is a task that I originally estimated to take 10 days but for one reason or another took several months. 😭 The good news is that it is completed and now I can start moving onto the next step. Before that, however, there are about 3-4 days of identified cleanup tasks for this previous work. I will start this tomorrow. 👍 #DailyDeveloper #Status #BuildingInPublic

.@StarbeamOne Daily Status - *brushes off dust -- STARDUST* 🤪 Welcome back, I have returned from my mini-break and am getting back into the routine here. It's a basic day today where really the only task I have is to get this update out. 😊 With a little luck I will resume the daily art tomorrow, as well as get myself acclimated back into the code. 🤞✌ #DailyDeveloper #Status #BuildingInPublic

.@StarbeamOne Daily Status - Yeehaw I am on a bit of sugar high after all the cake and assorted sugar from yesterday's double birthday event. ☺🎂 Today I will get back into the routine -- or try to do so. We still have our laundering issue to take care of. I basically need a way to manually resolve withdrawals so that they are marked as completed and update the books correctly. In this case, the withdrawal was requested but what I really need to do is refund the Stripe card used to onboard the user. Maybe I will decline the withdrawal and immediately force a refund instead. 🤔 This might actually take some further analysis and I am not entirely happy with the whole process (about as happy as I am with someone trying to abuse our system 😤). In any case, this will take my day for today. #DailyDeveloper #Status #buildinpublic

.@StarbeamOne Daily Status - A bit of a one step forward two steps back day yesterday... I finally got the API query story working and we can now serve requests with filtering and sorting. However, it's becoming clear that the FluentUI/QuickGrid I was hoping to use will pose some unexpected challenges. While it lives up to its name and is super quick, it doesn't easily support mobile mode like our current grid does. There are also other features accounted for that I will have to implement for the new grid, and they are not trivial. This will incur another 2-3 days of development and maybe another day of testing. As I am already this amount of time behind on this task, I was not happy with this prospect at all. I took some time yesterday to analyze this and decided to re-use what we currently already have with our grid solution (Syncfusion). So now I need to convert our current grids to the new API paging calls. With a little luck I should have this done by today. 🤞 #StarbeamOne #sb1 #DailyDeveloper #Startup #Status #azure #blazor #csharp #dotnet #buildinpublic #buildinginpublic

.@StarbeamOne Daily Status - I got the solution preparation story done yesterday, which means the solution is prepped. 😊🤓 Now is the matter of improving our Azure deployments. I researched Bicep yesterday and this looks promising. It's going to be awesome when this is done as we'll have far more control over our deployments and environments -- however many we choose to have. Additionally we'll be able to standup and teardown environments pretty easily, which will help with costs. We can even have different deployment configurations which can help out with costs in general, and I am still analyzing how this can be done. Essentially, we'll have one template for when we are at a certain amount of revenue, and another when we can reach it (afford it 😊). Difficult to accept it was two years ago in 2022 when I started looking into Azure around this time. Seems fitting to re-visit now that I understand it way better. The Azure Template story should take me a few weeks. Then it's a matter of deploying v1 with these new templates, and then finally we can start working on vNext. 👍 #StarbeamOne #sb1 #DailyDeveloper #Startup #Status #azure #blazor #csharp #dotnet #buildinpublic #buildinginpublic

.@StarbeamOne Daily Status - Tomorrow is Beta III. 😌 I've basically spent the two months on quality (again) and getting key pieces in place to help administer + moderate the current application. I am almost tempted to call what we have now v1. 🤔 Everything is pretty much settled and works pretty freaking well. 😌🙏 For Beta IV (February 6th), I will be adding a completely different (and modern) way of publishing. It's almost starting v2. However, I don't want to call it this because the UI/theme will basically be the same and people might be disappointed seeing "v2" but it "looks" the same. 🤔 Product Owner Problems™ 😅 Today I might actually chill. I may start the blog post for Beta III tomorrow, which I will also be discussing on our YouTube Channel with the monthly installment of Standup & Shine. You are subscribed, right? 🤓 @StarbeamOne" target="_blank" rel="nofollow noopener">youtube.com/@StarbeamOne #StarbeamOne #sb1 #DailyDeveloper #Startup #Status #azure #blazor #csharp #dotnet #buildinpublic #buildinginpublic

#StarbeamOne #sb1 #DailyDeveloper #Startup #Status Yesterday was filled with disruption, and I am aiming to get back on track here. We found some bugs with the email address policy story and should have fixes out today. I was hoping to get this deployed today but it looks like tomorrow is finally the day. During testing, I will also get some features/extras in for the Beta II announcement, scheduled for next Tuesday. #azure #blazor #csharp #dotnet #buildinpublic #buildinginpublic

#StarbeamOne #sb1 #DailyDeveloper #Startup #Status Finally got that CPU water-based cooler in yesterday and that's been hovering over me for a month. It basically took the entire day due to several complications and I am so glad that is over. Unfortunately, it doesn't seem to have reduced the temps of my machine as much as expected, with only a 10c reduction instead of the 20-30c that I was expecting. Oh well. Maybe it'll help with the thermal throttling. 🤷‍♂️ Today I continue on with the testing of the email address policy. We're almost done with this. We found a few issues yesterday and got them ironed out as well. Then there are a few tasks I want to get situated for the Beta II Announcement which is next Tuesday. If all goes well we'll finally get that email address policy deployed into production tomorrow and we'll see how it does. 😅 #azure #blazor #csharp #dotnet #buildinpublic #buildinginpublic

#StarbeamOne #sb1 #DailyDeveloper #Startup #Status I had more luck yesterday getting some code together and made a deployment to staging for our login issues. We now have a screen that displays troubleshooting information instead of a white screen. We still do not have a root cause for this issue. However, some devices that were encountering friction were able to log in yesterday with no trouble. As I was able to log in with every emulator I tried without any issues, this is beginning to seem like it is a device+localized issue rather than a more widespread one. Today I resume testing for the email policy story and plan to deploy it tomorrow -- finally. :D I also will get that CPU cooler in as well which I mentioned yesterday, wanting to have that done before the big change. #azure #blazor #csharp #dotnet #buildinpublic #buildinginpublic

#StarbeamOne #sb1 #DailyDeveloper #Startup #Status A bit of a down day yesterday. Half of my time was spent chasing the iOS/iPhone login issues, which still persist and the root cause is evasive, and the other half was calming down from it. 😞 I was able to finally set up a @LambdaTesting account for $9/mo (after discount) to try out all sorts of combinations of iOS/Mac/Safari and all of them worked. I do have to say, Lambda is such a great service. I highly recommend it if you need to do any sort of cross-platform testing, especially if you are bootstrapping and on a budget. As I mentioned, I am 100% $MSFT so purchasing anything $AAPL goes against my blood. For me, it's incredibly preferred (and cost-effective) to spend that $9-10 and test these devices and be done with it once confirming issues. Cancelling the subscription is super easy w/ no hassle so a good experience all around. We still have numerous accounts that attempt to sign into Twitter on their iOS devices and get weird errors. We seem to work with other providers like Google, so maybe it's a Twitter-app thing. 🤔 We'll track it down more and see what's happening. Hopefully. 🤞😅 Once/if we track down the root causes I will update the login workflow views to display troubleshooting steps to help assist with authentication. Outside of this, that really took my cycles. Having a priority-1 issue like this takes all my focus and it was difficult to settle into anything else. I had pushed several commits into staging and had to revert all of them because production already works as expected and verified with testing above as stated. I got the email story deployed again and will start to further test this. Before I deploy to production, one of the things I want to do is get a water-based CPU cooler on my rig. My room is consistently 75-77F degrees and has been since enabling Game Boost on my AMD. Before this, it was 73F. I can watch the temp of my room tick up as my CPU is heavily utilized and it's a total drag. As there is a chance my rig will never restart after installing this thing I want to be sure I do it before posting a major feature upgrade and not after. 😘 #azure #blazor #csharp #dotnet #buildinpublic #buildinginpublic

#StarbeamOne #sb1 #DailyDeveloper #Startup #Status iPhone/iOS login issues persist and will be the focus for today. I was unable to get an iPad from a family member so now the next step is to get an On-Demand Pass from @lambdatesting who I successfully used last year for another iOS issue. This product was perfect for me. Basically, I paid $10 and I got two hours of testing on an iOS device. Perfection. However, now I cannot seem to find where this is on their purchase page despite it being listed in their FAQ as an option. I sent an email for a support request and it's been two days now and I am still unclear how to acquire it. If this is not clear/resolved by the time I get underway this morning I will do what I did last year and get one of the higher priced items and request a refund later after done testing. This is my focus for the day. It's a frustrating one as all the attempts/tries at fixing this issue have not yet seemed to have worked. For any #AspNetCore peeps out there, the issue is a "Correlation Failed" error for finding the correlation cookie on sign-in for iOS/iPhone devices. As best as I can tell it's a SameSite issue but none of the fixes I have seen online address it. Open to any suggestions if you have them. Hopefully, we'll get some luck here soon today. 🤔 #azure #blazor #csharp #dotnet #buildinpublic #buildinginpublic

#StarbeamOne #sb1 #DailyDeveloper #Startup #Status Had kind of a sucky day yesterday after expecting a bit of smooth sailing. We've been having a bit of a wrinkle with Twitter logins for a while now, and I have been thinking it's due to our recent update to OauthV2. I haven't been able to piece it together recently because I lost UserAgent strings on our diagnostics due to how they are collected via the Serilog package we use. UserAgent is back and it's pretty obvious we have a sign-in issue with iPhone/iOS devices, resulting in "Correlation Failed" errors. My research yesterday has me believing this is due to SameSite cookie issues, but none of the guidance I tried worked. 😭 So today instead of the email policy story wrapup I am going to figure out why iPhone/iPad users cannot log in. Part of the challenge until this point is that I do not own these devices (I'm true $MSFT through and through) so testing has been challenging. I have relied on members such as @WillowGatePub and @flokdex to provide some serious patience and trial and error (thank you again both for your time + energy 🙏). Luckily, my brother has an old iPad that he managed to locate so I will be using this, and this will be the focus for the day to see if we can fix this today. I get a report of every error that occurs on the site and I cannot tell you how nerve-wracking it is to see someone try to authenticate but cannot. We had someone yesterday from North Carolina try a dozen times on both Twitter and Reddit with zero luck. If you see this, help is on the way. Unfortunately, this means the schedule has definitely slid and it looks like now my perfect plan of having v1 done by Feb is sliding a bit now. But hey, yesterday I also realized that Midjourney has been in Beta since I have known it (over a year now), so there's that. Onto the next fire. #azure #blazor #csharp #dotnet #buildinpublic #buildinginpublic

#StarbeamOne #sb1 #DailyDeveloper #Startup #Status Let's see if I can do this one without tripping all over myself this time. 😅 Yesterday I got all the little tasks done and fixed that performance issue in the proofing workflow. All fixes were committed and deployed to the testing environment where the new email address policy story is ready to test. 🤞 If you are a @StarbeamOne member, feel free to test it out in our testing environment here: testing.starbeam.one This is a testing environment with all the latest code and a separate database from production. Please feel free to comment below or DM me directly with any issues you encounter. If you need an email address, consider getting one from @burner_emails Today I will update the documentation, and further test this story. I've used a few accounts now and everything seems to work correctly. With a little luck, I will get this deployed tomorrow. 🤞 This has taken way longer than I anticipated. 😭 I suppose I shouldn't be so surprised as it does deal with identity/security so lots of considerations are to be had. It will be nice to get this out there and move onto the next feature. Small victories: My Google Help Community ordeal is over. Turns out there was an indicator on my profile that it indeed had been suspended due to a violation of community guidelines. Which ones? 🤷‍♂️ But there was an Appeal button and it took less than 12 hours to get me back online. 😌 #azure #blazor #csharp #dotnet #buildinpublic #buildinginpublic

#StarbeamOne #sb1 #DailyDeveloper #Startup #Status "Lots of little things" continued yesterday, but they were less of a lot of little things. So a "little of little things." 🤔 Small bugs but also one big one in actually migrating existing emails which I am looking into first thing today. Basically, we have a performance problem with our proofing workflow that is taking up a bunch of time. I will Hopefully, today is the day where I get everything out to staging ready to deploy to production. Tomorrow should be the day when this happens. I am attaching a preview for all existing users for what you will see when the prompt to supply your email address occurs. Notice the Get Help button in case something doesn't work or you need support. 👍 #azure #blazor #csharp #dotnet #buildinpublic #buildinginpublic

#StarbeamOne #sb1 #DailyDeveloper #Startup #Status Lots of little things happened yesterday while getting out the push for the email address policy story. Namely, I kept finding bugs with things that were not that. 😅 I noticed that we were no longer getting User-Agent strings in diagnostics and it was due to a new version of Serilog.Enrichers.ClientInfo which changed how to do this. I got that deployed and now we have a key metric in our logging again. We also had our first user merge yesterday, and by all appearances seems successful. No errors and all the data that was on the previous user is now on the other. I really feel this is a feature that needs an entire division dedicated to it and it will be some time before I feel entirely confident in it. To test it, I make a copy of the production database, run the order, and verify it there, deleting the database afterward. If it works/looks good I pull the trigger on production. Feeling like there's a better way to do this. 🤔 Today I continue on with "all the little things" that emerged from yesterday and get that email address policy story pushed to staging, and then probably production tomorrow. 🤞 #azure #blazor #csharp #dotnet #buildinpublic #buildinginpublic