Holmsland Municipality

Until January 1, 2007 Holmsland was a municipality (Danish, kommune) in Ringkjøbing County on the west coast of the Jutland peninsula in west Denmark. The municipality covered an area of 95 km2 on a narrow strip of land, Holmsland Dunes (Holmsland Klit), which is connected to the mainland on the north and south, and bounded on the east by Ringkøbing Fjord and on the west by the North Sea. It had a total population of 5,285 (2005). Its last mayor was Ivar Enevoldsen. The main town and the site of its municipal council was the town of Hvide Sande ("White Sands").

Lock and bridge in Hvide Sande, Denmark.

The municipality was created in 1970 due to a kommunalreform ("Municipality Reform") that combined a number of existing parishes:

  • Gammelsogn Parish
  • Holmsland Klit Parish
  • Nysogn Parish

Holmsland municipality ceased to exist due to Kommunalreformen ("The Municipality Reform" of 2007). It was merged with existing Egvad, Ringkøbing, Skjern, and Videbæk municipalities to form the new Ringkøbing-Skjern municipality. This created a municipality with an area of 1,485 km2 and a total population of 57,818 (2005). The new municipality belong to Region Midtjylland ("Mid-Jutland Region"). The merger was a hot issue in Holmsland municipality, since Holmslund distinguished itself by having Denmark's lowest tax rate, and residents expected that this rate would increase on account of the merger. According to Dagbladet Børsen, Denmark's leading business paper, residents risked a loss on their properties of more than 250,000 DKr, and a yearly tax increase of 15,000 DKr on account of the merger .

The town of Hvide Sande

The town of Hvide Sande lies in the middle of the former municipality and is Denmark's 5th largest fishing harbour. It was established on either side of the canal that runs from the North Sea into Ringkøbing Fjord. The canal was dedicated in 1931.

gollark: A search query which returns lots of results is going to take longer than one which returns none, mostly, thus you have access to some data you shouldn't.
gollark: For example, send a request to `https://interweb.site/search-some-private-data?query=thing` using a form or `img` or `script` or whatever, and see how long it takes (using `onload`/`onerror` handlers and such).
gollark: The timing attacks thing: since you can send GET requests to domains you probably shouldn't be able to, and time how long they take, you can infer some data you shouldn't be able to from other domains.
gollark: It is not okay, it is bees.
gollark: Because you can access cross-domain scripts and images without explicit optin by the site they're from, guess what? TIMING ATTACKS, *and* you can check whether there's an image or not at some arbitrary URL because while CORS weirdness won't let your code read the *content* of an image you include with `<img>` unless the site it's from opts in, you can check the width/height and whether it loaded or not.

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.