After being summoned like a Saudi diplomat to appear before the crown prince of Saudi Arabia, Saad Hariri returned to Beirut to pack and say his goodbyes, then returned to Riyad, picked up the phone and called the Lebanese president to tell him that he is quitting. The bizarre process led President Michel Aoun to wait to see if Hariri return and inform him in person, and through the proper protocol, about the reasons for quitting before accepting his resignation. That might be a very long wait.
Clearly, the Hariri’s decision to resign is not his own. After all, all the reasons he mentioned are not new developments: Lebanon is under the circumstances and conditions as when he agreed to the deal that brought him and Aoun to the offices of the presidency and the prime ministry.
Among the reasons, real and fictitious, that forced him to resign, Hariri claims that he could be assassinated, that Iran in meddling in Lebanese affairs, and that Hezbollah is a destabilizing force because of its use of force against Syrians and Lebanese citizens. Before he agreed to the deal that made him prime minister, Hezbollah was doing whatever it is doing now, Iran was doing whatever it is doing now, and his fear for his life then was as much a risk then as it is now. Clearly there is something else that has changed: Saudi Arabia’s plan for the region.
The summon is proof of that fact and it is also proof that Saudi Arabia is meddling in Lebanese affairs. Those who know Lebanese politics, know that many regional and world powers meddle in Lebanese affairs, so there is nothing new here.
These developments are indicative of Saudi plans to escalate its efforts to further destabilize Lebanon, and country, whose stability is crucial to region given its geography, demography, and history.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
A video-sharing platform for users to upload, view, and share videos across various genres and topics.
Registers a unique ID on mobile devices to enable tracking based on geographical GPS location.
1 day
VISITOR_INFO1_LIVE
Tries to estimate the users' bandwidth on pages with integrated YouTube videos. Also used for marketing
179 days
PREF
This cookie stores your preferences and other information, in particular preferred language, how many search results you wish to be shown on your page, and whether or not you wish to have Google’s SafeSearch filter turned on.
10 years from set/ update
YSC
Registers a unique ID to keep statistics of what videos from YouTube the user has seen.
Session
DEVICE_INFO
Used to detect if the visitor has accepted the marketing category in the cookie banner. This cookie is necessary for GDPR-compliance of the website.
179 days
LOGIN_INFO
This cookie is used to play YouTube videos embedded on the website.