josephfrazier Github contribution chart
josephfrazier Github Stats
josephfrazier Most Used Languages

Activity

28 Sep 2022

Josephfrazier

Brewfile: Install Zoom cask

Pushed On 28 Sep 2022 at 07:26:14

Josephfrazier

.bash_profile: Set PATH, MANPATH, etc., for Homebrew

Pushed On 28 Sep 2022 at 07:21:30

Josephfrazier

Install and use git-credential-manager-core, see https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token

Pushed On 28 Sep 2022 at 07:21:30

Josephfrazier

Use openssl@3 with rbenv, update rbenv shell helper syntax

Pushed On 28 Sep 2022 at 07:21:30

Josephfrazier

Brewfile: Sort a couple entries

Pushed On 28 Sep 2022 at 07:21:30

Josephfrazier

Brewfile: Install docker-compose and md5sha1sum for Care/Of WMS

Pushed On 28 Sep 2022 at 07:21:30

Josephfrazier

Brewfile: Install readline

Pushed On 28 Sep 2022 at 07:21:30

Josephfrazier

Brewfile: add restart_service: true to postgresql@14

Pushed On 28 Sep 2022 at 07:21:30

Josephfrazier

Remove .Brewfile, update Brewfile with brew bundle dump

Pushed On 28 Sep 2022 at 05:37:27

Josephfrazier

`Previous Submissions` UI needs pagination/filtering/searching

I got a couple bits of feedback at https://reportedcab.slack.com/archives/C9VNM3DL4/p1663680269461029:

  • List of complaints is hard to scroll through. Some month/year filters would be useful

Stuff that I think could be cool if we invested in the mobile apps though:

  • Really fast search so I can quickly find the report with details when the prosecutor calls me 6 months later

So far, my response is:

I definitely agree here! Having pagination/filtering of some sort would certainly be helpful, especially for those of us with a large number of previous submissions, which can make the API/UI slower when loaded

Forked On 26 Sep 2022 at 10:09:53

Josephfrazier

For reference, here's the backend API the webapp currently uses to get submissions: https://parseplatform.org/

Commented On 26 Sep 2022 at 10:09:53

Josephfrazier

