Dusty Pomerleau
banner
dpom.bsky.social
Dusty Pomerleau
@dpom.bsky.social
Web hobbyist • Leptos, Axum, Gel

(he/him)
I no longer recall the exact mistake, but I think it was something like an if/else where I thought the if should always hold, but the compiler viewed any entry into that block of control flow as reaching both arms.
November 7, 2025 at 10:01 AM
November 7, 2025 at 9:52 AM
Is that condensation, or is your L1 cache weeping because of this post?
November 6, 2025 at 10:09 AM
I compose the entire thing in an editor I trust, and then paste that into the text box, because then an unwanted reload can't steal everything. I've had massive forms wiped out just because I changed the country while entering an address in the last step.
November 5, 2025 at 12:23 AM
Settings > General > iPhone Storage

should tell you who the culprit is, no?
November 4, 2025 at 7:50 AM
Thanks (as always)! I actually didn't realize that rustc could guarantee immutability of *const T. i thought with raw pointers all bets were off.
November 1, 2025 at 9:30 AM
I have no experience with unsafe, but why do they need to cast into 2 different raw pointers in a row?
November 1, 2025 at 8:53 AM
My situation was a transactional email client held in global state, whose send method was async, but I realized that I could invoke the send without mutable access, so I ended up putting it in a plain Arc. Perhaps that further proves your point :)
November 1, 2025 at 8:34 AM
So if clippy gives that warning, do you just ignore it? Or do you have something else you use other than a tokio mutex?
November 1, 2025 at 1:21 AM
It's funny, because I had never used a tokio mutex, and then I finally had a situation where clippy barked at me for holding the lock across an await, so I switched to using the tokio mutex—and then an hour later I watched @sunshowers.io's cancellation talk, where they said to avoid tokio mutexes :)
November 1, 2025 at 12:40 AM
Reposted by Dusty Pomerleau
a bigger snapshot to take it in better:
October 30, 2025 at 8:57 AM
It's true - the contract can't always be enforced if someone challenges it and the terms are ruled not to be legal in the first place. When it comes to VPNs, these platforms are mostly just protecting themselves against lawsuits by the copyright holders.
October 30, 2025 at 7:52 AM
Platforms are forced to put this in their terms, because they only have a license to distribute the content for certain Service Areas. It's terrible UX, and people find ways around it, of course, but if the question is legality I think it's pretty clear cut.
October 30, 2025 at 6:45 AM
From a legal standpoint, what matters is the terms of service you agreed to when creating an account. For example, HBO Max defines a Service Area for your account, and the Terms of Use explicitly state: "You may access the Platform only within the Service Area."
October 30, 2025 at 6:45 AM