Življenje s psom

Kdaj prekiniti interakcijo med otrokom in psom?

Večinoma imajo otroci radi pse, za majhne otroke so psi nekakšne igračke. Zato je pomembno, da otroka, ki odrašča ob psu (pa tudi če ne) naučimo pravilnega odnosa do psa.

Sem in tja pretrese novica, da je kakšen pes popadel (največkrat domačega) otroka. Največ ugrizov povzročijo odraščajoči psi, stari od treh mesecev do enega leta, najpogostejše žrtve pa so domači otroci, stari okoli sedem let.

Če našemu psu še tako dobro zaupamo, je pomembno, da razumemo njegovo govorico. Z njo nam bo – še preden bo popadel – sporočil, če mu je v določeni situaciji, denimo v družbi otroka neprijetno. Če bi skrbniki razumeli pasjo govorico, bi psu velikokrat ponudili izhod, še preden pride do neljubega dogodka.

Zato v nadaljevanju nekaj primerov pasjega vedenja, ko je prav, da starši (ali skrbniki psa) prekinejo interakcijo med otrokom in psom:

  • Pes je postal tog in ima predirljiv pogled, s katerim otroka fiksira;
  • pes odmika glavo, ker se želi izogniti (trenutni) situaciji oz. preveč vsiljivemu otroku;
  • pes si oblizuje ustne, ”požira”, umika pogled – gre za očitne znake, da se ne počuti prijetno;
  • zelo nedvoumen opozorilni znak je renčanje, ki je zelo pomemben sestavni del pasjega komuniciranja; tega vedenja psu ne smemo prepovedovati, saj bi lahko v prihodnji podobni situaciji popadel brez opozorila.

Del prispevka avtorja Jožeta Vidica, dr. vet. med, objavljenega v reviji Moj pes

Center Nastavitev Zasebnosti

Obvezni piškotki

Shranijo uporabnikovo odločitev glede sprejemanja piškotkov.

gdpr[allowed_cookies], gdpr[consent_types]: beleži uporabniško odločitev glede sprejetja ali zavrnitev uporabe piškotkov. Veljavnost: 1 leto.

Socialna omrežja

Facebook vtičnik; za povečanje sodelovanja naših uporabnikov preko družbenih omrežij, analizo prodaje, segmentacijo uporabnikov in ponovno targetiranje uporabnikov

_fbp, datr, fr, locale, sb, wd
_fbp, datr, fr, locale, sb, wd

Analitika

Analitika nam omogoča, da merimo število uporabnikov.

_ga: merjenje obiskanosti s storitvijo Google Analytics. Veljavnost: 2 leti. _gat: piškotek ne hrani uporabniških podatkov, uporablja se za omejevanje pogostosti zadetkov pri merjenju obiskanosti strani s storitvijo Google Analytics. Veljavnost: 10 minut. _gid: naključno ustvarjeno unikatno število se uporablja za izračun podatkov o obisku našega spletnega mesta. s storitvijo Google Analytics. Veljavnost: 24 ur.

Analiza obiska

To function properly, Hotjar stores first-party cookies on your visitor's browser. Cookies are either set by the Hotjar script, or by visiting Hotjar's website. Displaying the correct content to your visitors without personally identifying anyone relies on Hotjar's cookies.

_hjClosedSurveyInvites Hotjar cookie. This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown. 365 days _hjDonePolls Hotjar cookie. This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in. 365 days _hjMinimizedPolls Hotjar cookie. This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site. 365 days _hjDoneTestersWidgets Hotjar cookie. This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in. 365 days _hjIncludedInSample Hotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels. 365 days _hjShownFeedbackMessage This cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show. 365 days _hjid Hotjar cookie. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. 365 days _hjRecordingLastActivity This should be found in sessionStorage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records). Session hjTLDTest When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed. Session _hjUserAttributesHash User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated. Session _hjCachedUserAttributes This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool. Session _hjLocalStorageTest This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted immediately after creating it so the expected storage time is under 100ms. N/A _hjptid This cookie is set for logged in users of Hotjar, who have Admin Team Member permissions. It is used during pricing experiments to show the Admin consistent pricing across the site. Session _hjAbsoluteSessionInProgress The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information. 30 minutes

error: Kopiranje teksta ni mogoče.