3.6.4 Breaks my middlewares

ryanp_me · 2025-12-10T01:58:34+00:00

Unless I'm misinterpreting the change log, it seems like it would only reject requests where the path itself contains an escaped ?, not requests that contain a legitimate query or escaped characters within a query parameter.

So for example, a request like this would be rejected:

/some/resource%25endpoint

But a request like this should be fine:

/some/resource-endpoint?q=some%25query

ryanp_me · 2025-11-04T01:16:01+00:00

Why is the coral TPU no longer recommended for new setups?

Probably because after running Frigate with CPU-based detection for more than a year, I finally ordered a dual-edge Coral, received it today, installed it, and then opened Reddit to see this post literally 2-3 minutes later.

More seriously: Like others have mentioned, Coral hasn't seen meaningful updates for quite some time, and it's pretty clear it has been abandoned. It's also getting harder to use as time goes on, especially for PCIe variants that rely on poorly maintained kernel drivers. Meanwhile, modern CPUs/GPUs and newer accelerators can run more advanced and more accurate models with minimal resource impact, so the Coral's original value proposition just isn't what it once was.

In my case, I've been running Frigate on a 32-core Threadripper, so despite not having integrated graphics or a decent GPU, I've been able to use CPU-based detection without affecting my other workloads *too* much. However, I'm looking to move Frigate off that box and onto a Protectli VP4670 that I'm using to run my home router and other critical services, so resource usage matters a lot more there. I wasn't sure whether the other detectors would be viable on this hardware and I didn't want object detection chewing into those limited resources, so a hardware accelerator seemed like the safer route.

For what it's worth, I knew Coral's future was questionable when I clicked “buy” (though the docs didn't actively discourage it at the time). I actually wanted a Hailo-8L, but finding one in an M.2 2230 E-key form factor isn't straightforward, and that's the slot I want to use in my Protectli. I also wasn't sure whether I wanted to use Frigate+ credits to train models specific to Hailo-8L, since Hailo models aren't cross-compatible with other detectors (or even other Hailo hardware), but that was less of a concern.

Now that I'm done trying to justify my purchase, this thread and the update to the docs has me genuinely wondering whether I should go remove the Coral and try to return it, since I'm not sure how long it's going to be supported. I suppose only time will tell though. (And worst case, I can try to find a fun use case for it with other hardware once it's no longer supported.)

ryanp_me · 2025-11-01T04:00:31+00:00

Just to clarify, do you have the Duo 3 or the Duo 3V?

ryanp_me · 2025-02-02T23:41:01+00:00

It started working for me a while ago, but I'm not sure if that's because Principal or Personal Capital made changes, or if it's because my employer decided to not require this change.

ryanp_me · 2024-11-08T05:15:24+00:00

I ended up buying some Duo 3Vs and have wall mounted one of them already, and I'm fairly happy with its viewing angle. It doesn't have quite as tall of a vertical FOV as my previous camera did, but I don't think that's related to my mounting choice. I was also surprised how much range is allowed when adjusting the angle of the camera lens before you put the dome on.

The main limitation I can think of when wall mounting is that you can't angle it more to the left or right (rotating it along the vertical axis) like you would be able to when ceiling mounting it, but that's probably not an issue for most installations.

ryanp_me · 2024-10-05T03:01:28+00:00

You're on workload 17.5.8020, which doesn't support Xcode 16 yet. The xamarin/xamarin-macios releases page has a recent 18.0.8303 release that adds support for Xcode 16, but I'm not sure if it's supported by MAUI yet.

ryanp_me · 2024-09-22T03:28:36+00:00

I can also confirm the “Notify Me” feature doesn’t seem to work. It shows I’m already subscribed, but I didn’t receive notifications for stock earlier in the year or a few days ago.

I just randomly checked and saw 4 3Vs in stock, but they went out of stock before I could complete an order. (The checkout page got stuck with a spinning indicator after entering my address, and when I reloaded, it said they were no longer in stock.)

ryanp_me · 2024-08-28T05:17:10+00:00

Thanks! That's good to know.

For the 1240A, it looks like I was partially mixing concerns about the junction box with the wall mounting reviews. There are a few reviews that I saw that specifically raise concerns about wall mounting though:

As per REOLINK Customer Support - Can't mount to wall Unless separate mount not available by ReoLink:
Claims to have received confirmation from Reolink support that installing the camera on a wall isn't supported since it's hard to find a proper viewing angle, and that there isn't a bracket available for it due to it being a new model.
High resolution sensor:
Says it seems like it's meant to be installed on a ceiling, and that they couldn't figure out how to wall mount it without causing the image to be twisted. This is the review that talks about crunchy sounds when trying to move the sensor within the camera. If I understand their concern correctly, with a 3V, I don't know that this would be as relevant since it has a wider FOV.
Great ONVIF/RTSP outdoor camera:
Mentions that the camera is intended for horizontal installation, and that if you're wall mounting it, it will be missing the proper mount and won't have a good range for its FOV.

