this post was submitted on 19 Aug 2025
622 points (97.7% liked)
Technology
74233 readers
4280 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Uh, how often are you using the Internet to connect to a computer in your home town? Maybe 5% of the time?
I've never used Starlink, but with a basic understanding of geography and optics, I'm going to bet that in most scenarios the latency difference between Starlink and fiber is negligible, sometimes even being faster on Starlink, depending on the situation.
That said, I'm not suggesting Starlink is a realistic replacement for fiber, just that latency isn't the big issue. (It has other serious issues)
Much more frequently than you think with CDN endpoints.
Ok, so actual question, How useful are CDN endpoints these days with https everywhere? Because most encrypted content is unique to a single web user, caching isn't super useful. Also you can't cache live content like video calls or online games. I'd imagine the percentage of cacheable content is actually fairly low these days. But like I said, I don't actually know the answer to this, i'd be curious to hear your take.
Edit: it's weird to get down votes for a question.
HTTPS / TLS has little to do with it. Don't think of the endpoint as a cache between you and the origin. The DNS name given to the endpoint is the origin from your browser's perspective. How content gets cached on the backend is irrelevant to the browser. Live video that someone else in your area is also watching is cacheable. Images to load a page, very cacheable. The personal stuff is mostly HTML specific to you but that's quite small.