u/Zealousideal-Owl1129

We just shipped a Navamsa (D9) calculator, and instead of a "find your soulmate" pitch, here's the honest idea behind it.

What the Navamsa actually is. It's the 9th divisional chart. You take each 30-degree sign and slice it into nine parts of 3 degrees 20 minutes, and each slice maps to a sign, so every planet gets a second "navamsa" sign on top of its main Rashi (D1) sign. Vedic astrology leans on the D9 mainly for two things: marriage and the spouse, and the underlying strength of each planet. The maxim worth remembering: the D9 refines the D1, it does not override it.

The thing most D9 tools never tell you. The Navamsa Lagna is brutally sensitive to birth time. Your D1 Lagna changes about every 2 hours; your Navamsa Lagna changes roughly every 13-14 minutes. So if your birth time is even a little fuzzy, your entire D9 house framework can be sitting in the wrong sign, and the reading is built on sand. Our tool computes how many minutes your birth time is from the nearest Navamsa Lagna boundary, so you know up front how much to trust the result. We haven't seen another calculator that does this.

One honesty bit: people treat "vargottama" (a planet in the same sign in D1 and D9) as rare and special. By the math it's about 1 in 9 placements per planet. We flag your vargottama planets and tell you that base rate, so you don't over-read it.

What it gives you: your Navamsa Lagna with the birth-time-confidence check, a per-planet D1-vs-D9 table, vargottama detection, and North + South Indian charts. Lahiri sidereal, the same engine as our Kundli tool. It's all cultural/informational, no remedies, no fear funnels.

Free. No nonsense: https://desiutils.in/astrology/navamsa-calculator

If you try it, cross-check a navamsa sign or two against a chart you already trust and tell us if anything looks off. Feedback welcome.

Wanted to make sure the weekday assignments I used in a sunrise-based Rahu Kaal calculator matched the dominant convention. Cross-checked four reference sources before locking the constants. Sharing in case useful.

The canonical Drik assignments (day length divided into 8 equal periods, indexed from sunrise to sunset):

Rahu Kaal: Sun:8 Mon:2 Tue:7 Wed:5 Thu:6 Fri:4 Sat:3

Gulika Kaal: Sun:7 Mon:6 Tue:5 Wed:4 Thu:3 Fri:2 Sat:1

Yamaganda: Sun:5 Mon:4 Tue:3 Wed:2 Thu:1 Fri:7 Sat:6

Reference sources I checked:

