u/TKB21

I've recently been struggling with emulsifying my food grade essential oils. Recently I experimented with arabic gum and lemon essential oil, which was decent but ended up with a thick end-product with a slightly dulled flavor profile.

The syrups and eventually drinks I'm incorporating them into are non-alcoholic. Despite this, I've seen the key ingredient for emulsifying is Everclear. I understand that the amount is small in dosage but do I still have anything to worry about as far as the drinks being labeled and marketed as truly non-alcoholic

Every now and then on streaming while watching FOL, I get re-reminded how much I love the guy and look up his limo service. As of this post his website is still up but looks like it hasn't been updated in decades. I can't imagine it not getting a decent amount of traffic due to syndication. I also couldn't find any Google listings for the business itself. Does anyone know if it's still around and what Big Rick is up to? He's probably my favorite right hand man with Big John being second.

Was thinking of giving the series a complete re-watch but with my antennas up this time around to pick up anything I missed during my first viewing. With that I was wondering if there were any loose ends or plot points that went nowhere but had signs of promise?

Was the submitted footage real? It seemed candid enough to the point where it didn't feel scripted. They had that one episode with Jimmy Jam & Terry Lewis where it was entirely dedicated to the audition tapes. It also makes me wonder what the end goal was (outside of the plot of course). During the original airing of this show, was there an email or physical address where artists submitted this footage for exposure? Though I didn't necessarily mind the auditions, every time I watch any of these episodes they seemed kid of odd/intriguing in regards to how long they let them run and how many of them were.

Cool….they addressed the usage bug but what concerns me is how the model degradation got swept under the rug with a reset. Resets in theory are “okay” in a sense but we find ourselves right back at near zero before the traditional weekly reset because the models fall over themselves with shitty code with multiple revisions needed to produce shippable product. They view us as social experiments.

With upgrading machines and software, I've gradually been moved off of the one and only music player I've loved to now what's Apple Music. Support for local files seems to be 2nd class which makes life miserable. I'm not going as far as using a VM so my second thought has been to create an app that mirrors what we know and love (i.e. iTunes) but for the modern Mac OS. One of the biggest things I could think of off the bat was the ability to be able to passively and wirelessly sync music without having to do it manually through Finder. Anything else you guys can think of that would be worth improving upon?

Token efficiency and model regression. Fix these two and I honestly could care less about any other feature for the foreseeable future. It's really that simple yet continues to be an issue a year+ into Codex's existence. The regressions appear to be the worst of the two. It makes me wonder if Codex overall needs a refactor or rewrite. I say this only because I don't think there's ever been a time where there's been more than a month of stability.

In all seriousness was there anything Jason did that could actually have been considered "honorable". It could've been something in his way that he handled in order to get to his main target or just in general. The first and only thing that comes to mind for me was saving Rennie from getting raped by the thugs in Part VIII. He didn't have to do it necessarily but chose to kill them over all 3.

FWIW: I'm not in the camp (no pun intended) thinking he's above killing kids. I believe he was intending to kill the kids in Part VI but got sidetracked. There's even more evidence pointing to him not discriminating by age as Tommy Jarvis in Part IV was always an intended target.

Some of my app's features include things like needing the camera for bill/receipt OCR. Despite the innocence of the requirement, users immediately see it as almost a threat towards privacy and deny permission. To reiterate, all the app is doing is using your camera to scan a bill and detect the amounts on them. The CTA before entering the camera view as well as the view is as transparent as you can get. The number one reason for the feature's failure according to my metrics is this permission denial. Do you all have any methods on lowering that level of friction so users aren't so immediately put off on such a feature?

I've transitioned from being a domain specific specialist and more of a stronger fundamentalist. If that's being deemed a "vibe coder", so be it. For the first time in my career I've finally been able to get out of my own way by putting the technical onus on the model to achieve the bigger picture. More specifically, I can bounce ideas off of the model and get really good design feedback quickly while picking up methodologies I would've never learned before. Even while side-caring, the model might insert a documentation or testing style that I pick up during its own rubber ducking. Instead of racking my brain on figuring out how to benchmark performance bottlenecks, I just describe what I'm experience in the client and it does the rest in creating an optimal solution. The whole thing is empowering.

Frustrates the hell out of me that App Store Connect doesn't give you this out the box and there's no historical tracking of ratings (not rating+review combo). I was wondering if you all have a script it place that you schedule to pull from the API so you're able to measure number of the number star ratings within a given time period.

One thing that still has me bound to either working directly on my machine and/or using Google Remote Desktop to said machine is I work heavily with user-facing sites and apps that require some sort of client to view visual changes and functionality. If you are using the Desktop app or the new /remote feature, how are you all dealing with scenarios like this?

I've gotten more into the habit of using my data to make design and feature decisions. Once the features are implemented though is where I have the hardest time figuring out the best way to communicate that "something's there" or fixed/addressed. I've been thinking of multiple methods: alerts, annotations, or action sheets on startup, behavior based triggers, badges, etc. What have you found to be the best way to do this?