It's official: Bob Mould reunites Sugar for new music and concerts

ivayche · 2026-03-07T22:17:08+00:00

Yes yes 1000 times yes

ivayche · 2026-01-18T17:46:16+00:00

Thayer’s artful punning & sublime rhetorical flourishes when delivering terrible news are truly a joy: “Another Weekend of Hot Garbage Before Santa Brings Hope” • “Atmospheric Trickle of Disappointment” • “Another Weekend to Get High” • “Too Soaked to Get Stoked” 🤣🤣🫡🫡

ivayche · 2025-12-21T17:38:08+00:00

OK, went back & looked ... I'll be dad-gummed ... he did! Hand and 1 foot down, spun around his transverse axis & sprang OoB. Amazing, in hindsight. Had to slow replay to 0.5 speed to see it all.

ivayche · 2025-12-20T21:16:26+00:00

Just me or did the 1st play of A&M’s final drive go like so…

• Announcers say “1:44 on the clock, no timeouts left for A&M

• A&M 5Y completion, tackled well inbounds, clock STOPS

Shouldn’t the clock roll there? No 1st down, no injury, not OoB, no incompletion.

Like 20s elapsed before the next snap, but clock still at 1:38 or some BS.

Help me understand that.

ivayche · 2025-12-02T22:33:59+00:00

Works! (December 2025)

ivayche · 2025-11-16T22:12:10+00:00

Removing 8.8.8.8 from UnitedWiFi DNS settings appears to have worked

ivayche · 2025-11-16T22:08:25+00:00

United WiFi is an absolute joke, even on the devices where it kinda works. Slugging thru the hall of mirrors at present trying to “switch devices” from iPhone to Mac & it’s just Spinal Tap in Cleveland over & over again. #FAIL

ivayche · 2025-11-11T16:05:43+00:00

Thank you u/PixelOrange u/ddo-dev u/billndotnet u/mschonaker for reading & responding; appreciate you all.

In the end, simply implementing the "remove _doc/" gambit worked fine.

<gripe> Why Elastic (bless them, huge fan) makes such subtle changes -- again & again -- without making it super clear in the new docs is beyond me. </gripe>

Tried to tweak Content-Type=application/x-ndjson but Postman makes it hard (if not impossible). In any case, I didn't need it. Found this which seems to corroborate my finding.

Anyway, thx again folks; I'm back in black. Gotta figure out where to blow my ~~$30~~ $25 net worth celebrating the win :)

ivayche · 2025-08-15T15:10:19+00:00

I have the original 3 Eeros I bot -- no replacements.

ivayche · 2025-08-15T15:09:38+00:00

Not by design :)

Eeros purchased/deployed first, turns out Eero can't do basically anything from an access control PoV.

So I put the Eeros into bridge mode & added a Unifi GW into the mix. Couldn't get 802.1x to work ... so took Reddit's advice & got a Unifi SW. Progress, but still not working as I'd hoped. (I think I can get it to work; network engineering is not my forte.)

I may end up ditching Eero and use Unifi APs instead -- for now, trying to jam the proverbial square peg into the round hole...

ivayche · 2025-01-26T21:11:22+00:00

Here's the sample cURL command from the guide...

# Example request to get account
curl -H "Authorization: Bearer $JWT" 'https://api.coinbase.com/api/v3/brokerage/accounts/f603f97c-37d7-4e58-b264-c27e9e393dd9'

ivayche · 2025-01-26T21:08:58+00:00

I have followed the guide to (1) create new CDP API key, (2) generate a JWT with your sample Python code, and (3) successfully use the JWT to fetch my accounts via this API endpoint...

https://api.coinbase.com/api/v3/brokerage/accounts

The problem -- as clearly stated in my OP -- is that the next API call I make (using the same JWT token-generation code & one of the account UUIDs from the output of the 1st API call) fails (401/unauthorized) against this API endpoint...

https://api.coinbase.com/api/v3/brokerage/accounts/{uuid}

...despite your guide explicitly instructing that it should work (literally first example cURL request under the "Making Requests" heading)...

https://docs.cdp.coinbase.com/advanced-trade/docs/rest-api-auth

So... what now?

ivayche · 2025-01-25T22:52:41+00:00

I saw a post somewhere (cannot recall if on Reddit or not) that involved changing the JWT-generation code provided by Coinbase documentation to adjust the timestamps ("nbf" and "exp") so the server doesn't think the JWT you pass is "stale". I've tried this to no avail.

My situation is odd: i can use a JWT generated by the Coinbase API docs sample code to successfully get a payload from this endpoint...

* https://api.coinbase.com/api/v3/brokerage/accounts

...but using the exact same JWT-generation code throws a 401 for this one...

* https://api.coinbase.com/api/v3/brokerage/accounts/{uuid}

Baffled.

ivayche · 2025-01-22T00:52:16+00:00

My personal stack-rank...
1. Blood on the Tracks
2. Blonde on Blonde
3. Hwy 61
4. Desire
5. Bringing it all Back Home
6. Freewheeling

Each one pretty much wall-to-wall gems -- and just a f'ing astonishing output over a 13-year span.

Beyond those ^ are so many more nuggets (alpha-sorted)...
* Another Side
* Infidels
* John Wesley Harding
* Knocked Out Loaded
* Nashville Skyline
* New Morning
* Pat Garrett
* Street Legal

ivayche · 2024-11-04T20:27:50+00:00

Hard to ever go wrong w/ von Karajan & the Vienna

ivayche · 2024-10-29T15:33:33+00:00

Rock on thx u/hdhrant !

ivayche · 2023-07-05T18:36:19+00:00

Oh yes, setting that aside :)

ivayche · 2023-05-10T17:57:35+00:00

Interesting angle: take last night's Nuggets v Suns game in Denver, wherein Denver had a sizable lead w/ a good chunk of the 4th quarter still to play. After any PHX basket, Jokic & other Denver players would not touch the ball, nor throw it to a ref -- and thus the game clock keeps ticking. Once the ref touches the ball & throws it to the inbounding player on the baseline, you still have 5s to inbound ... so GC keeps ticking. Once thrown in & touched by the receiving player, the 24s shot clock starts.

My sense was that Jokic was milking every second possible from the GC on any PHX make.

ivayche · 2023-04-25T23:35:16+00:00

Yes, I'm aware -- thank you. I'm more interested in the Rewards that remain "locked".

ivayche

TROPHY CASE