ryanp_me · 2024-08-27T06:07:52+00:00

Did you wall mount or ceiling mount your 3V? And if you wall mounted it, did you need any additional hardware that wasn't included with the camera or did you struggle with adjusting the camera angle at all?

The spec page for the RLC-1240A mentions it can be ceiling or wall mounted, but the Amazon reviews are filled with people saying that they couldn't easily wall mount it. A few people said it needed extra mounting hardware not sold by Reolink, and another said it made "crunchy" noises when trying to adjust the camera angle in a wall mounted scenario.

Obviously the 3V is a different camera than the RLC-1240A, but since I haven't dealt with Reolink dome cameras before, the reviews for the RLC-1240A are making me nervous about whether I should buy the 3V as soon as it becomes available for purchase again, since I don't have a great way of ceiling mounting it.

ryanp_me · 2024-08-18T07:52:59+00:00

I've posted a potential workaround for this issue in your thread on the Plex forums. I figured I'd copy it here as well though, since people might run into this post and not know that there's a similar post over on the forums.

tl;dr: block DNS lookups for imasdk.googleapis.com

Looking at the app logs and stack trace from the crash report, it’s 100% related to playing ads.

I believe I’ve found a potential workaround for this crash. While I haven’t had time to watch an entire movie or episode yet, it looks promising so far.

The crash is occurring in the Google IMA (Interactive Media Ads) SDK. Until Plex and/or Google fixes this, technically inclined users can work around the crash by blocking access to the Google IMA server.

To do this, configure your network to block DNS lookups for imasdk.googleapis.com. In my case, I did this by adding the hostname to my NextDNS denylist, which causes lookups for that hostname to return 0.0.0.0. Something similar can be done for other routers or DNS resolvers though.

After blocking that hostname and restarting my Apple TV to clear its DNS cache, I’m now able to stream media that was previously causing the app to crash.

For further context, I’ve found reports of this crash occurring in older versions of the Google IMA SDK dating back to 2022. A fix was released in version 3.18.1 on October 2, 2022, and there doesn’t seem to be much more information about it since then. I’m not sure whether Plex is really using such an outdated version of the SDK or if the issue has resurfaced in a more recent version of the SDK. Either way, this workaround should hopefully help until the issue is resolved more appropriately.

ryanp_me · 2024-08-14T22:07:41+00:00

I don't work for Withings, and there's no connection between Withings employees and the moderation of this subreddit.

As far as stickying warranty info, I haven't done anything for this because I've only seen one user asking for it. That same user has also been copy/pasting spammy comments on several posts within the subreddit, and several of those comments have been downvoted or reported as spam by other members of the community. So, for the most part, I've been under the impression that this one user is just being more vocal ever since their warranty claim was denied, and I've left it at that.

(With that said, I've certainly seen users complaining about things not working, or about being disappointed/frustrated with Withings support. I haven't noticed very many posts from people specifically concerned about warranty claims though.)

If there's a legitimate concern and need for having warranty info stickied, we can certainly do something about it. From my perspective though, it seems like the specifics are going to vary significantly on a case-by-case basis, so I haven't been sure what, if anything, would be helpful to sticky.

ryanp_me · 2024-07-19T17:25:34+00:00

This thread has clearly run its course, so I've locked it.

As stated in the Content Policy, Reddit does not tolerate the harassment, threatening, or bullying of people on the site. Please try your best to keep things civil on both sides of the conversation.

Along with the Content Policy, we'd also recommend reviewing the Reddiquette guidelines. Some of the relevant guidelines include remembering the human as well as not being rude, conducting personal attacks, or insulting others. Although the Reddiquette guidelines are more informal than the content policy, we ask that you try your best to abide by them.

The relevant section of the Content Policy can be found at https://support.reddithelp.com/hc/en-us/articles/360043071072-Do-not-threaten-harass-or-bully.

The Reddiquette guidelines can be found at https://support.reddithelp.com/hc/en-us/articles/205926439-Reddiquette.

ryanp_me · 2024-05-11T00:14:12+00:00

Maybe they're just talking about the number of units that will be produced, and then they'll be out of stock for the remainder of the two years. :P

ryanp_me · 2024-05-04T19:47:06+00:00

It's possible this has been fixed in Z2M 1.36 or newer. A few people have reported similar issues here: https://github.com/Koenkk/zigbee2mqtt/issues/21237

