u/Major-Language8609

Ok so I know we've all been through the sugar alcohol horror stories. I learned the hard way with a bag of sugar free gummy bears from amazon that I don't need to elaborate on. But I've found a few sugar free snacks over the past few months that don't wreck my stomach and actually taste decent.

Lily's chocolate chips. I eat like a small handful straight from the bag for a chocolate fix. The salted caramel ones are really good.

Cheese crisps with everything bagel seasoning. Not sweet obviously but I count these as snacks.

Pecans. Simple, fatty, filling. A small handful keeps me going for hours.

Shameless gummies. Only gummy type thing I've tried that doesn't destroy my stomach within 30 minutes. I was skeptical but my gut handled them fine.

Sugar free jello. The classic. I make it in bulk on sundays.

The key for me is reading what type of sweetener is used. Maltitol is the one that ruins me every time. If I see that on the label I just put it back. Erythritol and allulose seem to be fine for my system but everyone's different obviously.

The form question is genuinely confusing and I can't find a straight answer anywhere. Reduced glutathione, liposomal, IV, precursors like NAC. The price range is enormous and the bioavailability claims vary wildly.

What the research suggests: standard oral glutathione has absorption issues because it gets broken down in digestion before it reaches circulation. Liposomal versions protect it through that process. NAC as a precursor lets the body produce its own glutathione which some evidence suggests is more effective than trying to deliver it directly.

For skin the mechanism is clear. Glutathione inhibits tyrosinase, the enzyme involved in melanin production. That's why it keeps coming up in hyperpigmentation conversations, the biology is actually there.

I currently get L-glutathione through mindbodyskin by clearstem as part of a broader hormonal acne formula. Not a standalone high dose glutathione supplement but I noticed the dark spot improvement after a few months on it, which I wasn't expecting going in. Wondering whether anyone has layered a dedicated glutathione supplement on top of something like this and whether the difference was noticeable.

Edit: No idea why was it removed, here's me trying again. Thanks

Our outbound motion had gotten pretty mechanical. High-volume sequences to ICP accounts, low reply rates, reps increasingly skeptical of list quality. I knew it needed a rethink but wasn't sure where to start.

Sat through a demo with tapistro and it focused on warm outreach automation and the first thing they did was pull accounts from our segment that had shown signal activity in the past 30 days. Not new accounts, accounts already in our CRM that we'd tagged as low priority or stopped outreach on.

Three of the first five had job changes in the buying committee. One had been on the pricing page twice. Another had G2 activity in our category from two contacts. We had none of that surfaced anywhere in our stack. Those weren't cold accounts. We just had no visibility into what they'd been doing.

Edit: No idea why was it removed, so here's me trying again!

Rolled out Rovo across our 1200-person org for IT helpdesk in January. The deck pitched 35-40% tier-1 deflection by month 4. We are at 18.

