@barsiisaaabdii1: #ethopiantiktok🇪🇹🇪🇹🇪🇹 #oromotiktok❤️💚❤️ethiopiantiktok #ethiopian_tik_tok

barsiisaa abdii🇪🇹💻📞📟✅

Open In TikTok:

Region: SA

Wednesday 23 September 2026 08:24:35 GMT

6670

199

13

59

Music

Download

No Watermark .mp4 (1.54MB) No Watermark(HD) .mp4 (1.47MB) Watermark .mp4 (0MB) Music .mp3

Comments

Mohammed :

akkata visa fi Siyoosi ofii laalan himi mee?

2026-09-23 21:03:29

0

caalaa💪🥷 :

Internet tola jiraa naf himi

2026-09-23 08:34:58

0

misraa :

2026-09-23 18:00:40

0

shuguxi arsi itaya :

aka gadi bufanuti hijadhu

2026-09-23 11:14:30

0

Wozir ♤♧ :

Ochii jarana

2026-10-14 21:34:43

0

𝐌𝐮̄'𝐢𝐒́𝐇𝐚̂ 𝐋𝐢𝐕🇪🇹5𝐆 :

kan siwosiihoo

2026-09-23 08:29:35

0

Ramadan Nadaa :

🥰🥰🥰

2026-09-25 17:04:45

0

boru shawaa🤙🤍👱 :

🥰🥰🥰🥰

2026-09-23 17:42:18

0

Baredu Madirid🤍🖤🤍🫂 :

[Heartwarming][Heartwarming][Heartwarming]

2026-09-23 08:47:53

0

Fiqir mucaa Heraroo :

❤️❤️❤️

2026-09-25 04:59:22

0

Sabit nuradi Jimmaa nada✅ :

🥰🥰🥰

2026-10-03 11:54:30

0

To see more videos from user @barsiisaaabdii1, please go to the Tikwm homepage.

Other Videos

azoblash xizmati😂❤️ #foryou #fyp #trending #viral (#komediya #hayot #uzvideo

azoblash xizmati😂❤️ #foryou #fyp #trending #viral (#komediya #hayot #uzvideo

I am sorry! okay..? তুমি চাইলে আমাকে ঘৃণা করতে পারো, এমনিতেই সবাই করে! আর সত্যি বলতে কি আমি নিজেও নিজেকে অনেক দিন ধরে ঘৃণা করি..!😅❤️‍🩹 #sadvideo #banglacaption #caption #emotionalcaption #foryou @TikTok Bangladesh @TikTok @For You

I am sorry! okay..? তুমি চাইলে আমাকে ঘৃণা করতে পারো, এমনিতেই সবাই করে! আর সত্যি বলতে কি আমি নিজেও নিজেকে অনেক দিন ধরে ঘৃণা করি..!😅❤️‍🩹 #sadvideo #banglacaption #caption #emotionalcaption #foryou @TikTok Bangladesh @TikTok @For You

Top khoản đầu tư xứng đáng: Đi bác sĩ da liễu uy tín. Trvia đi dc 1 tháng da có ấy lên 🫰🏻#actidem #nuoctaytrang

Top khoản đầu tư xứng đáng: Đi bác sĩ da liễu uy tín. Trvia đi dc 1 tháng da có ấy lên 🫰🏻#actidem #nuoctaytrang

Okay, NOW It’s Time To Leave GitHub Microsoft's own code editor helped DDoS Microsoft's own GitHub. A latent retry bug in VS Code amplified traffic about ten times over during the August 17 outage, and half of all raw file and archive downloads failed with it. One saturated network layer took down Issues, pull requests, the API, Actions, Copilot and SSO logins for most of a workday, and it killed Homebrew installs and Terraform runs for people who do not even have a GitHub account. This video is the mechanism behind that: how one datacenter's load balancers cascaded into a global outage, why GitHub keeps breaking as commit volume runs toward 14 billion a year on a half finished Azure migration, and why leaving GitHub stays structurally hard even though your code moves in two commands. Zig, Ghostty and Guix already tried it. Here is what it actually cost them. CHAPTERS 0:00 VS Code helped DDoS GitHub 0:53 Anatomy of the outage: one saturated layer, every service 1:44 raw.githubusercontent.com is the internet's installer 2:19 14 billion commits and an unfinished Azure migration 3:08 Git stays up. GitHub Actions keeps dying. 3:46 The four layers of leaving GitHub 5:08 Zig, Ghostty and Guix: what migration really cost 6:23 Cursor's Origin and the exit developers refused 7:11 Why nobody actually migrates 7:50 Multihoming: the fix that takes one line of Git config THE RECEIPTS ~10x traffic amplification from a VS Code retry bug, pushing one internal service from 9,000 to 100,000 requests a second Almost 8 hours of degradation, with roughly half of raw and archive downloads failing 71% of GitHub Actions workflow runs hitting infrastructure failures at the worst point of the August 6 incident 99.99% uptime for Git operations against 99.33% for Actions over 90 days 275 million commits a week, on pace for 14 billion this year, with a fifth of all accounts under six months old $170,000+ a year in GitHub Sponsors income that Zig had to rebuild donor by donor 180 million developers who already have an account, SSH keys and the pull request flow in muscle memory WHY LEAVING GITHUB IS SO HARD Git is decentralized, so the code itself moves cleanly: git clone --mirror and git push --mirror copy every commit, branch and tag to Codeberg, Forgejo, Gitea, GitLab or a self hosted forge. The lock-in lives in the four layers above the code. Your CI is provider specific, so GitHub Actions secrets, runner images, branch protections, webhooks and OIDC cloud trust get rebuilt by hand. Your release URLs break, because every curl installer, package manager and Stack Overflow answer still resolves to github.com and no competitor can redirect those links for you. Your contributors never move at all, since a stranger fixing a typo costs one click on GitHub and a whole new identity anywhere else. The cost of leaving GitHub scales with the number of external edges touching your repo, not with the size of your code. WHAT THIS VIDEO COVERS The August 17 GitHub outage root cause, from load balancer saturation to the retry storm Why raw.githubusercontent.com is a hidden dependency in Homebrew, Go modules and Terraform GitHub's growth problem: AI coding agents, commit volume and the Azure migration Why GitHub Actions fails far more often than plain Git, and what that costs self hosted runners The four layers of vendor lock-in: code, CI, URLs, contributors Real migrations: Zig to Codeberg, Ghostty's incremental exit, one year of Guix on Codeberg Cursor's Origin launch and why developers refused an alternative on the day GitHub was down Multihoming, push mirrors, dependency audits and a CI escape hatch you can set up this week

