kanisae

They still recover the fairings. They gave up on trying to catch them out of the air and now just let them land in the water and pick them up.

Fission is the way to go for this for its general simplicity of design and it can self start by manually moving control rods. I never see anyone talking about they are going to restart a fusion reactor if it ever goes offline for any reason.

My thought is to use fission for powering the ship, and fusion for the drive. The fission reactors can start the fusion drive as needed and you can have multiple portable fission reactors like the NASA kilopower designs in an offline/inert state that could be powered on in an emergency.

Yeah residential is capped at 20kw of production for net-metering. I have array rated at 14.5kw and it tracks that at peak pretty well. I hope to add more panels, but they will not be part of my net-metering and be there to charge the future batteries and inverters I want to add.

I am on svec.coop, and have been much happier with them than I was on Dominion.

Glad I am not a Dominion customer anymore. I will happily stick with my coop and pay $0.12/kwh and keep my 1:1 metering.

I normally only commit to "We will give an update in X (minutes/hours) to make sure we understand the problem first. Then start giving estimated timelines in ranges with specific call outs for updates and possible changes to the timeline.

I've found that most management just want to be involved in the process and have definite times set for updates and can handle timeline changes as long as information is coming at regular intervals.

I use an Ambient Weather WS-2902 WiFi Smart Weather Station, easy to setup and integrate with wunderground/accuweather etc, plus simple to use with HomeAssistant in a purely local configuration.

I have an Intel Macbook 2019 for work. I've tried a couple different kvm solutions but they all had issues, always on the Mac side. The best I got was <1 sec switching from Mac to Linux and 10-15 seconds switching from Linux to Mac for everything to stabilize.

I ended up going with the nuclear option of an IP KVM https://www.raritan.com/support/product/dominion-kx-iv-101 that will do all the resolutions I want at 60hz. It was very expensive, but on the bright side it lets me keep work laptops completely unmodified and easily swappable.

Looking at it over the long term, it's something we will need to do regardless of co2 emissions as the sun heats up over it's lifespan. The more interesting part of it is that I've you do Earth you have the tech and infrastructure to do the same to Venus and do the opposite to Mars. Combine the solar shade with some solar panels and you are well on your way to becoming a Khardeshev II civilization.

My particular "killer app" for dnsdist right now is at my house I have 2 machines running dnsdist, set to forward to my pihole by default with health checks. If the health checks fail, the dnsdist daemons failover to google/cloudflare/etc.

This lets me run a single instance of pihole (avoiding all the issues with trying to replicate configs across multiple pihole instances) and still having a solid backup if my pihole server goes down as it is by far the most likely piece of infra to just stop working.

I also use it to route requests to my internal authoritative servers and failover to my external secondary authoritative mirrors as needed. This lets me keep all my local traffic local and still have my external failover as a catch all if my homelab infra is down to my own screw ups or some hardware failures.

I've been a fan of the powerdns project for many years. I have used it for authoritative, recursive and load balancing projects with great success. These days I use their dnsdist project to have fine grained control of DNS at my house to account for my various homelab shenanigans and provide that 99.99999% uptime the family demands.

I owned MMS platform for a carrier back in the day. Everything about it was janky. "Hey let's emulate SMTP commands but over HTTP and then try to track all the different models of phones to transcribe images so they can kinda sorta interopate"

Thenb you got to watch the huge queue build up every Christmas morning and New Years as the inter carrier brokers got backed up hours. All in all, not my favorite carrier app to manage.

* Davmail - https://davmail.sourceforge.net/ * Mbsync (part of the isync utilities) - https://isync.sourceforge.io/

Use Davmail to create a standard IMAP interface to O365, then use mbsync to poll your email account via the Davmail IMAP server and write the messages to a maildir that you can read with most any MUA.

I use aerc with o365 via davmail and mbsync. Using imap directly was to slow, but pulling mail to a maildir works well. Davmail handles all the o365 interaction and supports mfa directly.

How CDMA, eHRPD and LTE backend systems design and deployment. My other odd ball skill is knowing old PBX/Key based phone systems.

I use Davmail to talk to O365 and present standard interfaces like imap/caldav/smtp/etc and then use vdirsyncer to pull down my work calender to use with khal. It works pretty good for me, especially now that Davmail does MFA internally so no account changes are needed in O365

You are thinking of Tau Zero by Poul Anderson. It's well worth reading even though the cosmology is dated.

In the past I worked at a mid level 4G provider in the US who had to deal with the larger providers on a regular basis. I was always astounded at how little they knew about their own networks.

Regarding the articles statement of providers wanting an "all-in-one" solution, I have seen that in person, where management forced it, found it was horrible and then gave in and let us build the mixed vendor solution that worked well. I've personally mixed enode-b's from 2 different vendors to 3 different vendors SGW's and a different vendors PGW with no issues.

The "One Throat To Choke" idea doesn't work if your business depends on that throat to operate so you end up with the vendor calling the shots instead of the business.