I thought data caps for home internet were a thing of the past…

I’ve somewhat recently moved back to a very rural area of the Midwest. Small town. No stop lights. Biggest businesses other than the bars are Casey’s, Subway, and Dollar General.

And we have one ISP (not counting DSL) — Mediacom. When we first signed up, I had to go with the second service tier. But not because of speeds, but so I could have a reasonable 1 TB/mo data cap.

Lucky me, they increased the cap to 1.5 TB. 🙄

I hope that in my lifetime I can see ISPs regulated as a public utility.

  • @zikk_transport2@lemmy.dbzer0.comEnglish
    3•1 year ago

    Yes, this one.

    Pihole has a cache also though, does this do something different?

    The cache you are referring to is basically:

    1. Device asks to solve google.com
    2. Pihole asks upstream for IP.
    3. Pihole returns IP to device
    4. Another device asks to solve google.com
    5. Pihole returns IP from cache to another device.

    Blocky has the same functionality, but it also detects which domains are frequently requested, therefore puts them into “always keep up to date in cache”.

    Basically let’s say that many devices keep requesting for “google.com”, blocky detects it as frequently reqiested domain, and as soon as it expires, instead of removing from cache, blocky simply refreshes it’s value and keeps in cache. Expires again? Refresh and keep in cache again. And does this idefinitely.

    Let’s say “google.com” TTL time is 10 minutes. Once 10 minutes passes - blocky should remove it from cache, but because precatching is enabled - it will refresh it instead of removal.

    Check documentation for details. ✌️