Prevent iOS zoom on map address field by increasing font size (#381)

See https://reportedcab.slack.com/archives/C9VNM3DL4/p1663676505708239:

From User1 at https://reportedcab.slack.com/archives/C7Z0BHMMY/p1663108832158739?thread_ts=1663092819.678649&cid=C7Z0BHMMY:

Setting a location is awkward because of the size of the map pane on the screen/scrolling issues.

EDIT:

adding some feedback from User2 at https://reportedcab.slack.com/archives/C7Z0BHMMY/p1663547627566829?thread_ts=1663092819.678649&cid=C7Z0BHMMY since its discussing the same issue:

Also agree with User1 that the map is currently one of the most frustrating parts. I put in an intersection, then need to scroll down in just the right part of the screen to get to the Done button; otherwise, I lose the intersection I just entered.

User1: The issue seems to stem from iOS zooming in on the webpage when I click into the address field to type. It doesn't zoom out after I click out of the field or dismiss the keyboard.

User1: Apparently iOS will only zoom in when you tap a text field if the text size is < 16px. You could try adjusting it and seeing if that helps? https://stackoverflow.com/a/6394497

Pushed On 24 Sep 2022 at 07:51:10

Josephfrazier

Prevent iOS zoom on map address field by increasing font size

Created On 24 Sep 2022 at 07:51:09

Josephfrazier

Prevent iOS zoom on map address field by increasing font size

Created On 24 Sep 2022 at 07:48:37
Create Branch
Josephfrazier In josephfrazier/Reported-Web Create Branchios.address.zoom

Josephfrazier

Web front-end for https://twitter.com/Reported_NYC: https://reported-web.fly.dev/ or https://reported-web.herokuapp.com

On 24 Sep 2022 at 07:48:33

Josephfrazier

Use heroku/builder:22 for Fly deployment (#380)

See https://github.com/josephfrazier/Reported-Web/actions/runs/3119316697/jobs/5059203575 and https://github.com/heroku/builder/tree/fc79c502cf8a8650b6fac34b3a266a40cb1970ba

Pushed On 24 Sep 2022 at 07:08:10

Josephfrazier

Use heroku/builder:22 for Fly deployment

Created On 24 Sep 2022 at 07:08:10

Josephfrazier

Use heroku/builder:22 for Fly deployment

Created On 24 Sep 2022 at 07:05:04
Create Branch
Josephfrazier In josephfrazier/Reported-Web Create Branchfly.heroku.stack.22

Josephfrazier

Web front-end for https://twitter.com/Reported_NYC: https://reported-web.fly.dev/ or https://reported-web.herokuapp.com

On 24 Sep 2022 at 07:04:58

Josephfrazier

Show whether location came from device, photo, or manually setting via map (#379)

See feedback at https://reportedcab.slack.com/archives/C9VNM3DL4/p1663676341717829:

User:

It isn’t clear if it’s pulling location from my current location or the photo.

Me:

Good point, the user feedback here is pretty minimal/non-existent. For what it's worth, when you first open the site, it tries to get your current location, but once you upload photos, it tries to pull location from the photo, and lets you know if any photos did not have the necessary GPS metadata.

Maybe one way to make this more obvious to users would be to add a note by the address field indicating if it was pulled from the device's current location, or if it was pulled from a photo, or if it was set manually.

What do you think?

Pushed On 24 Sep 2022 at 07:04:21

Josephfrazier

Show whether location came from device, photo, or manually setting via map

Created On 24 Sep 2022 at 07:04:21

Josephfrazier

Show whether location came from device, photo, or manually setting via map

Created On 24 Sep 2022 at 06:56:12
Create Branch
Josephfrazier In josephfrazier/Reported-Web Create Branchaddress.provenance

Josephfrazier

Web front-end for https://twitter.com/Reported_NYC: https://reported-web.fly.dev/ or https://reported-web.herokuapp.com

On 24 Sep 2022 at 06:56:09

Josephfrazier

Upgrade heroku stack to 22, see https://devcenter.heroku.com/articles/heroku-22-stack (#378)

I'm hoping this may make HEIC/HEIF file handling a bit easier and less prone to run out of memory (OOM), but even if it doesn't probably best to stay up to date regardless.

Pushed On 24 Sep 2022 at 06:23:10

Josephfrazier

Upgrade heroku stack to 22, see https://devcenter.heroku.com/articles/heroku-22-stack

Created On 24 Sep 2022 at 06:23:10

Josephfrazier

Upgrade heroku stack to 22, see https://devcenter.heroku.com/articles/heroku-22-stack

Created On 24 Sep 2022 at 06:04:05
Create Branch
Josephfrazier In josephfrazier/Reported-Web Create Branchheroku.stack.22

Josephfrazier

Web front-end for https://twitter.com/Reported_NYC: https://reported-web.fly.dev/ or https://reported-web.herokuapp.com

On 24 Sep 2022 at 06:04:03

Josephfrazier

Add checkbox to toggle ALPR (platerecognizer) (#376)

See comments at https://reportedcab.slack.com/archives/C9VNM3DL4/p1663877313263879:

User Joseph Frazier how would you feel about making plate reading optional (if checkbox is unchecked you just skip it)? It's connection speed dependent and on slow connections it takes forever

Joseph Frazier Ooh, that's an interesting thought! I bet it might not be too hard to implement. I am curious though, does the automatic plate reading interfere with making submissions on a slow connection? I don't think it should, but if it does, I'd like to think about how to fix that

Joseph Frazier Like, I think you should be able to make a submission even if the plate reading is slow, without it stepping on your toes when you type the plate manually

User Yes, what happens is:

User I upload the photos I anticipate the plate reading will fail because the plate is tiny or whatever I type in the plate number myself I check the location and date I hit submit Uploading begins Some time later, I get the “plate couldn’t be read” modal (which requires me to click OK), which may or may not cancel the submission and make me start it again

User I haven’t been able to figure out why it sometimes does or doesn’t

User It just happened to me with a one-photo submission — I am on a very slow connection (0.5Mbps up)

User I hit submit, then came to this window, read your reply at the top of this thread, and typed all this up through “does or doesn’t”

User Then I got the “plate read failed”

User This time it did not cancel my upload that was underway, it was at about 90% by then

User But even when plate reading works, on large photos it takes a long time (very often 10 seconds for the first one and longer for subsequent ones)

User Even on normal connections

User My flow would be faster (and less annoying) if i just turned it off

User Because I can type the plate number in about 8 seconds

User Including reading it off the photo with my eyes

User Just had a lookup (on a super-slow connection) that took 9 minutes for photo 1 (of 2) to return failure

User By then the submission upload was about 60% complete

Joseph Frazier Oh, I see now, thanks for explaining how the plate reading and the submitting relate to each other, at least in the UI. For what it's worth, I don't think the plate reading should interfere with the submisison going through, even if the error messaging is confusing. Nevertheless, I don't think a checkbox would be hard to add, so I'm going to take a look

and https://reportedcab.slack.com/archives/C9VNM3DL4/p1664039707876189?thread_ts=1663679460.688329&cid=C9VNM3DL4, from a different user:

As it is, I feel like honestly the license plate OCR is more painful than it is useful. I submit a lot of complaints, and it probably only works correctly 40-50% of the time. Wondering if we should just turn it off until we can improve it?

Pushed On 24 Sep 2022 at 05:41:29

Josephfrazier

Add checkbox to toggle ALPR (platerecognizer)

Created On 24 Sep 2022 at 05:41:28

Josephfrazier

Update snapshots with yarn test -u (#377)

Pushed On 24 Sep 2022 at 05:38:56

Josephfrazier

Merge branch 'main' into ocr.checkbox

Pushed On 24 Sep 2022 at 05:38:56