If you’re wrong then I don’t wanna be right.
I’m just this guy, you know?
If you’re wrong then I don’t wanna be right.
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
That’s good to know. I’ve pretty much always been a TMO customer aside from a couple of years when I was with Cingular around the time of their buyout. They were pretty open back then.
I buy all of my phones carrier-unlocked, and have never had a problem.
Potential pitfalls are if the IMEI is blacklisted, which could happen if the phone is reported as stolen, or if the radio deck isn’t compatible with your carrier’s network.
In the US, the AT&T and T-Mobile networks are pretty open, and you just need to pop in your SIM card. I don’t have experience with Verizon to know if you can bring your own device or not, but I imagine as long as the phone can work with Verizon then its probably just a matter of visiting a store to have it activated.
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.
A cable-cutting war will be absolutely devastating to the global economy. It’s the modern equivalent of Mutually Assured Destruction. There are few viable contingency plans.
I say this as a telecom wonk: hope and pray and vote so that war never comes.
Because “Commerce Clause.”
Incidentally, Citizen, we haven’t seen you down at the local Rally lately…
I’ve been on the hiring end of those conversations before, and frankly I prefer it when a candidate withdraws. It saves me the time and effort of an interview and let’s me focus on other candidates.
Don’t forget, it’s an inter-view-- you’re vetting them as a potential employer just as much as they’re vetting you as a potential hire. It’s completely reasonable to tell them that after further consideration, you don’t think the you’re a good fit for the job and that you’d like to withdraw your application, thanking them for their time and consideration. It’s more professional to be respectful of everyone’s time and withdraw since you already know you don’t want the job.
If they booked you plane tickets or something to fly you in for a face to face…? Eh, they might have a beef with that. You’d have wanted to withdraw before it got that far.
You know what you did
When you burp, your stomach contracts and your esophagus relaxes, allowing air to expel. When you hiccup, your diaphragm contracts, and your esophagus closes up. I dunno. Kinda. I’m mock-hiccupping and burping as I type this and that seems to be what’s going on.
When all three contract, everything jams up, and that hurts.
Cool story time: Sometimes I hiccup really hard and it’s kind of painful. Thanks for coming to my TED talk
Looks like Python, but in an editor with a weird TUI scrollbar
That … That’s baller. I’m “doughy” at best, and its all I’ll ever be.
People are more buoyant in salt water because it has higher molar mass. Humans on average are about 90% density of water by mass so about 10% of your frame would float above the surface, which is generally enough to expose your nose. Of course you can articulate your neck, float on your back, tread water…
Salinity also matters. Salty water you might be up to 3% or 5% more buoyant, pound for pound, compared to fresh water.
Really, it depends on how fat and how salty, but generally the difference is less than 5% by mass.
Swim.
Not get splashed or crowded by kids, mostly.
edit: lol, sorry. misinterpreted the question
Public pools have a shallow end and a deep end. It’s difficult (but not impossible!) to drown in the shallow end because you can just stand up, but you can still swim.
Most humans, especially fat Western humans, are naturally buoyant. Completely inert, most (fat) Western people will float above the bottom of their nose (because we’re fat.) Very lean or muscular people tend to be more neutrally buoyant or even negatively buoyant (sink), YMMV.
Most important thing to remember as an Aquatic Mammal is you WILL get water in your nose, and sometimes down your windpipe. DO NOT PANIC. It burns, you will want to cough. Resist that urge. If you are under water or do not have free air passage, DO NOT COUGH. Control the urge and break the surface, then you can go ham coughing and sputtering.
The most important thing about being in and around water is to be comfortable. If you’re not comfortable, you’re too deep. Get shallow.
source: PADI certified diver
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.