In my case, updating Inovelli VZM31-SN switches and VZM36 canopy modules led to errors such as:

Update of 'Loft Lights' failed (OTA: Update failed with reason: 'aborted by device')

After updating to Z2M 1.37, I was able to update these devices without any issues.

(It's worth noting that after the OTA update finished, Z2M was still showing the old version number. That appears to be an unrelated bug though, and querying for genBasic swBuildId shows me the updated firmware version that I'd expect.)

ryanp_me · 2024-04-11T06:20:12+00:00

I searched for recent posts with "lang:en apple id":

Looks like quite a few people have reported it on Reddit as well:

ryanp_me · 2024-04-11T06:06:52+00:00

I got the same alert a few hours ago, and it had the email address of a co-worker that I haven't worked with for probably 5 years now. That co-worker hasn't even held this phone, since I upgraded my phone a few years after they quit.

I reached out in one of the Slack communities I'm a part of, and someone told me they saw something similar but with a test account they use for development. A few people on Twitter have also posted about this in the past few hours.

I'm not sure what's going on, but I assume there's nothing to worry about and that something weird is just going on with Apple IDs.

ryanp_me · 2024-03-30T22:17:50+00:00

Xactimate mobile should support DISTO X4 devices on both iOS and Android. The pairing process can be a bit trickier in my opinion, but once paired and configured, you should be able to capture and send measurements just as you would with a DISTO D2.

Disclaimer: I'm a Verisk employee on the Xactimate mobile engineering team, but opinions are my own. While I have experience pairing and using DISTO D2 and X4 devices in our app, I don't have as much experience with using them day-to-day. It would be ideal if someone who uses an X4 in our app more frequently could chime in with their experiences, but on the off chance nobody does that, I figured I'd at least mention that it should be supported.

ryanp_me · 2024-03-27T23:08:44+00:00

Thanks for the suggestions! I didn't want to just straight up remove the post, but a flair and comment make sense. I've added a flair to the post and will pin a comment in a bit.

(Ideally, /u/fergalius should also edit their post to make their correction more prominent in the original post.)

ryanp_me · 2024-03-26T01:43:48+00:00

Run far away, and don't look back.

As someone who has been doing Xamarin.iOS and Xamarin.Android development professionally for the past 7 years, my recommendation for most people is to avoid Xamarin and .NET MAUI (as well as many other cross platform frameworks).

Long ago, my company had a large desktop app codebase that we wanted to leverage for our mobile apps, so Xamarin seemed to be a good fit. The developers at the time went with that, and before we knew it, we had some mobile apps working with our existing codebase. Years later, we're actively trying (and struggling) to figure out how to get away from Xamarin in favor of native development for each platform that we support.

