I now open up waterfox on those occasions when I need to use fireftp.
I'll definitely give this a try out if it can do the job instead
51–60 of 82 posts
I now open up waterfox on those occasions when I need to use fireftp.
I'll definitely give this a try out if it can do the job instead
One of the developers here. We worked three years to make Uppy the best open source file uploader the world has seen. Looking forward to your brutally honest feedback! Happy to answer questions too.
One of the developers here. We worked three years to make Uppy the best open source file uploader the world has seen. Looking forward to your brutally honest feedback! Happy to answer questions too.
I know it's not your responsibility at all but the only thing that stopped me from using it was the pain in the ass that is configuring s3 itself. I will get to it eventually cause I'm not very happy with filestack's UI but it was so quick to get it working and I was in a hurry.
If you want to save money then yes, you could configure direct S3 uploading with Uppy, we do have better examples fot that these days (e.g. we now also show back-end code for signing the requests)
However it seems you got it working now so maybe no reason to change?
Has anyone switched to/from Uploadcare? ( https://uploadcare.com/ ) - would love to hear how they compare.
Some differences between the uploader widgets themselves:
- Uppy is open source and can be used with your own back-end. Free as in liberty & pizza
- Uppy is vanilla JS with support for React/Native
- Uppy has resumability (via the open standard https://tus.io) and can recover from browser crashes / accidental navigate-aways. Uploads will just continue where they broke off
- Uppy supports _less_ external sources (e.g. 1.0 comes with support for Dropbox, Instagram, Google Drive, but we don't yet have support for e.g. Facebook, or Google Photos)
Some differences between the companies/back-ends (should you optionally use Uppy+Transloadit to handle the uploading, fetching from e.g. Instagram, and encoding):
- Transloadit offers more encoding features (Uploadcare is making good progress tho, they recently added video encoding for instance). Those features can be combined in workflows. So you leave a JSON recipe ("Template") with us that says: for every video, take out thumbnails, watermark some of those, detect faces in others, store those separately, all in one 'job', or how we like to call it: "Assembly"; because it can be a chain of virtually infinite jobs that take the output of other jobs as input for their own
- Transloadit does _not_ offer a CDN, instead only exports results to storage/buckets you own (not sure if we'll add this)
Just a _few_ differences, there are more. But it seems they are getting fewer and maybe in 5 years we'll be identical companies : ) but yeah so there's some time left until then that we can still afford pleasantries :D
One of the developers here. We worked three years to make Uppy the best open source file uploader the world has seen. Looking forward to your brutally honest feedback! Happy to answer questions too.
I see there's ability to upload directly to S3, any ability to upload direct to Azure Blob store?
Does this have an API for repeatable scripted uploads?
Not entirely sure if I read your question right, but Uppy does have a scriptable API so that you could do uploads without bringing in all the UI yes. So you could write your own UI, or have some kind of automation in place. But maybe you're talking about something else? Happy to dive in deeper
It would be nice if this can function as a point and click upload point and also a scriptable upload point for savvier users.