Last week we noticed that mailgun has lot of mail bounces from outlook mail address, because the mail delivery IP had been blocked. Usually mailgun fixes these issues automatically, but the issue was not solved after several days, so we asked them to change the IP. They refuced to do it because our bounce rate was high. This was a given as mailgun was mainly used to confirm valid mail address.
To fix it one option is to deliver mail by ourself, but since our server is IPv6 only, this won't work.
Second option is get our bounced rate back down by adding a notice in the registration page and making the backend validation more tougher. Which we took this option and while some users used a tempary email address(which is okay) some users were still adding non-existing email address.
To combact it, now we will send confirmation email by checking out the email address manually. This will take upto 24 hours. Also the upload page has been enabled to all users, so they can upload images wit…
Open it and extract to anywhere you like, and run the exe file.
Refresh the desktop and click on BeeIMG icon If there is a rundll error ignore it
Use the contact form and select Request API key from the dropdown menu and ask for a API key Set the API key you have to set it everytime you open the app Use the button the select files to upload The image URL will be on the text form below
We faced some blackouts recently, and it was because we got very popular in china.
The images that was generating lot of traffic were violating our TOS, but as they were generating lot of traffic and I thought it was a good time to stress test our image delivery systems.
At first we were handling the load fine. after some time our redis server start acting wired. the issue was with dumping the db to disk, but as the images were generating lot of data the redis server crashed. we started to migrate the all gif images to be served by our CDN while still collecting views data. but at some point our real time stats handling script started to fail due to redis connection issues. after that the data started to collect and the redis server crashed every time it was started.
While all that was happening we noticed that our php front end started throwing errors. this was due the connectivity issues to our redis server.
The image serving end do not use redis server and was not afflicted. its using …