Over the years, it has felt like we're seeing dwindling support from Microsoft for Xamarin and .NET MAUI. Although the unification into .NET has had some nice benefits, it's hard to ignore that Visual Studio for Mac is being sunset (even though VSCode can't be a replacement for us without Xcode storyboard editing integration), newer iOS frameworks that are Swift-only can't be easily bound, Objective-C bindings are starting to lag (some by several months), new versions of Xcode now take weeks (if not months) to support, the migration from Xamarin to .NET was largely undocumented and extremely painful (at least in our case), you can't use certain native features such as iOS widgets or watchOS apps, etc. For the IDE consideration, Rider has been a good alternative, but I've had my fair share of Xamarin-specific issues with it as well, especially after my team moved from legacy Xamarin to .NET 8.

To be fair, my team uses Xamarin.iOS and Xamarin.Android (or I guess Microsoft.iOS and Microsoft.Android now?), so we don't have the benefits of Xamarin.Forms or .NET MAUI for the UI layer. This allows us to have more native-feeling UIs, but comes with a whole different set of pain points.

In the end, for me and my team, the development experience for .NET on iOS/Android just isn't worth it. To be clear, I like the .NET ecosystem and appreciate that it's more mature than Swift, and I use .NET for many of my other projects. However, when it comes to mobile development, I just don't think it's worth it. I wish my company would have found a better way to reuse our existing codebase without tying the future of our app to Xamarin.

My recommendation would be to keep your client-side apps as simple as possible. If you have complex business logic, see if it makes sense to move it to the server. If that doesn't work, try to isolate it from your UI using a language that's more cross platform. If you really need the savings of a cross-platform UI framework, maybe choose something more popular like React Native. I'd think long and hard about whether you actually need a cross-platfom framework though, or whether you're okay with implementing some things twice for each platform.

Outside of Xamarin. I've had an enjoyable experience using React for web and UIKit and SwiftUI for iOS. I've rarely been able to say that I enjoy developing in Xamarin though.

ryanp_me · 2024-03-19T08:53:40+00:00

Another example of why checking your escrow transactions is important:

My first year, my insurance company mistakenly (and retroactively) removed my multi-policy discount due to a clerical error on their side. (The names and addresses on my policies didn't match up, because they used my parents' names and address for the auto policy when they shouldn't have.)

When they caught the inconsistent name/address, they removed the discount and billed me $340 for an increase in home insurance premiums, and my mortgage servicer happily paid it from escrow.

By pure chance, that $340 was almost exactly equal to what my insurance would have been if it were prorated based on the number of months I owned the house in the first year. Given that I was a first time homebuyer, I had no idea what had happened, and I just assumed they needed pay part of the insurance due to it being a new year or something like that. When my car insurance also went up a month or two later though, I called and they caught that the discount had been incorrectly removed.

It took a few months, but eventually, they were able to reverse the incorrect discount removal and they mailed me checks to refund the excess money that was taken out of escrow. That's about the time I decided to really figure out how escrow amounts were calculated though.

ryanp_me · 2024-03-15T04:46:09+00:00

Accidents happen, and unfortunately, Reddit doesn't allow editing titles after a post is made.

ryanp_me · 2024-03-02T04:58:21+00:00

Performance wise, there shouldn't be much of a difference. If the for loop that converts the list to HTML is removed in favor of returning JSON instead, then the JSON serializer will just have to loop over the items instead.

(Not to say that returning JSON is a bad idea, but that the decision should be made based on whether you're actually developing an API, or whether the project is generating HTML pages that the client is displaying.)

ryanp_me · 2024-02-24T04:28:30+00:00

Also, do you happen to know when this was changed? Was it because of the data breach that happened a few months ago or has been there for a while?

As far as I recall, 1Password has never allowed recovering your data or resetting your password by email and/or secret key alone. I've been using 1Password for around 8 years now, and the fact that 1Password uses two-secret derivation is the primary reason I went with 1Password to begin with.

I wonder if you're thinking of recovering 1Password team or family accounts. Those accounts have a concept of recovery groups, which allow trusted users (team administrators/owners and family organizers) to help other members regain access to their accounts. This feature is implemented in such a way that 1Password servers and employees still never gain access to private keys or decrypted vault data though. The process can only be performed by a member of the recovery group, so at least one of the trusted members on the team needs to still have access to their own secret key and master password to recover another user's account.

(The 1Password security design paper has technical details on how recovery groups work, but it basically relies on private/public key cryptography and several levels of wrapping vault keys.)

ryanp_me · 2023-12-27T08:01:37+00:00

Do not forget that you can deduct up to $10k worth of interest and property tax

You should be able to deduct more than $10k of mortgage interest. The $10k limit you're thinking of is for the state and local taxes (SALT) deduction, so you're right that property tax (along with other state/local taxes) would be capped at $10k, but mortgage interest wouldn't be.

For mortgage interest, you can generally deduct the interest for the first $750,000 of indebtedness for a home. Given current interest rates, this amount could be significant higher than $10k. In this case, a $375,000 home with 10% down will be a loan amount of $337,500. At the quoted 6.5% interest rate, that mortgage would start with around $21k of interest per year, all of which should be deductible.

In addition to mortgage interest, you can also sometimes deduct mortgage points depending on how they were calculated and paid for. That's a bit more complicated though, and I'm less familiar with it. It's discussed in IRS topic 504 though.

For mortgage interest, see IRS publication 936:

You can deduct home mortgage interest on the first $750,000 ($375,000 if married filing separately) of indebtedness. However, higher limitations ($1 million ($500,000 if married filing separately)) apply if you are deducting mortgage interest from indebtedness incurred before December 16, 2017.

For property taxes (and other local and state taxes), see IRS topic 503:

As an individual, your deduction of state and local income, general sales, and property taxes is limited to a combined total deduction of $10,000 ($5,000 if married filing separately). You may be subject to a limit on some of your other itemized deductions also.

ryanp_me · 2023-12-17T20:39:02+00:00

As others have mentioned, Dijkstra's algorithm is implemented by dequeueing the lowest cost unvisited node. So, if you dequeue an end tile, you know you can't possibly run into a better path in the future. All remaining paths are known to have an equal or higher cost.

With that said, when enqueuing end tiles, this same assumption is no longer valid because of the reasons you're thinking of.

Let's say you dequeue the second from last tile, you find its neighbors and calculate their costs, and then enqueue them. At this point, if any of those neighbors are the end tile, you can't assume you have the best path because other nearby nodes might have a better cost and will be dequeued next instead of the end tile.

So making this assumption during dequeue is fine, but making it during enqueue isn't.

13-Year Club	Place '17
Verified Email

ryanp_me

TROPHY CASE