Okay, NOW It’s Time To Leave GitHub Microsoft's own code editor helped DDoS Microsoft's own GitHub. A latent retry bug in VS Code amplified traffic about ten times over during the August 17 outage, and half of all raw file and archive downloads failed with it. One saturated network layer took down Issues, pull requests, the API, Actions, Copilot and SSO logins for most of a workday, and it killed Homebrew installs and Terraform runs for people who do not even have a GitHub account. This video is the mechanism behind that: how one datacenter's load balancers cascaded into a global outage, why GitHub keeps breaking as commit volume runs toward 14 billion a year on a half finished Azure migration, and why leaving GitHub stays structurally hard even though your code moves in two commands. Zig, Ghostty and Guix already tried it. Here is what it actually cost them. CHAPTERS 0:00 VS Code helped DDoS GitHub 0:53 Anatomy of the outage: one saturated layer, every service 1:44 raw.githubusercontent.com is the internet's installer 2:19 14 billion commits and an unfinished Azure migration 3:08 Git stays up. GitHub Actions keeps dying. 3:46 The four layers of leaving GitHub 5:08 Zig, Ghostty and Guix: what migration really cost 6:23 Cursor's Origin and the exit developers refused 7:11 Why nobody actually migrates 7:50 Multihoming: the fix that takes one line of Git config THE RECEIPTS ~10x traffic amplification from a VS Code retry bug, pushing one internal service from 9,000 to 100,000 requests a second Almost 8 hours of degradation, with roughly half of raw and archive downloads failing 71% of GitHub Actions workflow runs hitting infrastructure failures at the worst point of the August 6 incident 99.99% uptime for Git operations against 99.33% for Actions over 90 days 275 million commits a week, on pace for 14 billion this year, with a fifth of all accounts under six months old $170,000+ a year in GitHub Sponsors income that Zig had to rebuild donor by donor 180 million developers who already have an account, SSH keys and the pull request flow in muscle memory WHY LEAVING GITHUB IS SO HARD Git is decentralized, so the code itself moves cleanly: git clone --mirror and git push --mirror copy every commit, branch and tag to Codeberg, Forgejo, Gitea, GitLab or a self hosted forge. The lock-in lives in the four layers above the code. Your CI is provider specific, so GitHub Actions secrets, runner images, branch protections, webhooks and OIDC cloud trust get rebuilt by hand. Your release URLs break, because every curl installer, package manager and Stack Overflow answer still resolves to github.com and no competitor can redirect those links for you. Your contributors never move at all, since a stranger fixing a typo costs one click on GitHub and a whole new identity anywhere else. The cost of leaving GitHub scales with the number of external edges touching your repo, not with the size of your code. WHAT THIS VIDEO COVERS The August 17 GitHub outage root cause, from load balancer saturation to the retry storm Why raw.githubusercontent.com is a hidden dependency in Homebrew, Go modules and Terraform GitHub's growth problem: AI coding agents, commit volume and the Azure migration Why GitHub Actions fails far more often than plain Git, and what that costs self hosted runners The four layers of vendor lock-in: code, CI, URLs, contributors Real migrations: Zig to Codeberg, Ghostty's incremental exit, one year of Guix on Codeberg Cursor's Origin launch and why developers refused an alternative on the day GitHub was down Multihoming, push mirrors, dependency audits and a CI escape hatch you can set up this week

#viral #fyp #goviral

#viral #fyp #goviral

#تابعوني_رح_نزل_شي_جديد #ستورياتي١

#تابعوني_رح_نزل_شي_جديد #ستورياتي١

About

Robot
API

Legal

Privacy Policy