What we tried: rebuilt the Confluence KB with the Rovo template (helped marginally). Added agents for the top 6 ticket categories (categorization got better, deflection didn't move). Narrowed scope per agent and tuned search relevance. Opened a partner ticket, got referred to professional services which felt like a concession.

Stuff i think we got wrong:

• KB is written like documentation. real tickets are phrased like i cant get into the thing
• anything multi-step (group adds, conditional access) opens a ticket anyway
• slack handoff to a human is rough enough that users DM IT directly
• a chunk of what shows as deflection was stuff our scripted flows already handled

Anyone here actually hitting 30+ in a similar sized org? Curious what your config looks like, what categories you gave up on, and whether the slack experience is working or your users route around it.

Would rather know we're running it wrong than write a renewal rec to leadership.

I recently moved from a big university lab into a small biotech startup, and one thing I've noticed is how different chemical management looks outside of academia.

At the university we had pretty structured systems for everything—chemical inventories, SDS databases, waste procedures, storage rules, etc. It was all managed through EHS and you didn’t really think about it much because the process already existed.

At this startup it's more… informal. Most chemicals are tracked in a spreadsheet (when people remember to add them), and SDS are mostly saved in a shared drive. It works okay for now, but it does make things a bit harder when you're trying to check compatibility, track what we actually have on hand, or figure out disposal.

I’m curious how other small labs handle this. Do you usually just run a spreadsheet + shared folder setup, or do most companies eventually move to some kind of chemical management system once they hit a certain size?

Feels like one of those operational things nobody talks about until the lab starts scaling.

Done on-premises enterprise AI coding deployments at three different organizations. The gap between vendor documentation and operational reality is consistent enough to write up.

What vendors undersell is that the initial model selection and sizing is more consequential than they imply. The model that produces acceptable inference latency for 50 developers on your hardware may produce unacceptable latency for 200. Getting sizing right before committing to hardware is genuinely difficult and vendor estimates are optimistic. Context engine configuration is also more work than "connect it to your repos" on complex enterprise codebases.

What IT teams overestimate is the ongoing operational overhead. Once the deployment is stable it's much lower than most internal teams expect. It's infrastructure maintenance. The tools designed for enterprise AI coding deployments have admin interfaces that don't require deep AI expertise to operate. The things that go wrong are things IT teams already know how to handle.

The organizations that struggle with on-premises AI coding are the ones that either chose hardware before understanding real sizing requirements or tried to do it without someone who's done a deployment before owning the initial configuration.

Had a drawer full of lip products. Glosses that were too sticky, lipsticks that dried my lips out, tinted balms that disappeared in twenty minutes. Kept buying more trying to find the one that actually worked the way I wanted.

Someone in my friend group wouldn't stop talking about ogee's tinted lip oil and I finally caved. The texture genuinely surprised me, much closer to a gloss than an oil, actual color payoff, and comfortable enough that I stopped thinking about reapplying

The clean formula was something I noticed after the fact. No synthetic fragrance, nothing I'd usually flag on an ingredient list. But that wasn't what kept it in rotation, it just works better than most of the conventional ones I'd cycled through before it.

One product, used daily, that I haven't felt the need to replace or supplement. That's the whole point of this sub and it took longer than it should have to get here.

Had a drawer full of lip products. Glosses that were too sticky, lipsticks that dried my lips out, tinted balms that disappeared in twenty minutes. Kept buying more trying to find the one that actually worked the way I wanted.

Someone in my friend group wouldn't stop talking about ogee's tinted lip oil and I finally caved. The texture genuinely surprised me, much closer to a gloss than an oil, actual color payoff, and comfortable enough that I stopped thinking about reapplying

The clean formula was something I noticed after the fact. No synthetic fragrance, nothing I'd usually flag on an ingredient list. But that wasn't what kept it in rotation, it just works better than most of the conventional ones I'd cycled through before it.

One product, used daily, that I haven't felt the need to replace or supplement. That's the whole point of this sub and it took longer than it should have to get here.

1200 person org and our quarterly access reviews have become a real problem. Every quarter security drops a 9,800 row Excel on us, we email it to 140 managers, and we spend the next 6 weeks chasing responses.

Last cycle ended with us escalating 200 stale rows to VPs at week 6 just to close. The cycle before that, same thing. Im pretty sure the bottleneck is the medium, an Excel email is a guaranteed way to lose a managers attention.

Were considering routing it through our slack-side AI helpdesk (we run risotto for our IT request flow already) so each row becomes a slack approval message with context pre-filled. Trial we ran on a 200-row subset closed in 4 days vs the usual 4 weeks for that subset.

The thing im worried about is data quality on the pre-fill. Our provisioning records have drifted in places and a wrong pre-fill is worse than no pre-fill (a manager who approves bad context is worse than a manager who didnt respond).

Anyone tried this approach at scale and what did you do about provisioning data quality before turning it on?

Was running calls and emails out of hubspot on a list marketing had approved based on ICP fit. No visibility into why any of these contacts were in the CRM, no signal, no intent context, just a name, a title, and a sequence to run. Marketing was happy because the ICP criteria looked right on paper. I was frustrated because nothing was converting and I had no idea which accounts were actually in market.

Our VP of sales had seen what proper gtm tooling could do in terms of scalability and results and got us onto tapistro. I was skeptical but two weeks in we had the system set up and I could suddenly see signals on contacts that were already sitting in our CRM. Which ones had recent activity worth acting on, which were cold, which had structural changes happening at the account level that made them worth calling right now.

Marketing stays happy because the ICP list is still the ICP list. I now have an actual handle on which contacts in that list are worth prioritizing. My time shifted away from blasting cold emails toward nurture and targeted calls on accounts where something is actually happening. The difference in how conversations go when you know why you're calling versus just that you should is significant.

How safe is doing p2p transactions these days? I will have around 20 to 30 USDT every week on Binance and I need to withdraw via p2p.

What do you guys recommend, bank transfer, eSewa or Khalti? It wont be a huge amount, maybe max $50 per week. I might be overthinking but just want to be safe.

Is it true that if I choose an agent with high rating and high completion rate then the risk is almost none? From what I read most issues happen when someone sends scammed or stolen money and the victim files a complaint, which leads to account freeze.

I’m looking to get a pretty large vinyl banner made for an event (something that’ll be hung outdoors, probably on a fence or building), needs to be vinyl specifically.

What are the best stores in Chicago that can do it high quality but for a fair price, delivery is preferable as well but I can pick it up if I have to.

Any recs or spots to avoid would be great, thanks.

Real question for the IAM folks. We are running access reviews on a 2 week cadence and they keep stretching to 3-4 weeks because the request queue is just enormous. About 1100 employees, Okta in front of basically everything, plus a separate IGA tool for the periodic certification stuff.

Okta itself handles the auth fine. The problem is the request side. Someone wants access to a tool, they file a ticket through helpdesk or DM their manager. Manager forwards to IT, IT approves, IT enters the assignment in Okta or in the downstream app, employee waits a week.

We have tried Workato to automate the routing pieces and it works for the access patterns we already had templated. The problem is most of our actual access requests are slightly weird, one-offs, edge cases, contractor flavor of normal employee, etc. The templates we built cover maybe 40% of volume.

What are people doing for the 60% that doesnt fit the templates? Are you just throwing more bodies at it, or has anyone gotten an AI layer to actually triage and approve the standard slices automatically while flagging the edge cases? Genuinely interested in the workflow more than the tool name.

Two things California hospital credentialing actually checks for ACLS: AHA issuance and documented in-person skills completion, that's it. Everything else on the cert is noise.

Fully online ACLS doesn't appear in the AHA training center registry and gets flagged regardless of what the certificate looks like. This applies at initial credentialing, privilege renewal, and when onboarding at a new practice. The registry check is real and credentialing coordinators at larger California systems run it in real time.

How to get it done: complete the AHA ACLS HeartCode online module at your own pace, which covers the cognitive content, then book the in-person skills check at an AHA authorized center. Safety training seminars runs ACLS certification across Northern California including Bay Area, Sacramento, and Central Valley locations with daily availability, and the credential issued is the AHA ACLS Provider card that California hospital credentialing requires.

One thing worth confirming before you book: some California hospital systems run shorter internal ACLS renewal cycles than the standard AHA 2 year period. Check with your credentialing contact before assuming the standard timeline applies.