Its ambiguous, but it seems to expresses the speaker regrets not feeling regretful about the topic, as if to acknowledge that one might (and maybe should) sympathize with the other party, but in fact does not.

Depending on the context, it might also merely express that speaker is an asshole.

My next mower will probably be a lawn service

San Jacincto was a different battle wherein Mexico got their collective ass kicked in there. The Alamo was a rallying cry.

Alamo itself was a rout for the Texians [sic]. There’s no side-stepping that. It goes as it goes.

I didn’t so much forget it as I did assume Texans were just playing the martyr for getting their collective asses kicked in. Again.

You know… Like Dallas Cowboys fans?

No worries, the other poster was just wasn’t being helpful. And/or doesn’t understand statistics & databases, but I don’t care to speculate on that or to waste more of my time on them.

The setting above maxes out at 24h in stock builds, but can be extended beyond that if you are willing to recompile the FTL database with different parameters to allow for a deeper look back window for your query log. Even at that point, a second database setting farther down that page sets the max age of all query logs to 1y, so at best you’d get a running tally of up to a year. This would probably at the expense of performance for dashboard page loads since the number is probably computed at page load. The live DB call is intended for relatively short windows vs database lifetime.

If you want an all-time count, you’ll have to track it off box because FTL doesn’t provide an all-time metric, or deep enough data persistence. I was just offering up a methodology that could be an interesting and beneficial project for others with similar needs.

Hey, this was fun. See you around.

You know what? I’m gonna disengage here. You’re not hearing what I am saying.

#### MAXLOGAGE=24.0
Up to how many hours of queries should be imported from the database and logs? Values greater than the hard-coded maximum of 24h need a locally compiled `FTL` with a changed compile-time value.

I assume this is the setting you are suggesting can extend the query count period. It still will only give you the last N hours’ worth of queries, which is not what OP asked. I gather OP wants to see the cumulative total of blocked queries over all time, and I doubt the FTL database tracks the data in a usable way to arrive at that number.

Ah, well if you know differently then please do share with the rest of us? I think the phrasing in my post makes it pretty clear I was open to being corrected.

So, like a running sum? No, I don’t think so, not in Pi-hole at least.

Pi-hole does have an API you could scrape, though. A Prometheus stack could track it and present a dashboard that shows the summation you want. There are other stats you could pull as well. This is a quick sample of what my home assistant integration sees

That counter, I believe, for the last 24 hours. It will fluctuate up and down across your active daily periods

I see where this question is leading, and I don’t think I like the implications

Unless I misunderstand your question, draw.io can be downloaded as a standalone Linux application and run locally.

Likewise, the Xfig package should he available in most Linux repos. It’s old, but good enough for a quick sketch.

edit: aha. My mistake. My eyes slid over ‘open source’ in the title*, and even still I hadn’t realized it was an Apache license.

* Whaaat, it was pre-coffee? Let the purest among us cast the first stone.

I was gonna say snowflakes, but now I can’t unsee the buttholes.

deleted by creator

I suspected, but I’m not about to let facts get in the way of comedy.

(No really, I feel bad)

Maybe, maybe not. Time will tell.

See you around, hey?

I’ve also been watching this account, and I think it’s an agitator organization. The posts are too frequent across several focused topics, and engagement is contemporaneously too cogent across those topics for it to be a single person.

I call shenanigans.

Alternatively: I find I rarely need or want to visit a user’s profile, and would be fine with accessing it through the 3 dots menu.

Sure that’s easy. All you need is an HX711 sensor load cell amplifier taped to the floor of the chamber where it sits under an edge of your bottle.

Full, 5 gal (US) jug or water weights 40lbs nominal. If you have the same bottom feed dispenser I have, it starts drawing air with about 16-20oz of water left in the bottom.

You’d want to calibrate first for the sensor without weight (tare), and then for a full bottle’s weight (40lb) accounting for cosine error of the bottle being slightly tilted by the thickness of the sensor. Or, tape a couple of shims at 120° offset from the sensor to level out the bottle.

Finally, note the weight of an “empty” bottle with that 18ish oz of water in it, which will probably be close to the zero value.

Now you can calculate % full by looking at the ratio of the current weight between your full/empty value as:

%Water = [ (W_full - (W-18oz -W_tare) ) - W_now ] / (W_full - (W_18oz - W_tare) ) x 100

I guess technically that’d be the email account at my employer where I started some decades ago. Before Google and their Gmail was a thing, anyway. Or, livejournal, I guess. …MySpace… Oof, AOL… Usenet, maybe…

Gah. I’m old.