- Drik Panchang Saturday panchang (the canonical reference for this site's convention)

- AstroSage Rahu Kaal article + sample-day output

- mPanchang Rahu Kaal article

- AstroVed Rahu Kaal explanation

All four match on the 8-period-per-day Drik convention. The interpretation of "period 1" varies slightly between sources (some count from sunrise, some explicitly from local solar noon offset) but the cumulative window placement comes out identical when sunrise is correctly computed.

Engine notes: sunrise / sunset via Meeus / NOAA-style algorithm (50' refraction). This is intentionally INDEPENDENT of the Kundli ephemeris (Lahiri ayanamsa, VSOP87) - Rahu Kaal does not need lunar / planetary position calculations, so coupling it to the Kundli engine would be unnecessary. For India (UTC+5:30) and most east-of-UTC zones, you have to pass the observer's local Y/M/D directly to the julian calendar - converting to UTC first floors to the previous local date in astronomia's Sunrise constructor. (Caught this in pre-commit when Saturday's weekday assignment was getting paired with Friday's sun. Off-by-one date bug, the timing was close enough that the symptoms hid for a while.)

Shipped at https://desiutils.in/astrology/rahu-kaal with a "Major Indian Cities Today" SSR table for the curious. All browser-side. Open to any pushback on the weekday convention - I am aware some traditions vary on Yamaganda Friday assignment and there are alternative Karnataka / Tamil Nadu placements floating around.

Spent the last couple of days building a small set of focused Vedic astrology calculators and ran into a handful of numbers that are mildly surprising once you sit with the math. Sharing the ones that changed how I think about the standard online tools, in case any of this is useful to others.

1. Roughly 7 in 8 charts get flagged Manglik under the simplified rule

The simplified Mangal Dosha screen checks whether Mars sits in houses 1, 2, 4, 7, 8, or 12 from any of three reference points (Lagna, Moon, Venus). For any single reference point, Mars falls in an afflicting house with probability 6/12 = 1/2. Under the rule that any one reference afflicting suffices to flag the chart, the probability of NOT being flagged is (6/12)^3 = 1/8. So the model predicts about 87.5% of random charts flag.

Most matrimonial calculators surface the Manglik verdict without ever mentioning this. Users see "you are Manglik" and assume it's an exceptional finding. It's the base rate. Cancellation rules (Mars in own sign / exaltation, Jupiter or Venus aspect, mutual Manglik between partners) are what actually carry information; the raw flag almost doesn't.

I shipped a Mangal Dosha calculator that leads with the raw reference-point count (N of 3) instead of the binary verdict, and surfaces the base-rate honestly in the TL;DR and FAQ. Multilingual aliases (Mangal Dosha / Manglik / Kuja Dosha / Chevvai Dosham / Mangal Dosh) covered. Age-28 cancellation belief is kept separately from the four classical rules. https://desiutils.in/astrology/mangal-dosha

2. About 44% of random birth dates are Moon-transition days

The Moon transitions between sidereal signs roughly every 2.25 days, so the share of birth dates where the Moon crosses a sign boundary within the local 24-hour window is about 1/2.25 ≈ 44%. About 4 out of 9 people, give or take. On those days, "noon defaults" silently report ONE Rashi when in reality both signs touch the day.

For the Rashi calculator I bisect local 00:00 to 23:59 in the birthplace timezone to find the exact transition timestamp, then show BOTH possible Rashis with the local transition time when a boundary is detected. "I don't know my birth time" toggle uses 12:00 noon local birthplace, never silently IST. https://desiutils.in/astrology/rashi-calculator

3. ~0.3 degrees of Moon position error = ~33 minutes of nakshatra-boundary ambiguity

Engine accuracy ~0.3 deg vs Swiss Ephemeris (we use Meeus VSOP87 + Lahiri ayanamsa via the astronomia library). Moon mean motion ~0.549 deg/hour. So 0.3 deg translates to ~33 minutes of birth-time uncertainty for nakshatra-boundary determination — which directly affects starting Mahadasha lord in Vimshottari Dasha.

The Vimshottari calculator I shipped surfaces a nakshatra-boundary warning when the natal Moon is within 0.3 deg of an edge, naming BOTH candidate starting lords and the ~33 min ambiguity window. It also distinguishes the canonical 120-year reference cycle from the user's actual personalized timeline (the first Mahadasha truncates to the remaining balance of the birth nakshatra, so most personalized timelines are slightly less than 120y from birth). All 81 Antardashas rendered, distant periods folded past current-age + 50. https://desiutils.in/astrology/vimshottari-dasha

4. The "Madhya is most intense" framing of Sade Sati is chart-dependent in reality

AstroSage and AstroCamp both note that the second-charan peak or the chart-specific influences determine the actual most-intense phase. The flat "Madhya is most intense" claim that travels around matrimonial sites doesn't survive contact with classical sources. I phrase it as "traditionally often considered the most intense" with the chart-dependent qualifier visible.

Also: most online Sade Sati calculators model the cycle as one contiguous interval (start to end). This lies near retrograde sign re-entries — Saturn briefly leaves the 12th-from-Moon and retrogrades back, or briefly enters the 2nd-from-Moon and retrogrades back. A segment-based cycle model with currentPhase derived from current-Saturn-sign-relative-to-natal-Moon is robust under retrograde. https://desiutils.in/astrology/sade-sati

5. Drik canonical Rahu Kaal weekday assignments are not universally followed

The canonical weekday assignments per Drik tradition: Rahu = [Sun:8, Mon:2, Tue:7, Wed:5, Thu:6, Fri:4, Sat:3]. Gulika = [Sun:7, Mon:6, Tue:5, Wed:4, Thu:3, Fri:2, Sat:1]. Yamaganda = [Sun:5, Mon:4, Tue:3, Wed:2, Thu:1, Fri:7, Sat:6]. I cross-checked AstroSage, mPanchang, AstroVed, and Drik before locking these in the engine.

Sunrise / sunset for the user's actual city via Meeus / NOAA-style algorithm (separate from Kundli ephemeris — no Lahiri dependence). https://desiutils.in/astrology/rahu-kaal

Sources I leaned on: Brihat Parashara Hora Shastra (Santhanam translation), N.C. Lahiri's Indian Astronomical Ephemeris for sidereal Lahiri ayanamsa, Jean Meeus 1998 Astronomical Algorithms (VSOP87 lunar / planetary theory), B.V. Raman's Hindu Predictive Astrology, NASA JPL Horizons as a cross-validation reference. Whole-sign houses throughout.

Engine accuracy ~0.3 deg vs Swiss Ephemeris from 1900 onward.

Happy to take feedback on the framing, the multilingual aliases (Tamil / Telugu / Kannada spellings especially), or any of the specific numbers above.

Just shipped: a free, interactive Telugu Varnamala (అక్షరమాల) chart.

How many letters does Telugu have? 52, 56, or 60 - all three are "correct," depending on what's being counted. Instead of silently picking one, this page explains all three (the modern 16 + 36, the traditional count, and the script-wide summary) with sources.

What's inside:

- 🔊 Tap any letter to hear it (uses your device's Telugu voice)

- 🔤 16 achulu + 36 hallulu with example words

- 🧩 Full గుణింతాలు (guninthalu) tables for క గ చ త ప - the combination tables, rendered cleanly (couldn't find these anywhere else online)

- ✅ Yogavahalu, numerals, and a one-tap print for home or class

👉 desiutils.in/tools/telugu-varnamala

Native speakers - two asks: do the example words feel natural, and does the pronunciation sound right on your phone? And genuinely curious: which count do YOU treat as "the" answer, 52 or 56?

Got CC'd on one too many "gentle reminder" chains and built this on a weekend.

Paste any corporate email, get a passive-aggression score (0-100) and the plain-English translation of the toxic phrases.

A few it catches:

- "Per my last email" - I already told you this, please read the thread

- "Gentle reminder" - Deadline is staring at everyone, this isn't gentle anymore

- "Let's take this offline" - Stop replying-all, this thread is now a public wrestling match

- "With all due respect" - Respect has left the room, HR formatting remains

- "Looping in HR/skip-level" - Adding witnesses to this courtroom

- "Do the needful" - Solve this without making me specify every step

- "As discussed" - You agreed to this somewhere, I'm bringing receipts

Reply-all and EOD/ASAP each bump the score by 8. Top tier is "HR Incident in Progress",that's when you forward the thread to your therapist.

link to checkout the tool -

https://desiutils.in/tools/corporate-email-translator

Couldn't sleep after Tuesday so this happened. You type any name, date, scoreline, or phrase and it generates a proof that it equals 7.

A few clean ones:

mahi → 4 letters + 2 vowels + 1 word = 7

chepauk → 7 letters flat

07/07/1981 → day = 7

It labels each proof as clean, stretch, or nuclear depending on how much it had to bend. Mostly stays clean for cricket inputs which feels about right.

We ride for 8 in 2027.

Something most Indians don't realise: the BMI thresholds on global apps don't apply to us. Indian medical bodies use stricter cutoffs because we develop diabetes and heart disease at significantly lower body weights than European populations.

"Indian cutoffs (2009 consensus, still widely used):"

- Normal: 18.5 - 22.9

- Overweight: 23 - 24.9

- Obese: 25+

"Global (WHO standard):"

- Normal: 18.5 - 24.9

- Overweight: 25 - 29.9

- Obese: 30+

The research behind it: a 2004 WHO Expert Consultation (Lancet 2004; 363:157-163) found that Asian populations develop type 2 diabetes, cardiovascular disease and metabolic syndrome at lower BMIs than Europeans. India then adopted even stricter cutoffs based on Indian-specific evidence (Misra et al., JAPI 2009).

The scale of the gap is striking. A 2021 Lancet Diabetes & Endocrinology study found that South Asians hit the same age-adjusted diabetes risk at **BMI 23.9** that White populations hit at **BMI 30**. That's a 6-point gap. Same risk, very different number on the scale.

The biological reason: South Asians have what's called the "thin-fat phenotype" - we accumulate visceral (belly) fat at smaller body sizes. You can look slim and still have high metabolic risk.

This is also why "waist circumference matters as much as BMI for Indians". IDF South Asian thresholds:

- Men: above 90 cm = elevated risk

- Women: above 80 cm = elevated risk

If your BMI is normal but waist is above these, the BMI is hiding actual risk.

Update worth knowing: in January 2025, an Indian Obesity Commission led by Dr Anoop Misra published a revised two-stage framework (Diabetes & Metabolic Syndrome journal). The new model still uses BMI >23 as the trigger but combines it with waist circumference and comorbidities to distinguish "Stage 1 obesity" (BMI >23, no organ impact) from "Stage 2 obesity" (BMI >23 + abdominal fat + comorbidity like diabetes/hypertension). Most calculators still use the simpler 2009 cutoffs.

Why this matters at scale: India has one of the world's largest diabetes populations. Part of that is genetics, but a non-trivial part is that we under-diagnose risk by applying global standards. Someone at BMI 24 gets called "healthy" by a Western app and never gets early intervention.

Built a calculator that uses Indian standards by default: https://desiutils.in/tools/bmi-calculator

Full writeup with research citations: https://desiutils.in/blog/bmi-guide-indian-standards

Not medical advice. But if you've been tracking BMI on a global app, worth re-checking against the right threshold.

Got tired of reading 10 articles saying different things about EPFO 3.0. Some say ATM withdrawal is live, some say coming soon, some bundle the ₹5 lakh auto claim with EPFO 3.0 like it's a brand new change.

Sat down with the official PIB release from the 238th CBT meeting (13 Oct 2025) and tried to figure out what is actually approved vs what is still in rollout. Made this infographic for my own clarity and sharing in case it helps someone else.

A few things that surprised me while researching:

The ₹5 lakh auto-settlement limit is not new. It's been live since 24 June 2025, with EPFO targeting settlement in about 72 hours. Most articles bundle it with EPFO 3.0 but it predates the framework.

UPI-linked withdrawal is not live yet for most members. Still in phased rollout, with no operational public launch announced.

ATM-style PF access has been discussed under the EPFO 3.0 framework, but I couldn't find a public operational launch date anywhere. If you've seen articles claiming it's already live, I'd genuinely like to see the source.

The 238th CBT meeting simplified 13 withdrawal categories into 3: Essential Needs, Housing Needs, and Special Circumstances. This feels like one of the biggest practical changes and barely gets covered.

Minimum service period for partial withdrawals was reduced from 5 years to 12 months. Younger employees benefit a lot here.

The "75 percent withdrawal" thing also gets oversimplified everywhere. CBT approved more withdrawal flexibility, subject to a new minimum balance rule and category conditions. So it is not a flat 75 percent cap across every scenario. The actual rule depends on what you are withdrawing for and which category it falls under.

Sources I cross-checked: PIB release dated 13 Oct 2025 and the EPFO press release on auto-settlement dated 24 June 2025, both on epfindia.gov.in.

If anyone has actually used the new auto-settlement system or has firsthand info on UPI rollout from their own claim experience, would love to hear how it's going. Official communication is still sparse and most news articles seem to repeat each other.

Happy to be corrected on any detail. Most of you probably know specific corners of this better than I do.