Check in your settings whether you have disabled the visibility of bot responses. This can happen if bots replied to you and your settings are set to not see them.

I find it satisfying to see the graph come down :)

Yes, sorry, there was some serious lagg in fetching posts from Lemmy World that persisted for several days and accumulated a 1-week delay.

But after upgrading Mander it is now fetching data from LW quite rapidly and it should be back in-sync in about a day and a half from now.

If you are curious about the ranking algorithm, there is some info here: https://join-lemmy.org/docs/contributors/07-ranking-algo.html

Dragonfruit lemonade (agua de pitahaya) is delicious!

Cool initiative! Thank you for setting this up!

I have pinned an announcement to my instance so that it’s easy for users to find it.

Thank you - that makes sense!

I think I understand why this is done now. Most HTTP requests are hidden by the SSL encryption, and the keys to decrypt it are client-specific. So, if one wants to block ads at the network level without needing to get the SSL keys of every client that connects to the network, then this is the most specific amount of information that you can provide the PiHole with. The HTTP blocking needs to be set up in a client-specific manner, and that’s why they work well as browser extensions.

Thanks!

Adblocking plugins aren’t limited by this and can filter the actual content and HTTP requests made by the browser.

Why is this the case? What rules do Adblock plugins use that allow them to determine that something that is being served is an ad? I understand from what you are saying that Adblock will block on the basis of the HTTP requests instead of filtering at the DNS level - do ads come with specific HTTP headers that are not processed by the pi-hole DNS server and thus can’t be used for filtering? I don’t fully understand yet the details of how the two ad-blocking mechanisms operate, so their differences are not obvious to me.