Możesz dodawać lokalizację do Twoich Tweetów, jak miasto czy konkretne miejsce, z sieci lub innych aplikacji. W każdej chwili możesz usunąć historię lokalizacji swoich Tweetów. Dowiedz się więcej
One thing I really underestimated with @thankbox is the amount of storage I'd need for user-uploaded images. I thought most people would choose gifs over uploding their own but I was wrong.
I'm going to run against the Cloudinary limits real soon. I need an alternative.pic.twitter.com/8j85vzUoKc
I've been thinking about either rolling my own AWS S3 solution or doing a mix between Cloudinary and S3. I really like Cloudinary and would definitely find it useful when I add video support to messages. But I cannot store media there long term, it makes no financial sense.
Basically, a week or so once a Thankbox is sent, all the images in it are not likely going to be seen again. Or if they are, it won't be often. So my thoughts are, at that point, I move the media from Cloudinary into S3. At one resolution.
I'd lose the transformation capabilities of cloudinary and loading images at just the right size for different screens(increasing bandwidth for users) but if it's after a Thankbox has been sent and seen by the recipient, does anyone care?
The other option is just ditching cloudinary and going full on S3 and doing my own (basic) image transformations in a Lambda or something. Might be the long term solution but sounds very time consuming at this stage.
In any case, I need a solution - and relatively quickly. Appreciate any tips from people who have dealt with this before.
I'd go for a simple solution as a start using S3 and Lambda.https://aws.amazon.com/solutions/implementations/serverless-image-handler/ …
Twitter jest przeciążony lub wystąpił chwilowy problem. Spróbuj ponownie lub sprawdź status Twittera, aby uzyskać więcej informacji.
