{"id":6058,"date":"2019-06-19T14:41:09","date_gmt":"2019-06-19T11:41:09","guid":{"rendered":"https:\/\/www.kaspersky.com.tr\/blog\/?p=6058"},"modified":"2020-05-13T19:31:27","modified_gmt":"2020-05-13T16:31:27","slug":"facebook-10-fails","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com.tr\/blog\/facebook-10-fails\/6058\/","title":{"rendered":"En epik 10 Facebook facias\u0131"},"content":{"rendered":"<p>Ge\u00e7ti\u011fimiz May\u0131s ay\u0131nda Mark Zuckerberg 35. do\u011fum g\u00fcn\u00fcn\u00fc kutlad\u0131. Kendisini tebrik ediyoruz! Ne var ki Zuckerberg, bu noktaya sessiz sedas\u0131z gelmedi. Tam tersine, man\u015fetler Facebook\u2019la ilgili skandallarla dolu oldu\u011fu s\u0131rada kendisini kullan\u0131c\u0131lar\u0131n gizli verilerini yanl\u0131\u015f y\u00f6netmekten ki\u015fisel olarak sorumlu tutabilmenin yollar\u0131n\u0131 arayan bir federal soru\u015fturma <a href=\"https:\/\/www.washingtonpost.com\/technology\/2019\/04\/19\/federal-investigation-facebook-could-hold-mark-zuckerberg-accountable-privacy-sources-say\/?noredirect=on&amp;utm_term=.de4eb66b9e77\" target=\"_blank\" rel=\"noopener nofollow\">ge\u00e7irdi<\/a>. Bu yaz\u0131da veri suistimali de dahil Facebook\u2019un en \u00f6nemli 10 facias\u0131n\u0131 derledik.<\/p>\n<h2>1. Cambridge Analytica: Her \u015feyin ba\u015flang\u0131c\u0131<\/h2>\n<p>Her \u015fey, Cambridge Analytica skandal\u0131yla ba\u015flad\u0131. Facebook\u2019ta payla\u015ft\u0131\u011f\u0131m\u0131z verilerin ve g\u00f6r\u00fc\u015flerin, r\u0131zam\u0131z olmaks\u0131z\u0131n \u00fc\u00e7\u00fcnc\u00fc ki\u015filerce kullan\u0131labildi\u011fini ilk defa 2018\u2019in ba\u015flar\u0131nda kesin olarak \u00f6\u011frendik. Cambridge Analytica\u2019n\u0131n 50 milyon Facebook kullan\u0131c\u0131s\u0131na ait verileri toplamas\u0131 ve bu verileri siyasi reklamlar i\u00e7in kullanmas\u0131 d\u00fcnyay\u0131 sarst\u0131, fakat bu yaln\u0131zca ba\u015flang\u0131\u00e7t\u0131. Bu olaylar\u0131 yeniden incelemek isterseniz <a href=\"https:\/\/www.kaspersky.com.tr\/blog\/delete-facebook\/4813\/\" target=\"_blank\" rel=\"noopener\">bu yaz\u0131y\u0131 okuyabilirsiniz<\/a>.<\/p>\n<h2>2. Facebook tokenlar\u0131 \u00e7al\u0131nd\u0131<\/h2>\n<p>6 ay sonra, <a href=\"https:\/\/www.kaspersky.com.tr\/blog\/facebook-token-breach\/5287\/\" target=\"_blank\" rel=\"noopener\">Facebook bir ba\u015fka skandalla sars\u0131ld\u0131<\/a>: Korsanlar, Facebook\u2019taki \u00e7e\u015fitli zay\u0131f noktalar\u0131 kullanarak milyonlarca Facebook kullan\u0131c\u0131s\u0131n\u0131n eri\u015fim tokenlar\u0131n\u0131 (bunlar\u0131 insanlar\u0131n oturumda kalmas\u0131n\u0131 sa\u011flayan dijital anahtarlar olarak d\u00fc\u015f\u00fcnebiliriz) \u00e7ald\u0131.<\/p>\n<p>Toplamda 30 milyon kullan\u0131c\u0131n\u0131n tokenlar\u0131 \u00e7al\u0131nd\u0131. Su\u00e7lular, 15 milyonunun isimlerine ve ki\u015fisel verilerine eri\u015fti. 14 milyon vakada sald\u0131rganlar, daha detayl\u0131 bilgileri ve kullan\u0131c\u0131lar\u0131n Facebook aktivitelerini g\u00f6r\u00fcnt\u00fcleyebildi. Geri kalan 1 milyon kullan\u0131c\u0131n\u0131n verilerine ise ula\u015famad\u0131lar. Facebook kullan\u0131c\u0131lar\u0131, Facebook g\u00fcvenli\u011finin a\u015f\u0131lamaz olmad\u0131\u011f\u0131n\u0131 ve kendileri yanl\u0131\u015f bir \u015fey yapmasa bile hesaplar\u0131n\u0131n kitlesel halde \u00e7al\u0131nabilece\u011fini bu olayla \u00f6\u011frendi.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kis-trial-privacy\">\n<h2>3. Facebook ve Instagram \u015fifreleri if\u015fa oldu<\/h2>\n<p>30 milyon yetmezmi\u015f gibi, y\u00fcz milyonlarca Facebook ve Instagram kullan\u0131c\u0131s\u0131n\u0131 ilgilendiren ba\u015fka bir olay daha ger\u00e7ekle\u015fti. 2019\u2019un ba\u015flar\u0131nda Facebook, kullan\u0131c\u0131 verileri g\u00fcvenli\u011fiyle ilgili i\u00e7 s\u00fcre\u00e7lerinin idealden \u00e7ok uzak oldu\u011funu fark etmemizi sa\u011flad\u0131. \u015eirket, Facebook ve Instagram hesaplar\u0131na ait \u015fifrelerin bir k\u0131sm\u0131n\u0131 d\u00fcz metin halinde <a href=\"https:\/\/newsroom.fb.com\/news\/2019\/03\/keeping-passwords-secure\/\" target=\"_blank\" rel=\"noopener nofollow\">depolad\u0131\u011f\u0131n\u0131<\/a> kabul etti. Bu \u015fifrelerin yaln\u0131zca \u00e7al\u0131\u015fanlar taraf\u0131ndan g\u00f6r\u00fclebildi\u011fi ve kimsenin eri\u015fim iznini k\u00f6t\u00fcye kullanmad\u0131\u011f\u0131 konusunda \u0131srar ettiler.<\/p>\n<p>Bu noktada tam olarak ka\u00e7 ki\u015finin etkilendi\u011fine dair bir a\u00e7\u0131klama yap\u0131lmad\u0131. \u015eirket ilk ba\u015fta sorunun milyonlarca Facebook Lite kullan\u0131c\u0131s\u0131n\u0131, on milyonlarca normal Facebook kullan\u0131c\u0131s\u0131n\u0131 ve on binlerce Instagram kullan\u0131c\u0131s\u0131n\u0131 ilgilendirdi\u011fini s\u00f6yledi. Bir ay sonra ise bu a\u00e7\u0131klamaya d\u00fczeltme getirerek (art\u0131k yamanm\u0131\u015f olan) sorunun on binlerce de\u011fil, milyonlarca Instagram kullan\u0131c\u0131s\u0131n\u0131 etkiledi\u011fini a\u00e7\u0131klad\u0131.<\/p>\n<h2>4. Instagram \u015fifreleri tekrar if\u015fa oldu<\/h2>\n<p>Esas\u0131nda Instagram kullan\u0131c\u0131lar\u0131, \u015fifrelerinin s\u0131zm\u0131\u015f olabilece\u011fini ilk defa duymuyorlard\u0131. Birka\u00e7 ay \u00f6nce, Instagram\u2019daki \u201cVerilerinizi \u0130ndirin\u201d \u00f6zelli\u011finin baz\u0131 Instagram \u015fifrelerini <a href=\"https:\/\/www.theverge.com\/2018\/11\/17\/18100235\/instagram-security-bug-exposed-user-passwords-data-download-tool\" target=\"_blank\" rel=\"noopener nofollow\">yanl\u0131\u015fl\u0131kla if\u015fa edebilecek<\/a> (art\u0131k yamanm\u0131\u015f) bir g\u00fcvenlik kusuru bar\u0131nd\u0131rd\u0131\u011f\u0131 ke\u015ffedilmi\u015fti. Kullan\u0131c\u0131, \u00f6zelli\u011fi kullanmak i\u00e7in oturum a\u00e7ma bilgilerini girdi\u011finde \u015fifre, Web taray\u0131c\u0131lar\u0131ndaki URL\u2019e dahil ediliyor ve Facebook\u2019un sunucular\u0131nda yine d\u00fcz metin halinde saklan\u0131yordu.<\/p>\n<h2>5. Facebook, e-posta \u015fifrelerini isteyerek ki\u015filere eri\u015fti<\/h2>\n<p>Facebook, r\u0131zalar\u0131 olmaks\u0131z\u0131n 1,5 milyon kullan\u0131c\u0131n\u0131n e-posta ki\u015filerine eri\u015fti. Asl\u0131nda durum bundan biraz daha karma\u015f\u0131k. Hikaye \u015f\u00f6yle: Facebook, bir k\u0131s\u0131m kullan\u0131c\u0131dan e-posta hesaplar\u0131n\u0131n \u015fifresini vererek kimliklerini do\u011frulamas\u0131n\u0131 <a href=\"https:\/\/twitter.com\/originalesushi\/status\/1112496649891430401\" target=\"_blank\" rel=\"noopener nofollow\">istedi<\/a>. Haber duyuldu\u011funda pek \u00e7ok ki\u015fi bunun 1 Nisan \u015fakas\u0131 oldu\u011funu sand\u0131; \u0130nternette gezinmeyi bilen herkes i\u00e7in \u00fc\u00e7\u00fcnc\u00fc ki\u015filerin e-posta ileti\u015fimlerine eri\u015fmesine izin vermek hayal dahi edilemezdi. Ne yaz\u0131k ki bu bir \u015faka filan de\u011fildi. \u00dcstelik pek \u00e7ok ki\u015fi bu tuza\u011fa d\u00fc\u015ft\u00fc.<\/p>\n<p>Facebook, <a href=\"https:\/\/www.businessinsider.com\/facebook-uploaded-1-5-million-users-email-contacts-without-permission-2019-4\" target=\"_blank\" rel=\"noopener nofollow\">\u0131srarla<\/a> kullan\u0131c\u0131lar\u0131n e-posta i\u00e7eriklerine eri\u015fmedi\u011fini, yaln\u0131zca (istemeden) e-posta ki\u015filerine eri\u015fti\u011fini iddia etti. Toplamda 1,5 milyon kullan\u0131c\u0131n\u0131n adres defteri toplanm\u0131\u015ft\u0131. Fakat insanlar\u0131n ki\u015fi listelerinde y\u00fczlerce ismin olabilece\u011fi d\u00fc\u015f\u00fcn\u00fcld\u00fc\u011f\u00fcnde, ileti\u015fim bilgileri ele ge\u00e7irilen ki\u015fi say\u0131s\u0131 on milyonlar\u0131 bulabilir. \u015eirket, verileri reklam hedeflemeyi geli\u015ftirmek, Facebook\u2019un sosyal ba\u011flant\u0131 a\u011f\u0131n\u0131 in\u015fa etmek ve kullan\u0131c\u0131lara yeni arkada\u015flar \u00f6nermek i\u00e7in kulland\u0131\u011f\u0131n\u0131 s\u00f6yledi.<\/p>\n<h2>6. 2 a\u015famal\u0131 do\u011frulama, Facebook\u2019ta reklam verenler i\u00e7in bir ara\u00e7<\/h2>\n<p>Elbette hepimiz hesaplar\u0131m\u0131z\u0131 g\u00fcvende tutmak isteriz ve iki a\u015famal\u0131 do\u011frulama, bunu yapman\u0131n ideal yolu gibi g\u00f6r\u00fcn\u00fcr. Fakat burada bile potansiyel sorunlar ortaya \u00e7\u0131kabilir. \u00d6rne\u011fin, Facebook hesab\u0131n\u0131zda iki a\u015famal\u0131 do\u011frulamay\u0131 etkinle\u015ftirmek i\u00e7in verdi\u011finiz telefon numaras\u0131, ba\u015fka bir se\u00e7enek sunulmaks\u0131z\u0131n otomatik olarak profilinizle ili\u015fkilendirilir. Bunun sonucunda, bir hesab\u0131 olmasa bile herkes, bu telefon numaras\u0131yla <a href=\"https:\/\/techcrunch.com\/2019\/03\/03\/facebook-phone-number-look-up\/\" target=\"_blank\" rel=\"noopener nofollow\">profilinizi arayabilir<\/a>. \u00dcstelik: Facebook, numaran\u0131z\u0131 reklamlar\u0131n <a href=\"https:\/\/www.facebook.com\/notes\/facebook-security\/fixing-sms-notifications-for-those-using-two-factor-authentication\/10155124741945766\/\" target=\"_blank\" rel=\"noopener nofollow\">hedefine de alabilir<\/a>.<\/p>\n<h2>7. Reklam vericiler s\u00f6zkonusu oldu\u011funda ki\u015fileriniz asla g\u00fcvende de\u011fil<\/h2>\n<p>Yukar\u0131da de\u011findi\u011fimiz gibi, Facebook ve Instagram, reklam vericiler i\u00e7in Facebook\u2019ta bile olmayan ileti\u015fim bilgilerine eri\u015fim <a href=\"https:\/\/gizmodo.com\/facebook-is-giving-advertisers-access-to-your-shadow-co-1828476051\" target=\"_blank\" rel=\"noopener nofollow\">sa\u011fl\u0131yordu<\/a>! Di\u011fer bir deyi\u015fle, reklam vericiler yaln\u0131zca \u201cileti\u015fim ve temel bilgiler\u201d sayfam\u0131zda belirtti\u011fimiz e-posta adresleri ve telefon numaralar\u0131n\u0131 de\u011fil, ayn\u0131 zamanda ba\u015fka verileri de baz alarak bizi hedefliyordu (ve b\u00fcy\u00fck olas\u0131l\u0131kla hala da bu \u015fekilde hedefliyorlar).<\/p>\n<p>Bu verilerin i\u00e7inde (varsa) 2 a\u015famal\u0131 do\u011frulama i\u00e7in girdi\u011finiz telefon numaras\u0131 da olabilir, indirimler veya gizli \u00e7evrimi\u00e7i al\u0131\u015fveri\u015fler i\u00e7in verdi\u011finiz istenmeyen e-posta adresleri de\u2026 Ayr\u0131ca, ki\u015filerinizden biri, \u201carkada\u015f bulmak\u201d i\u00e7in kendi ki\u015filerini Facebook\u2019la payla\u015fmay\u0131 (\u201csenkronize etmeyi\u201d) tercih ederse ya da kendi adres defterlerini Facebook\u2019a y\u00fcklerse ve listelerinde size ait bir telefon numaras\u0131 varsa, bu bilgiyi siz Facebook\u2019a hi\u00e7 girmemi\u015f olsan\u0131z bile reklam vericiler bu telefon numaras\u0131n\u0131 kullanarak reklam i\u00e7in sizi hedefleyebilir.<\/p>\n<h2>8. Reklam vericilerle daha da fazla Facebook verisi payla\u015f\u0131ld\u0131<\/h2>\n<p>S\u0131zd\u0131r\u0131lan i\u00e7 belgeler, Facebook\u2019un ortakl\u0131k kurdu\u011fu \u015firketlere \u00fcst\u00fcnl\u00fck sa\u011flayabilmek i\u00e7in kullan\u0131c\u0131 verilerini g\u00f6zetledi\u011fini ortaya <a href=\"https:\/\/www.nbcnews.com\/tech\/social-media\/mark-zuckerberg-leveraged-facebook-user-data-fight-rivals-help-friends-n994706\" target=\"_blank\" rel=\"noopener nofollow\">koydu<\/a>. \u00d6rne\u011fin, Facebook reklamlar\u0131na ciddi miktarda yat\u0131r\u0131m yapan Amazon.com, arkada\u015flar\u0131 arac\u0131l\u0131\u011f\u0131yla kullan\u0131c\u0131lar\u0131n isimlerini ve e-posta adreslerini <a href=\"https:\/\/www.nytimes.com\/2018\/12\/18\/technology\/facebook-privacy.html\" target=\"_blank\" rel=\"noopener nofollow\">elde edebiliyordu<\/a> (t\u0131pk\u0131 Sony, Microsoft ve daha bir\u00e7ok \u015firket gibi).<\/p>\n<p>Microsoft\u2019un Bing arama motoru, bizim (veya onlar\u0131n) r\u0131zas\u0131 olmaks\u0131z\u0131n b\u00fct\u00fcn Facebook arkada\u015flar\u0131m\u0131z\u0131n ismini g\u00f6rebiliyordu. Netflix\u2019e, Spotify\u2019a ve Kanada Kraliyet Bankas\u0131\u2019na \u00f6zel mesajlar\u0131m\u0131z\u0131 okuma, yazma ve silmenin yan\u0131 s\u0131ra bir mesaj dizisindeki t\u00fcm kat\u0131l\u0131mc\u0131lar\u0131 g\u00f6rebilme ayr\u0131cal\u0131\u011f\u0131 sa\u011flanm\u0131\u015ft\u0131. Apple cihazlar, hesap ayarlar\u0131n\u0131 t\u00fcm payla\u015f\u0131m\u0131 engelleyecek \u015fekilde de\u011fi\u015ftirmi\u015f ki\u015filerin bile ki\u015filerine ve takvim girdilerine eri\u015febiliyordu.<\/p>\n<p><strong> \u0130lgili \u015firketler, eri\u015ftikleri verileri asla suistimal etmediklerini beyan etti; hatta bir k\u0131sm\u0131, b\u00f6yle \u201cgeni\u015fletilmi\u015f\u201d haklara sahip olduklar\u0131n\u0131 bile bilmediklerini s\u00f6yledi.<\/strong><\/p>\n<h2>9. Facebook Pazar Yeri, sat\u0131c\u0131lar\u0131n konumunu s\u0131zd\u0131rd\u0131<\/h2>\n<p>Facebook\u2019un dijital pazar yerindeki (<a href=\"https:\/\/www.databreachtoday.com\/facebook-marketplace-flaw-revealed-sellers-exact-location-a-12402\" target=\"_blank\" rel=\"noopener nofollow\">art\u0131k yamanm\u0131\u015f olan<\/a>) bir kusur, sat\u0131c\u0131lar\u0131n ve dolay\u0131s\u0131yla \u00fcr\u00fcnlerinin konumunu (en ince enlem ve boylam koordinatlar\u0131na kadar) if\u015fa ediyordu. Konumu g\u00f6rmek i\u00e7in Facebook\u2019a giri\u015f yapmak bile gerekmemesi, baz\u0131 ara\u015ft\u0131rmac\u0131lar\u0131n hizmete \u201ch\u0131rs\u0131zlar i\u00e7in al\u0131\u015fveri\u015f listesi\u201d demesine sebep oldu. \u00d6zellikle pahal\u0131 bisikletler satanlar i\u00e7in durum daha da endi\u015fe vericiydi, \u00e7\u00fcnk\u00fc bunlar su\u00e7lular i\u00e7in lezzetli lokmalard\u0131 ve Pazar Yeri, sat\u0131c\u0131lar\u0131n konumunu if\u015fa ederek bu bisikletleri adeta bedava da\u011f\u0131t\u0131yordu.<\/p>\n<h2>10. Facebook verileri if\u015fa edildi; hem de \u00fc\u00e7\u00fcnc\u00fc ki\u015filer taraf\u0131ndan!<\/h2>\n<p>Facebook kullan\u0131c\u0131lar\u0131n\u0131n bilgilerini i\u00e7eren iki veri taban\u0131, a\u00e7\u0131k a\u011fda, verileri herkesin eri\u015febilece\u011fi ve indirebilece\u011fi \u015fekilde d\u00fcz metin olarak depolar halde <a href=\"https:\/\/techcrunch.com\/2019\/04\/03\/facebook-records-exposed-server\/\" target=\"_blank\" rel=\"noopener nofollow\">bulundu<\/a>. Bir grup veri, uzun s\u00fcre \u00f6nce kullan\u0131m d\u0131\u015f\u0131 olan \u201cHavuzda\u201d adl\u0131 bir oyun uygulamas\u0131ndan geliyordu. 540 milyondan fazla kay\u0131t i\u00e7eren ikinci grup ise Latin Amerika\u2019da faaliyet g\u00f6steren Meksikal\u0131 medya \u015firketi Cultura Colectiva\u2019ya aitti. \u0130f\u015fa olan her iki veri taban\u0131 da kullan\u0131c\u0131lar\u0131n isimlerinin ve e-posta adreslerinin, arkada\u015f listelerinin, be\u011fenilerinin ve yorumlar\u0131n\u0131n yan\u0131 s\u0131ra tercihleri ve ilgi alanlar\u0131n\u0131 analiz etmek i\u00e7in kullan\u0131labilecek her t\u00fcrl\u00fc ayr\u0131nt\u0131y\u0131 i\u00e7eriyordu.<\/p>\n<p>Bilgiler \u00f6zellikle hassas olmad\u0131\u011f\u0131 ve Facebook \u00e7al\u0131\u015fanlar\u0131n\u0131n if\u015fayla bir ilgisi olmad\u0131\u011f\u0131 halde bu durum, yine de (tekrar) Facebook\u2019un kullan\u0131c\u0131 verilerini \u00fc\u00e7\u00fcnc\u00fc ki\u015filerle nas\u0131l payla\u015ft\u0131\u011f\u0131na dair sorular\u0131 ve bu yaz\u0131y\u0131 ba\u015flatan Cambridge Analytica skandal\u0131n\u0131 ak\u0131llara getirdi.<\/p>\n<p>Bu yaz\u0131y\u0131 okuduktan sonra Facebook\u2019un sa\u00e7mal\u0131klar\u0131ndan b\u0131kt\u0131\u011f\u0131n\u0131z\u0131 hissediyorsan\u0131z blogumuzda <a href=\"https:\/\/www.kaspersky.com.tr\/blog\/how-to-delete-facebook\/5821\/\" target=\"_blank\" rel=\"noopener\">Facebook hesab\u0131n\u0131z\u0131 nas\u0131l silece\u011finize dair bilgiler bulabilirsiniz<\/a>. Elbette karar tamamen size kalm\u0131\u015f.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"ksc\">\n","protected":false},"excerpt":{"rendered":"<p>Kullan\u0131c\u0131lar\u0131n\u0131n g\u00fcvenli\u011fini ve gizlili\u011fini tehdit eden 10 Facebook hatas\u0131<\/p>\n","protected":false},"author":2508,"featured_media":6059,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[994],"tags":[20,1944,500,1891],"class_list":{"0":"post-6058","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-privacy","8":"tag-facebook","9":"tag-facia","10":"tag-gizlilik","11":"tag-hata"},"hreflang":[{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/facebook-10-fails\/6058\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/facebook-10-fails\/15797\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/facebook-10-fails\/13325\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/facebook-10-fails\/17708\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/facebook-10-fails\/15853\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/facebook-10-fails\/14599\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/facebook-10-fails\/18475\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/facebook-10-fails\/17352\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/facebook-10-fails\/26980\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/facebook-10-fails\/11760\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/facebook-10-fails\/11856\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/facebook-10-fails\/10767\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/facebook-10-fails\/19284\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/facebook-10-fails\/23269\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/facebook-10-fails\/22633\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/facebook-10-fails\/22583\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com.tr\/blog\/tag\/facebook\/","name":"Facebook"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/posts\/6058","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/users\/2508"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/comments?post=6058"}],"version-history":[{"count":4,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/posts\/6058\/revisions"}],"predecessor-version":[{"id":8285,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/posts\/6058\/revisions\/8285"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/media\/6059"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=6058"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=6058"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=6058"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}