Surely I'm not the only one who thinks this is ridiculous. People are recommending a third party program with a shithouse duck icon and interface from 2007 just to let me drag and drop files. I'm unreasonably irritated because I've spent time I don't have researching and signing up for this shit, only to find there's a barrier to entry just to use the fucking thing. But I'm also busy and need a cloud storage solution for my work and personal files with very little time to spare.
I'm not trying to type code whenever I upload files for Christ sake. I don't understand if this is supreme arrogance, absolutely razor thin profit margins, or computer nerds living in a complete bubble but why the fuck would any regular ass person want to use a program that has a learning curve for new users. I don't understand if I'm missing something or what but this guy starts fiddling with a bunch of garbage to get the thing to run and then demonstrates some commands. aiob2 - A Modern and Pythonic API Wrapper for Backblazes API. Find some jamoke on YouTube giving a tutorial and can I just say what the fuck. Open it and it's lines of code that just close immediately. Find a link to something called a command line.
Decide to make an account and start putting some files in. It works well for what its intended to do. So the inability to set a specific file name, file size limit and expiry date is preventing some of us from switching over from S3 to Backblaze for our storage of app data needs.I've been looking into cloud storage for a while and have seen backblaze recommended a bunch. Backblaze Personal is simply a backup, not a file sync program. I ended up just going back to S3 - costs more, but still worth it. All sorts of bad things could come of that. I didn't want the generation of a signed url to, say, upload a profile photo, give carte blanche to create a hidden image host when combined with the limitation that you highlighted. I had the exact use case you mentioned, too - image uploads bypassing my backend server. I ran into the same limitation! IIRC, there also wasn't a way to expire a signed upload URL sooner than whatever the default was, which was hours or maybe a day. This pretty much prevents me from using B2 for now. Next thing you know, you have a 5gb sized image uploads happening. So if you are using b2 for storage for lets say image uploads from browser, some malicious user has the ability to modify the network request with whatever file name or file size they want. It simply gives you a url to upload it to. This same limitation is faced by someone else too who replied to my comment:Ī limitation I ran across when using B2 was that their pre-defined url generation doesn't allow you to set file-size limits nor does it allow you to set the file name in the pre-defined url. I made 2 separate posts regarding this previously which B2 staff replied to:
0 kommentar(er)
