blagadariu Profile Banner
blagadariu Profile
blagadariu

@blagadariu_

17,385
Followers
16
Following
1
Media
14
Statuses

CTO at @Playpixiz

Joined April 2019
Don't wanna be here? Send us removal request.
Pinned Tweet
@blagadariu_
blagadariu
16 days
Online version in progress at @playpixiz ? 👀🧑‍💻
294
563
969
@blagadariu_
blagadariu
13 days
🧵 [THREAD] The disasters we faced and how we overcame them since the beginning of Playpixiz. I will reveal to you everything that happened behind the scenes 👇 P.S: Feel free to ask me anything below! $PIXIZ
8
4
21
@blagadariu_
blagadariu
13 days
Finally, I want to thank you all for your trust and involvement in the project, we wouldn't exists without you 🤩 I also want to thank the entire @playpixiz team who work very (very) hard every day 🙏 Remember: you're the best 🫵
1
3
6
@blagadariu_
blagadariu
13 days
🗣️ Throughout all this, we faced a lot of FUD from detractors, despite ALWAYS delivering on our promises. It’s tough, but it’s part of the journey, especially when you get this amount of visibility from the public.
1
0
4
@blagadariu_
blagadariu
13 days
🌐 Next hurdle: Our registrar suspended our domain for alleged phishing/scam activities. We store no personal info from our users. The support was unhelpful, claiming we were a scam based on “reliable sources” they wouldn’t disclose. In short, they stole our domain name and
2
0
4
@blagadariu_
blagadariu
13 days
🔒 Next: Metamask and other wallets flagged us as a scam/phishing site. This was likely due to our detractors. Users were warned our site was dangerous (it's not). We engaged in long conversations with these networks to get whitelisted and clear our name.
1
0
3
@blagadariu_
blagadariu
13 days
🚀 Solution: We acted fast. Moved to @cloudflare registrar, registered a new domain (playpixiz), changed our name across all networks, and migrated our entire infrastructure. Adapt and overcome. 🥷
1
0
3
@blagadariu_
blagadariu
13 days
💪 Solution: Persistence paid off. After numerous and long, time-consuming discussions, we got whitelisted from their blacklists. Always fight for what’s right, and never give up. ⚔️
1
0
3
@blagadariu_
blagadariu
13 days
💡 Solution: We remembered we had a replica. The cloud provider’s interface showed nothing, but by checking developer console requests, we found the IP of the read-only replica. We connected, made a dump, and restored data on a new instance quickly. Of course, we messaged them
1
0
2
@blagadariu_
blagadariu
13 days
🖥️ First disaster: One of our servers at our cloud provider burnt out. No notification, nothing on the site interface. We immediately paid a Gold support plan to fix the issue, but they told us we'd need to wait 2 days for a technician. Unacceptable with +100,000 users' data
2
0
2