But what is showing that message? Cyberduck?

Cyberduck downloading status dialog

It's a progress dialog showing up while downloading.

That seems like a bug in Cyberduck 😅

it keeps downloading forever 😐

now I'm redownloading via aws cli.

I've stopped using Cyberduck, I'm using S3 Browser. I was uploading large zips and VMDKs, and Cyberduck would either fail, or appear to successfully complete but then files would be partially uploaded, corrupt, or otherwise junk. When I was deleting files with Cyberduck, they'd remain a phantom files and I'd have to manually delete them using the s3cli. Haven't had any issues with S3 Browser since 👍🏻 Edit: my bad, I thought S3 Browser had a Mac client.

confirmed. download normally with aws cli

Yeah I saw similar things with cyberduck sadly. I went back to the free edition of Cloudberry Explorer for easy gui access to r2

I couldn't help for di database

what do you think is (generally speaking) the best way of streaming a 3gb video from a s3 bucket (like r2)?

through a public bucket using hls is probably pretty decent cuz that way u can cache the chunks too

I'm looking into moving a lot of data from Backblaze to R2 I saw in the past that it was recommended to limit concurrency when using rsync otherwise you would get errors...is that still necessary?

Shouldnt be

Sounds good. Thanks!

is it possible to generate api tokens with permissions for only specific buckets?

without the use of workers, I'm using a .net api with S3

Not possible right now, but coming soon

I'm creating a multi-tenant website where users who sign up should only have access to a bucket associated with their account

oh ok

thx

I dont recommend giving them to users though

they're stored internally in our db

I see

one problem is youll hit the max of 50 api tokens pretty fast

oh shoot didn't know that was a thing

alright well guess I'm going with another route haha thanks

I guess now thinking about it, it makes more sense to just use a single api key from my backend and just check if a user has the proper authorization to make that specific call to a bucket

Yeah

I'm having trouble hosting a React app from R2. It worked fine in S3. Is there a technical reason/limitation causing it? Or do I just need to fine tune the configuration?