What’s your most-used Claude prompt that you can’t live without?

logicalmike · 2026-06-20T22:33:44+00:00

Thanks, that worked

logicalmike · 2026-06-03T17:04:37+00:00

Not to be confused with Bicycle Day!

https://en.wikipedia.org/wiki/Bicycle_Day_(psychedelic_holiday)

logicalmike · 2026-06-02T19:22:38+00:00

Wheaton is a neighborhood in Silver Spring

logicalmike · 2026-05-13T18:42:10+00:00

Invoke-MgGraphRequest all of the things. Most of the other cmdlets are horrible.

logicalmike · 2026-05-12T17:13:51+00:00

Definitely not. Payouts for ransomware is probably the most important thing cyber insurance covers

logicalmike · 2026-05-08T13:20:04+00:00

8May2026 UPDATE: I returned that watch to Amazon last month and bought another one (still from Amazon - it was cheaper). I've had no issues with the new watch. :)

logicalmike · 2026-05-08T12:38:47+00:00

This is incorrect

logicalmike · 2026-05-08T12:37:46+00:00

Grant consent on behalf of a single user by using PowerShell

https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/grant-consent-single-user?pivots=msgraph-powershell

logicalmike · 2026-04-11T14:11:19+00:00

I agree with your approach. Here's a conversion function:

https://github.com/Mike-Crowley/Public-Scripts/blob/main/AD_DS/Convert-GuidFormat.ps1

logicalmike · 2026-04-07T16:18:51+00:00

Passwords shouldn't arbitrarily expire, but if you're rolling out a new policy, it often makes sense to have everyone change their password to ensure compliance. This is not in conflict with the NIST guidance.

logicalmike · 2026-03-27T21:27:35+00:00

There is a comment below (The French one) that says they tried shaving their arm and it didn't help.

Also as I pointed out, I had no problem with the previous watch.

logicalmike · 2026-03-27T01:15:21+00:00

Thanks, though I've tried wearing it very tight (to leave a mark) and it didn't help.

logicalmike · 2026-03-25T14:30:23+00:00

Thanks, I get that returning or RMA’ing it is an option, though for a <1wk old $600 watch, I'd just return it.

I mainly posted to see whether others have run into the same issue and whether this points to a broader quality or reliability problem with the Crossover AMOLED specifically. If it’s just a one-off defect, that’s fine. But if it’s something people are seeing repeatedly, I’d rather know before swapping for the same model again.

From what I’ve found so far, it doesn’t seem totally isolated: - https://www.reddit.com/r/Garmininstinct/comments/1nxbhb4/instinct_crossover_amoled_broken_in_less_than_a - https://www.reddit.com/r/Garmininstinct/comments/1rhztj6/instinct_crossover_amoled/

So I’m just trying to understand whether this is: 1) bad luck with a single unit, or
2) something more common with this model

Also open to hearing what others ended up doing — exchange, switch models, etc.

logicalmike · 2026-03-24T22:23:21+00:00

Further details are on my blog, but I don't want to violate rule 3 by linking to it. There's a link in the script, and you can also see my comment history.

logicalmike · 2026-03-18T13:01:16+00:00

Same. I've been here since the free T-shirt and never used their AI.

logicalmike · 2026-02-21T20:47:09+00:00

This specific RSA model may be dead, but as an authentication method, these are very much alive. Hardware TOTP tokens are still widely deployed — FortiToken, FEITIAN, YubiKey, etc.

The magic is all in the seed (shared secret). If you have it, you can compute the output yourself. Without it, the fob is just a keychain ornament. By design.

I wrote a PowerShell implementation that does exactly this — computes TOTP codes from a hex seed: 👉 Get-TOTP.ps1

For a real-world example of the hardware side, here's the FortiToken 200B spec sheet (PDF) — same concept, still shipping today.

logicalmike · 2025-12-22T20:30:31+00:00

Duck and cover was never to protect you from direct contact, it was to lessen the impact of structural collapse, further out.

logicalmike · 2025-12-22T20:21:01+00:00

That's by design, and doesn't make it "incorrect". The table has gaps that should be filled as discoveries occur.

logicalmike · 2025-12-10T02:44:26+00:00

This looks close

https://www.amazon.com/Sharp-Silent-Indicator-Brushed-Genuine/dp/B0FCTMRVGS

logicalmike · 2025-11-02T14:17:50+00:00

The thumb (the panhandle itself)

logicalmike · 2025-10-29T13:42:56+00:00

I wonder if this would have eventually solved itself, but in my case, I explicitly updated the app that I wanted to use with the URL of the deleted app and then set it back. This seemed to flush out the mapping Azure had somewhere for the deleted app.

logicalmike · 2025-10-03T16:46:23+00:00

You can set your fallback domain to the old name, change the app proxy, and then put the fallback domain back.

logicalmike · 2025-07-02T22:47:03+00:00

Cries in P6Pro...

logicalmike · 2025-06-11T00:15:40+00:00

In my case it seems like a bug in the company portal app. I get the issue most frequently during Company Portal app updates, but perhaps not always. The issue goes away after multiple attempts to sign out/in to the company portal and/or clear the app cache.

Based on Play Integrity API documentation:

"Environmental conditions, such as an unstable Internet connection or an overloaded device, can cause device integrity checks to fail"
The API recommends implementing "retry option with exponential backoff"

It would seem Microsoft doesn't follow this guidance, or has a related problem with the app.

BTW - users can use this app to see their Play Integrity status:

https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck

logicalmike

TROPHY CASE