Remote

ash furrow (still spooky)

@ashfurrow@tenforward.social

mastodon 4.6.6

Compassionate software developer focused on mobile UX.

Created mastodon.technology in 2017, shutdown in 2022.

Error: cycle detected: "Fredericton -> Toronto -> Amsterdam -> New York -> Fredericton"

🏳️‍🌈

2553 Followers

494 Following

22 Posts

Joined July 29, 2024

Blog:

https://ashfurrow.com

GitHub:

https://github.com/ashfurrow

pronouns:

he/him

launch codes:

--|-..|-.

Posts

ash furrow (still spooky) @ashfurrow@tenforward.social · Apr 24, 2026

Replying to @daniel@social.telemetrydeck.com

@daniel@social.telemetrydeck.com perfect, this was part of our mitigation, so thanks!

ash furrow (still spooky) @ashfurrow@tenforward.social · Apr 24, 2026

@harshil@mastodon.social “Captain, I’m on call.” 😭

mastodon.social

Harshil Shah :psyduck: (@harshil@mastodon.social) - Mastodon

ash furrow (still spooky) @ashfurrow@tenforward.social · Apr 24, 2026

Replying to @ashfurrow@tenforward.social

Switching to ISO8601DateFormatter resolved the bug (the differing behaviour I was seeing with plain DateFormatter). I never found a root cause of why it failed to parse the same dates on different users’ devices, which means I can’t guard against the bug except by avoiding DateFormatter. Thanks to everyone who responded!

ash furrow (still spooky) @ashfurrow@tenforward.social · Apr 24, 2026

Replying to @designatednerd@mastodon.social

@designatednerd@mastodon.social I am now, but I was hoping to confirm this behaviour difference with others while waiting for App Store review. I should follow up, since, it did fix the bug 🎉

ash furrow (still spooky) @ashfurrow@tenforward.social · Apr 21, 2026

Replying to @stevestreza@indieweb.social

@stevestreza@indieweb.social @brunoph@breakpoint.cafe still helpful to know this sounds familiar :) thanks

ash furrow (still spooky) @ashfurrow@tenforward.social · Apr 21, 2026

Replying to @brunoph@breakpoint.cafe

@brunoph@breakpoint.cafe this is helpful confirmation, thank you 🙇‍♂️

ash furrow (still spooky) @ashfurrow@tenforward.social · Apr 21, 2026

Replying to @brunoph@breakpoint.cafe

@brunoph@breakpoint.cafe that does help, thank you. does this fix look familiar? using an ISO8601DateFormatter specifically. formatOptions = [.withInternetDateTime, .withFractionalSeconds] // try to parse formatOptions = [.withInternetDateTime] // try to parse again

ash furrow (still spooky) @ashfurrow@tenforward.social · Apr 21, 2026

This is a long shot, but...

Has anyone seen an issue where a Swift DateFormatter will *mostly* correctly parses dates with the wrong number of milliseconds, but won't under specific device configurations?

I have a date formatter with "yyyy'-'MM'-'dd'T'HH:mm:ss.SSSZ" as its format string (which expects three millisecond digits). iOS will correctly parse a date string with only two digits, eg "2026-04-21T19:29:15.11Z", which, that's fine. But I have reports of an intermittent error in parsing dates, and they all have only two millisecond digits. So I'm wondering if there is some combination of locale/date settings that cause this to fail.

Does this ring a bell to anyone?

ash furrow (still spooky) @ashfurrow@tenforward.social · Apr 12, 2026

Replying to @ashfurrow@tenforward.social

COMBINE:

1/3 measures Daniel Jackson being invited by vaguely a European woman to prove the unorthodox theories that ruined his career.
1/3 measures John Crichton making pop culture references to puppet aliens as he struggles to hold onto sanity.
1/3 measures Deep Impact “extinction level event” international coalition rising-to-the-challenge, with focus on interpersonal relationships.

Shake (optionally: shake camera). Garnish with budget.

YIELDS: one excellent sci-fi movie.

ash furrow (still spooky) @ashfurrow@tenforward.social · Apr 12, 2026

Ben Browder stumbled+flailed so that Ryan Gosling could stumble+flail with a big budget

ash furrow (still spooky) @ashfurrow@tenforward.social · Apr 03, 2026

Replying to @jacob@social.jacobian.org

@jacob@social.jacobian.org yeah, exactly. Lots of AI coding boosters are talking about the importance of tests, documentation, small modules… On one hand, yes! Great ideas! OTOH why did we have to wait for LLMs to prioritize this? (And as soon as we can avoid it, will we?) But, I do like the move to smaller PRs, smaller files, more tests. My biggest challenge is that PR review has become a bigger bottleneck.