u/Tris_Memba

The RBI is highly likely to bump the repo rate by 25 basis points to 5.50% today. Honestly, with inflation hovering near 5% and oil sitting comfortably around $100, the market has already digested this hike. The actual volatility is going to come from the commentary.

If the Governor keeps it light and suggests this is just a one off pre eemptive move to steady the rupee, Nifty should see a decent relief rally as the uncertainty clears out. On the flip side, if they sound spooked about the weak monsoon or structural oil shocks and hint at a prolonged hiking cycle, expect rate-sensitives like Bank Nifty, autos, and realty to take a massive beating.

Are you guys buying the dip on defensives like IT and pharma, or just sitting on cash until the dust settles? Let me know your plays.

Hey everyone,

I ran into a weird issue with QRZ Logbook blind matching on a DMR contact and wanted to see if anyone knows the exact database logic behind it.

I had a DMR QSO where both of us logged the band as 70cm. All our other details (callsigns, mode, date/time) were correct. However, my entry showed a blue dot (unconfirmed).

Originally, my logged frequency was 438.800 MHz. I went into edit mode and simply pressed the 70cm band button. Pressing that button automatically changed the frequency field from 438.800 to 420.000 MHz on its own.

I did not change the callsign, date, or time. The very second I saved that automatic frequency change to 420.000, the blue dot immediately turned into a gold star (confirmed).

I've always read that the QRZ matching algorithm only cares about the broader "Band" field and completely ignores the granular numerical frequency field. If that's true, why did the system changing the frequency from 438.800 to 420.000 instantly trigger the match? Does QRZ store different hidden band strings based on what the band button generates?

Has anyone else noticed QRZ behaving this way? Thanks!

73