Archive for the ‘CDN (Content Delivery Network)’ Category
Posted by jpluimers on 2026/09/28
Not using vim much, so every time I need it for more complex things than basic editing or leaving any vi based text editor (hello <Esc> :q!), I need a FAQ or cheat sheet.
I like this one the most as it has merged most if not all other cheat sheets in it: [Wayback/Archive] ikwyl6 vim cheat sheet.
The above page is the [Wayback/Archive] CDN for your source code | raw.githack.com hosted version of the HTML page in the repository [Wayback/Archive] GitHub – ikwyl6/vim-cheat-sheet-html: Collaboration of vim cheat sheets I’ve found and put them in a html file.
That means you can contribute to it with more vim features in case they become available.
By intent, the cheat sheet looks like [Wayback/Archive] Vim Cheat Sheet – vim.rtorr.com, but it omits the tips bits like:
Read the rest of this entry »
Posted in *nix, *nix-tools, CDN (Content Delivery Network), Cloud, Hosting, Infrastructure, Power User, vi/vim | Leave a Comment »
Posted by jpluimers on 2026/08/24
If I ever run into a Cloudflare hosted site, I should try fiddling with the site-specific /cdn-cgi/ endpoint that Cloudflare automagically adds: [Wayback/Archive] /cdn-cgi/ endpoint · Cloudflare Fundamentals docs
Via [Wayback/Archive] Dr. Christopher Kunz: “I didn’t know this and it migh…” – chaos.social
I didn’t know this and it might really be handy with debugging weird Cloudflare issues (like pages not loading): Cloudflare adds an URL endpoint to each domain that they host, /cdn-cgi. It has, amongst others, the /cdn-cgi/trace endpoint that shows which data center services your request. More docs here: https://developers.cloudflare.com/fund
The/cdn-cgi/trace endpoint is documented at [Wayback/Archive] Gathering information for troubleshooting sites · Cloudflare Support docs
--jeroen
Posted in CDN (Content Delivery Network), Cloud, Infrastructure | Leave a Comment »
Posted by jpluimers on 2026/03/17
During a Cloudflare outage¹, I learned about [Wayback/Archive] Wisp.place Documentation | Wisp.place Docs
Decentralized static site hosting on the AT Protocol.
Wisp.place enables you to host static websites directly in your AT Protocol repository. Your Personal Data Server (PDS) holds the cryptographically signed manifest and files as the authoritative source of truth, while hosting services index and serve them with CDN-like performance.
This is the documentation of [Wayback/A] wisp.place by [Wayback/Archive] Ana (@nekomimi.pet) — Bluesky.
Related:
Read the rest of this entry »
Posted in CDN (Content Delivery Network), Cloud, Cloudflare, Development, DVCS - Distributed Version Control, git, Hosting, Infrastructure, Power User, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2025/12/11
Nog niet gecontroleerd, maar wellicht werkt dit ook voor (fragmenten van) radiouitzendingen?
Edit 20260313: redirect toegevoegd voor SEO, en sectie over redirect-checker.
Uit een draad over het liedje “Met puntjes” van Joke Bruijs die een paar maanden terug enkele dagen na haar boezem vriend en ex-man Gerard Cox overleed¹.
Ionica Smeets schreef over het liedje op Mastodon², maar de link naar de audio van de podcast [Wayback/Archive] Andermans Veren – Beluister Andermans Veren zondag 14 januari 2018 | Podcasts | NPO Radio 5 verdween al snel.
Omdat ik al eerder een probleem had met de audio van [Wayback/Archive] Keihard de Beste – NPO Podcast te downloaden, dook ik in de CDN die de NPO gebruikt.
De archivers hadden er wat problemen mee dus het staat in 2 stukken:
- [Wayback/Archive] Jeroen Wiert Pluimers: “@ionica ik ga het je proberen uit te leggen. En dan kan jij het vast in veel simpeler bewoording weer terug uitleggen zodat anderen het ook begrijpen. …” – Mastodon
- …
- [Wayback/Archive] Jeroen Wiert Pluimers: “@ionica hopelijk heb ik je een beetje kunnen helpen met je opmerkingen in…” – Mastodon
- …
- ³
Er waren wat zijstapjes naar onder meer hoe je een goede vraag op het internet moet stellen, dus de draad werd lang (:
Hieronder de volledige tekst, aangevuld met wat gearchiveerde links. Maar eerst twee versies van het liedje “Met puntjes” van Joke Bruijs: opnamen van 1986 en 1988:
Read the rest of this entry »
Posted in Authentication, CDN (Content Delivery Network), Cloud, CSS, Development, Hashing, HMAC, HTML, Infrastructure, Power User, Security, Software Development, Web Development | Leave a Comment »
Posted by jpluimers on 2025/11/29
Besides the August 2025 XKCD infrastructure dependency inspired cartoon on the right, the more recent and great [Wayback/Archive] XCKD: Dependency derivative below is a monumental piece as it combines the recent:
- fiber outage of the Internet Archive
- DoS of Cloudflare by itself
- AWS us-east-1 dependencies outage
- Crowdstrike DoS of Windows machines
- framework-du-jour mentality in the JavaScript world
- many more¹
Image [Wayback/Archive] 36247840bf294a9d.png (1080×1389) from [Wayback/Archive] xyla 🐀🪇: “someone pls alt text this shit…” – buy shitpost cheap:
Read the rest of this entry »
Posted in *nix, Amazon.com/.de/.fr/.uk/..., AWS Amazon Web Services, C, CDN (Content Delivery Network), Cloud, Cloudflare, cURL, Development, Fun, Hardware, Infrastructure, ISP, JavaScript/ECMAScript, Network-and-equipment, Node.js, npm, Power User, Rust, Scripting, Software Development, Web Development | Tagged: Meme, ProgrammerHumor | Leave a Comment »
Posted by jpluimers on 2017/05/26
There are various arguments for using Google DNS (8.8.8.8 or 8.8.4.4) or Open DNS servers or not. A few are listed here:
It basically comes down to two things:
- DNS speed
- CDN speed (Contend Delivery Network providers like CloudFlare, Akamai, etc)
If your DNS server isn’t close to you, it might select a CDN server that is far from you. If you rely on CDN, then you need to weight in that factor.
This is how I decide:
- devices not needing CDN: use Google DNS or Open DNS
- devices needing CDN: use Namebench to pick fast DNS servers that are nearby based on Namebench reports with “Recommended configuration (fastest + nearest)”
–jeroen
Posted in Akamai, CDN (Content Delivery Network), Cloud, Cloudflare, DNS, Google, Infrastructure, Internet, Power User | Leave a Comment »
Posted by jpluimers on 2016/10/22
Less than a month after The IoT strikes back: 650 Gigabit/second and 1 Terabit/second attacks by IoT devices within a week the IoT struck back again: an estimated half a million IoT devices was used to perform multiple DDoS attacks against Dyn Managed DNS that took around 11 hours to resolve.
Google DNS appears to “live” near me in Amsterdam
High availability usually involves a mix of DNS TTL and/or BGP routing. That’s typically how CDN providers like Cloudflare work (it’s one of the reasons that global DNS servers like Google’s 8.8.8.8 appear near to you and over time routes – some MPLS – to it change). Short DNS TTL can help CDN, requires a very stable DNS infrastructure and is similar to but different from a Fast Flux network.
Last months attacks were on a security researcher and a single ISP. The Dyn DNS attack affected even more internet services (not just sites like Twitter, WhatsApp, AirBnB and Github). So I’m with Bruce Schneier that Someone Is Learning How to Take Down the Internet.
Handling these attacks is hard as the DDoS mitigation firms simply cannot handle the sudden increase of attack sizes yet. BCP38 should be part of mitigation, but the puzzle is big and fixing it won’t be easy though root-causes of bugs change as a lot of research is in progress.
I’m not alone in expecting it to get worse though before getting better.
On the client side, I learned that many users could cope by changing their DNS servers to either of these Public DNS Servers:
- OpenDNS 208.67.222.222, 208.67.220.220, 208.67.222.220, 208.67.220.222
- OpenDNS does a good job of handing “last known good” IPs when they can’t resolve.
- Google Public DNS 8.8.8.8, 8.8.4.4
- Level 3 DNS 4.2.2.1, 4.2.2.2, 4.2.2.3, 4.2.2.4, 4.2.2.5, 4.2.2.6
Some more interesting tidbits on the progress and mitigation on this particular attack are the over time heat-maps of affected regions and BGP routing changes below.
Read the rest of this entry »
Posted in CDN (Content Delivery Network), Cloud, Cloudflare, DNS, Hardware, Infrastructure, Internet, IoT Internet of Things, Network-and-equipment, Opinions, Power User | Leave a Comment »
