Sounds really cool! Do you have a page describing your project with some pictures? It's funny I checked your post history before asking and found that you made the same comment I'm doing today to someone doing something similar one year ago! Is it what got you started?
Not yet! I'm a mechanical engineer by trade, so my C++ is horrendous. I am still in the very early phases of this project, once I get past the hardcoding all of my variables I will share some more.
I Do Cars did a tear down of the M96 engine from a 986 Boxster S. Seeing inside of them, it makes sense how these motors cost $20K to teardown, rebuild and remedy Porsche's cost cutting in their first water cooled engine. I would own another 986 or 996 in a heartbeat. Tear down video: https://youtu.be/qrkALiq5hTU?si=0OmBKYcim-cflJEy
Thanks! I’m not sure what people expect from these engines- they’re somehow basically the most reliable car engine from that era (they regularly came out at the top of reliability ratings), while still making ~1.5x the power per displacement that was standard at the time. Things like the D chunk failure and IMS failure can happen, but most people will get a reliable 200-300k miles before they do, and the IMS can easily be prevented with a new bearing kit that is fairly cheap and easy to do. The 2.7 Boxster engine had none of the cylinder issues- that’s the Porsche to get if you want low hassle fun transportation IMO.
It’s true they’re expensive to rebuild properly but you can get used engines with a lot of life left for just a few k.
Curious, what does someone gain with MacTCP? I'm not familiar with the space, but a casual glance (not an assessment!) suggests that OpenTransport was standard-ish from system 7.6 onwards.
Does it boil down to compatibility with older hardware?
Different software. They had different APIs from the programmer perspective. MacTCP was older and was based on Berkeley sockets (I think with some BSD code in the implementation?) and was somewhat primitive.
OpenTransport was fully multithreaded and based on SysV UNIX streams. Technically much superior. It has partial MacTCP API support for older apps but some programs demanded real MacTCP to work properly. I think Mac was the only place that really used Streams widely. Mac network programming in the OpenTransport days was alien from a Unix perspective.
OS X now uses sockets like everyone does these days.
Going off memory here it has been a long long time.
Carriers have been blacklisting IMEIs for at least 10+ years. Since phones tended to be carrier-locked back then you couldn't go to a new carrier without being in good standing to get your device's unlock code from the old carrier. Now that devices are available unlocked by default, it is probably harder since it would require carriers to communicate IMEIs?
I looked it up. US Carriers were forced by the US government to start blacklisting them in the final months of 2012. They didn't do it voluntarily.
Australia had been doing it since 2003. IMEIs have been around for 30 years? Everyone having a cellphone is still a relatively recent phenomenon, but according to Pew 80% of American adults had cellphones for several years already before carriers were forced to deal with stolen ones.
~15 years ago the blacklists were certainly shared within Europe, but there was an intercontinental trade of blacklisted phones from Europe to Africa (and, if memory serves, Asia).
There are some business/enterprise displays offer a "framework" approach by using a RPI CM4 to control everything. Unfortunately, that is out of reach for most consumers lacking a corporate sales account.
That also makes me wonder how much TVs are being subsidized with ads and sponsored content. Those businesses displays cost significantly more than a regular consumer TV.
UniFi doorbell requires a UniFi NVR, and maybe UniFi console/ AP. The non-pro doorbells require wifi. POE is only an option on the with the Pro doorbells via a proprietary USB-C to POE cable.
I am currently using 2 of the G4 Pro doorbells. They are direct PoE to my UDM-Pro SE without any adapters. The recordings are stored locally and are private.
Your UDM-Pro-SE is where you run your Unifi Protect. I.e. you need to have another device from the same vendor that supports NVR functionality.
The above mentioned Reolink doorbell will happily run with any NVR from any other vendor that supports relevant standards (ONVIF). Or even without NVR (it has microsd slot for local storage on device).
My UDM-Pro-SE has a 12TB hard drive in it and acts as the NVR itself without issues. I do not need any APs (doorbells are direct wired PoE), and I do not need a separate NVR.
Yes but the UDM-Pro-SE is a separate product from the doorbell. The Reolink doorbell does not need a separate product to function. You can just get a POE injector or POE switch from any brand, run Home Assistant on a Raspberry Pi or NUC and it'll work. The UDM acts as an NVR for your doorbell camera, you couldn't use it without it, right?
You can run UniFi console as software on any* device to manage the doorbell, which would then allow you to use Scrypted as the NVR and expose it to Home Assistant.
I love my Esterbrooks, I was gifted a green model J many years ago, and I use it frequently at home. I recently purchased an SJ from an antiques market, and revived it with a new ink sac ($20 all in), this pen now lives on my desk at work. I prefer their lighter weight to the Pilot Metropolitans.
in 2015 I bought a lifetime license for SpeedDial2 Pro, but in 2021 they switched to a yearly subscription model to sustain upkeep and development. I am thankful that their team has grandfathered in lifetime licenses for use of the core feature set. I believe the new features that came after the subscription model are only for the new subscribers.
