Anyone know of something like the ratgdo, but for motorized swing gates (like DoorKing)? I'd love to check the status as well as actuate open/close, but some of the "upgrade" quotes I've seen are $5k USD. It seems like I should be able to get this thing integrated with either WiFi or Z-wave...
RIPE Atlas is an amazing project. I remember getting 3 probes at a NANOG and telling my coworkers about it. They couldn't believe that it was a free project, and that I didn't have to pay anything for the probes. Great stuff from RIPE, for free! (Anchors cost dough but probes were free)
I've yet to make it out of the lab. The failover solutions seem to be A-B rather than A-B-DR. That is, you can have a primary and a replica (probably in the same DC/AZ), but you can't do a primary, a replica, and another replica in another datacenter that can function on its own (in a DR capacity).
Citus uses physical replication for worker and coordinator nodes, and things start getting complicated when you're trying to monitor the status of all the replicas. With vanilla PostgreSQL, you don't have this issue. I'm guessing that they solve this in Azure with block-device primitives at the storage level or something along those lines? It's probably not insurmountable to do it yourself, but we're not yet at the grip-n-rip enterprise offering.
Depending on OS, you might need to actually put the interface name in there? As you can have fe80::1 on multiple interfaces...it being link-local. Maybe browsers are holding it back?
Backup on site and store tertiary copies in a cloud. Storing all backups in AWS wouldn't meet a lot of compliance requirements. Even multiple AZs in AWS would not pass muster as there are single points of failure (API, auth, etc).
"Why was iron low?"
"We don't know."
"It's better now?"
"Yes we fixed it!"
If they don't know what's wrong, how did they know what to fix? This is still fishy to me. Also, shame on the author for using the term "ratted out" when this company was selling a substandard product to Americans.
It sounds like PayPal isn't actually buying Bitcoin, but instead created their own proxy bookkeeping instrument. Speculation, but that's what it sounds like to me if you can't have Bitcoin's utility and only its store/speculation.
My point was to show that she had a legitimate need, then let the permit lapse when she no longer had a need. She didn't have one for an abuse of power.
I wasn't debating the merits of the CA shall issue policy.
In other words, don't pick a fight where there isn't one.
She had one because the anarcho hippie terrorist groups of SF targeted her and shot up her home several times. When the group was arrested/disbanded, she let her permit lapse.
While I agree it sucks that some rich and powerful people seem to live by a different set of rules, it's not like she had a permit just for kicks.
I hope that they can handle all those deletes on their spinning hard drives. Append-only is easy, since you're never deleting and there's no chance for fragmentation. Once you get deletes, you're going to get fragmentation and performance goes to hell.
Yet long-lived connections (processes) suffer tremendously on Postgresql servers with high cores (> 100) and a decent amount of memory (> 256GB). Connection pooling is good, but you gotta recycle those connections on a regular basis.