Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a2450af04d47b1a9

Jump to content

Talk:Mount Shani

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 4 months ago by ~2026-13777-87 in topic Wrong picture V2

Wrong picture V2

[edit]

Sorry, I do not know the correct way to flag stuff on Wikipedia. Tried to comment by not deleting the old one. However, the new picture still seems off and the description sure is. The peaks shown are Q'uro / Gora Kuru and (Mt.) Shino. The highest peak obstructed by the cloud is definitely Q'uro / Gora Kuru. This can be easily verified by looking at a map. By the angle the photo was made, Mt. Shani should show up behind the ridge connecting Q'uro / Gora Kuru and (Mt.) Shino. Due to the low altitude of the photo spot, the ridge obstructs the view to Mt. Shani. Quickly going on Google Maps photo sphere shows this exactly. Photo sphere on the way up to Kazbek Here you can see Mt. Shani popping up behind the ridge, because the photo was made at a higher elevation. Preceding unsigned comment added by ~2026-13777-87 (talk) 18:15, 3 March 2026 (UTC)Reply

Wrong picture

[edit]

I believe the pictures attributed in Mt. Shani in both the English and the Georgian article are wrong. The mountain named Mt. Shani is actually Mt. Khuro, whereas Mt. Shani is further to the right of the falsely-attributed and - more importantly - further back, as there is another valley between the Khuro and the Shani massifs. Mapping material does not support the attribution given in wikipedia. WaltDisno (talk) 09:04, 10 March 2024 (UTC)Reply