Hdcp bypass splitters seem easy to find, have you tried one? There are also hdcp converters so if you have a splitter that only bypasses 1.4, you can try hooking it up to a 2.whatever to 1.4 converter.
I also can’t remember how they work exactly but you might need an hdcp compliant display connected to the main output of the splitter so the CC can establish an hdcp handshake. Idk if that’s only a thing with some of them. Good luck!
I had the same dilemma after mullvad stopped allowing you to create port forwards. I switched to Proton which works fine but I’m curious what other options are out there. It can be hard to find the details about port forwarding, especially if it only works when using their app and not with openvpn/wireguard which is easier for running containers.
I love to see this. It is kinda weird to have to use rolls, but I guess the mechanical complexity of separating sheets and feeding them reliably is not fit for an MVP. I wonder how accurately the cut sheets would stack with individual sheets of another brand.
Luckily they are on 2.0.1 now so there has been 2 stable version by now
Tesla Robotaxi Reports 3 Crashes In Austin In July, Hides Details
By Brad Templeton, Senior Contributor.
Brad Templeton, who was early at Waymo, covers transportation’s future
Sep 18, 2025, 04:43pm EDT
Sep 22, 2025, 01:24pm EDT
(Photo alt text: Musk Self Driving Promises)
A rider boards a driverless Tesla robotaxi, a ride-booking service, Sunday, June 22, 2025, in Austin, Texas. (AP Photo/Eric Gay) Copyright 2025 The Associated Press. All rights reserved
Tesla’s crash report for self-driving vehicles to the federal government lists 3 crashes involving the Tesla robotaxi, in July, shortly after launching their pilot service in Austin, TX. Tesla redacted much of the relevant data about the crashes, claiming they reveal important proprietary information. By this date, Tesla’s approximately dozen cars had done fairly few 7,000 operational miles. Let’s unpack the details.
UPDATE: All Crashes in the government database were listed as on July 1, but it is likely this date is used for all crashes in July. An earlier version of this story presumed the listed date was the real date.
The report is current as of August first, suggesting there were no more crashes in July. It’s not clear how many miles the cars drove: During the Tesla earnings call on July 23, it was reported they had driven 7,000 miles. That might have been in the first 30 days, or it might have covered just driving in the second quarter, ie. from June 22 to June 30. Either way it’s a small amount of driving to have any crashes.
This is particularly true because these Tesla “robotaxis” aren’t actual robotaxis, they have a safety driver on board, located in the passenger seat. Tesla defies industry convention and calls the safety driver a “safety monitor” while they are in that right hand seat, but, like a driving school instructor they have an emergency stop button they keep their finger on, and can access the wheel, they are the responsible driver for legal reasons. (This is what a safety driver means, they are not expected to actually drive the car, they are the legal, licensed driver who can intervene if the car makes a mistake.) The crash rate with a safety driver should be very low. Tesla claims its Autopilot (mainly freeways) system with a human monitoring it has an airbag deployment every 5 million miles, for example, a rate probably modestly better than the drivers would have alone. (Tesla claims 10x better but this is highly inaccurate–people in the same demographic have airbag deployments on freeways probably every 3-4 million miles, though this number is not easy to determine.)
With the crash description and other important details like location redacted, it is hard to really determine what happened.
Crash #1 looks like the Tesla was rear ended while stopped which would be no fault of the vehicle or safety driver. Crash #3 is harder to tell–without the details, it could be the Tesla backing up, or it could be a rear-ending. Crash #2 is the most serious. Even one crash of this nature in the first 7,000-25,000 miles is cause for significant concern, especially with a safety driver on board.
During this period, Waymo had many crash reports, Zoox had 7 and May had 2, others had 1. The other companies do not redact the details as Tesla did. Waymo had a famous crash into a lighting pole that might be similar to crash #2 above, but this took place in a vehicle that’s giving 250,000 rides/week and just reported 96 million miles–their crash rate is actually better than expected. Analysis of the reports for Waymo suggest they are not at fault for the vast majority of their reported crashes. Even one at fault crash, especially an injury crash, in under 25,000 miles is an extremely poor rate. You can’t extrapolate well from a single data point, the strong implication is that Tesla has to get much better – perhaps 300x better, to match Waymo. The presence of the safety driver implies the improvement goal might be much greater than 100x.
It is unclear why Tesla redacted most of the important details, or what value there is in hiding data which might paint them in a better light (for example, confirming they were rear-ended.) The reports claim there was no safety driver in all 3 crashes, but that’s very unlikely, it’s more likely Tesla just trying to pretend their right side safety driver is not a safety driver.
Not listed is an event that was shown on video where the Tesla’s tire hit the front side of a parked passenger car in a parking lot on day #1. It is possible it did not need to be listed because damage was limited to tire marks, or because it was on private property. Either way, it’s at least two at-fault crashes for the Teslas, possibly three.
Let’s hope that when August reports come out, we’ll not see any from Tesla, unless they are doing a lot more miles. In California they keep the safety driver in the left seat, and they have started doing that in Texas for at least some rides, due to new regulations. Crashes with safety drivers should be ridiculously rare in a mature product–they require the system to make a major mistake, and for the human to also not handle it at the same time. When Tesla Autopilot and FSD were less mature, they made mistakes very frequently, every few miles, but even with amateur safety drivers, the resulting crash rate was low. Professional safety drivers do even better.
It’s odd that these crashes didn’t end up online. Back in July, only invited influencers were able to ride in Tesla robotaxis, and many of the rides were recorded on video. Perhaps these crashes took place during empty vehicle moves. They just say that “all passengers were belted” but that would include the safety driver. For other vehicles, there are no passengers when the vehicle is moving between rides. It’s also surprising that a crash at noon which involved the Tesla being towed away didn’t get widely reported, even in social media, considering the scrutiny and public interest in the project. It’s unclear what else we are missing.
Is external libraries maybe what you’re looking for?
There’s already an issue open for it: https://github.com/immich-app/immich/issues/1713
Be sure to thumbs it up!
A while ago I got tired of tracks going missing from my playlists because of stuff being removed from Spotify so I started buying everything on Bandcamp and then playing it from my jellyfin using finamp.
The main novel thing is non-soldered ram that’s fast. The huge improvement is upgradability in new laptops.
Or alternatively:
- Does this mean unverified sideloading is going away on Android?
Yes
It’ll be hit or miss. If it’s ripped from the same source then it should be fine, but different editions, TV edits, scenes that are cut in some versions or additional title cards at the beginning will mess it up so you’d need to QC it.
If you search for pfsense alias script, you’ll find some examples on updating aliases from a script, so you’ll only need to write the part that gets the hostnames. Since it sounds like the hostnames are unpredictable, it might be hard as the only way to get them on the fly is to listen for what hostnames are being resolved by clients on the LAN, probably by hooking into unbound or whatever. If you can share what the service is it would make it easier to determine if there’s a shortcut, like the example I gave where all the subdomains are always in the same CIDR and if one of the hostnames is predictable (or if the subdomains are always in the same CIDR as the main domain for example, then you can have the script just look up the main domain’s cidr). Another possibly easier alternative would be to find an API that lets you search the certificate transparency logs for the main domain which would reveal all subdomains that have SSL certificates. You could then just load all those subdomains into the alias and let pfsense look up the IPs.
I would investigate whether the IPs of each subdomain follow a pattern of a particular CIDR or unique ASN because reacting to DNS lookups in realtime will probably mean some lag between first request and the routing being updated, compared to a solution that’s able to proactively route all relevant CIDRs or all CIDRs assigned to an ASN.
I think the way people do it is by making a script that gets the hostnames and updates the alias, then just schedule it in pfsense. I’ve also seen ASN based routing using a script, but that’ll only work on large services that use their own AS. If the service is large enough, they might predictably use IPs from the same CIDR, so if you spend some time collecting the relevant IPs, you might find that even when the hostnames are new and random, they always go to the same pool of IPs, that’s the lazy way I did selective routing to GitHub since it was always the same subnet.
That’s what I do. 1.6TB currently on rsync.net, only my personal artifacts excluding all media that can be reacquired and it’s a reasonable $10/mo. Synced daily at 4am.
If I wanted my backups to include my media collection or anything exceeding several TB, I would build a second NAS and drop it at my parents’.
I don’t have a bambu so this is just a shot in the dark - but did you maybe use a multi color profile for the single color print? I seem to remember at one point getting purge towers on single color prints when I forgot to switch back to the single color profile.
I’m also curious about people’s experiences when it works - I already had 1 treatment on my underarms and it thinned it out a lot. My sister had 5 or 6 sessions for her underarms and it’s been all gone for years. Considering my decently light olive complexion and dark hair seems to be a good candidate, I’m wondering if I should do other areas but I still fear getting it done on my face and being stuck with a patchy mess if I stop being able to afford it. I rely on looking half decent unshaven to be able to not shave for a week every week and not care so if I had to start shaving every couple days that would suck.
Sounds almost like something the sentinels from the matrix would be able to do with their “electrical signature” detection. I guess it’s all killbots in the end.
I noticed the article mentioned Dropbox, g drive, and OneDrive and I was curious and from searching around it seems you can also use ftp and ssh. That’s super cool, being able to script an auto backup to my NAS makes this a lot more appealing.
FYI the codename for the Xiaomi Redmi Note 13 5G is “gold”. You’ll usually see stuff for your phone labeled with that codename since it’s much shorter and easier to check than the whole name where you have to check pro vs non-pro, 5G version, etc as other variants will have completely different codenames.
If roms don’t have official support, then basically your other main option is to look for unofficial builds made by random people on XDA. I’ve used unofficial builds for many years in the past and they’re generally fine, but it’s up to you.
I don’t see any rom threads in the XDA forum for gold, so unfortunately I can’t really help any more. Good luck!
(Skimming around the XDA threads, it appears that the lack of roms is due to mediatek not releasing necessary source code, so if you want custom roms, it’ll be a lot easier to find them for a different phone)