I’m just this guy, you know?

  • 3 Posts
  • 84 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
  • 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.



  • #### 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.









  • Of course you’re right, but this time America-- significantly, the part that votes Democratic-- is pretty divided over it and that plays to Trump’s strength. By agreeing to keep the war going until next year, Bibi can accomplish at least two things simultaneously. First, it keeps the Democratic base divided between supporting the Israeli state vs doing anything substantive about the death, destruction and genocide occurring in Gaza. Any Democratic candidate that takes a stance against the war publicly will suddenly find their opponent very well funded. Meanwhile a key bloc of voters remains alienated by the party’s policy. It’s a heavy albatross hung about the necks of the Democrats. Harris has to campaign with that as a backdrop, and of course the Republicans will make hay over it.

    Second, if and once Trump back is in office then Israel will be free to roll through Gaza and perhaps even the West Bank, completely wiping out any chance of a Palestinian state. The war ends, and Trump gets to say he resolved the conflict, which means “he won.”

    So, yes. Different than 1980, but not really. All Republican dirty tricks-- and violations of the Logan Act-- to muddy up an election for fun and profit.





  • More, shelter.

    There’s no atmosphere to attenuate hard radiation, so rock overhead is the next best thing.

    There’s no gravity to contain an atmosphere, and domes are expensive and time consuming to build. Meanwhile the crews are exposed to radiation.

    There’s nothing but regolith on the surface of the moon-- finely powdered rock of unknown (and likely poor) assay for vital ores and minerals useful to bootstrap a colony.

    A cave provides shelter, more assay-ably dense ore resources, potentially water in the form of subsurface ice, and potentially a vitrable (melted, glassified rock) cavity to contain a viable, pressurized atmosphere on the quick.

    A cave on the moon is a find. Given the potential for neocolonialism in the next decade or three, it’s a boon for whatever program discovers one.

    edit: typos



  • I used to selfhost more, but honestly it started to feel like a job, and it was getting exhausting (maybe also irritating) to keep up with patches & updates across all of my services. I made decisions about risks to compromise and data loss from breaches and system failures. In the end, In decided my time was more valuable so now I pay someone to incur those risks for me.

    For my outward facing stuff, I used to selfhost my own DNS domains, email + IMAP, web services, and an XMPP service for friends and family. Most of that I’ve moved off to paid private hosting. Now I maintain my DNS through Porkbun, email through MXroute, and we use Signal instead of XMPP. I still host and manage my own websites but am considering moving to a ghost.org account, or perhaps just host my blogs on a droplet at DO. My needs are modest and it’s all just personal stuff. I learned what I wanted, and I’m content to be someone else’s customer now.

    At home, I still maintain my custom router/firewall services, Unifi wireless controller, Pihole + unbound recursive resolver, Wireguard, Jellyfin, homeassistant, Frigate NVR, and a couple of ADS-B feeders. Since it’s all on my home LAN and for my and my wife’s personal use, I can afford to let things be down a day or two til I get around to fixing it.

    Still need to do better on my backup strategies, but it’s getting there.