(Relevantly to my tweet earlier today: this is the last quarter miles for file-shaped data. After it's in the cloud and being operated on by competent engineering teams that know what they're doing life is grand but getting it from an arbitrary freaking phone aaaaaaaagh.)
-
-
Show this thread
-
(Do you sense a bit of frustration about this issue? Here's why: a) I have just spent 3 weeks attempting to upload e.g. iPhone photos of my ID to Japanese financial firms to satisfy KYC requirements b) I once implemented "Oh just drag an Excel/CSV file here" SCARS.)
Show this thread -
In one case, I kid you not, technical difficulties required me to: 1) Take a photo of my ID. 2) Dropbox the photo to my computer. 3) *Edit the photo.*, apparently because of lighting conditions. 4) Download a blessed image upload app from the bank. 5) Take a photo of MBP screen.
Show this thread -
"Wait what!?" They needed to OCR my "My Number" (個人番号; think of it like Japanese SSN) off my ID card and apparently lighting in my apartment wasn't playing nicely so I got to blackbox and improve their file upload pipeline for them. "Wait, WHAT?" File uploads. They suck.
Show this thread -
"Why do they need an upload of your card to grab a 9 digit number?" Because there will come a time in the future when a Very Serious Professional asks them to show that they have an appropriate level of controls for the data quality of ~300,000 similarly collected numbers.
Show this thread
End of conversation
New conversation -
-
-
because backend?
-
Character limits are hard. You want to be able to consume file uploads as infrastructure from a program written in ~anything but OSSing them requires you to run and administer (monitor, update, etc) some backend service, which minimizes the utility of the OSS frontend.
End of conversation
New conversation -
-
-
"How hard could it be?" I ask myself then spend 6 months implementing it poorly.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
There sort of is an open source solution https://uppy.io/ . Yeah, you still handle backend, but I'm not convinced that's a lot of trouble. Client-side resizing etc. is definitely handy, but on slow devices...ouch.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
There’s already a startup for that. https://www.filestack.com
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.