No chromecast support. I don't own a smart tv so my chromecast is the life of my living room TV.
It's kind annoying since I can only watch it on computer or tablet.
Yes, but I guess in that case you would put your lambda function behind an API gateway, and limit the user requests.
If it's a static content you would serve it from a CDN.
Not a specialist on this, but that's what I would do.
Wouldn't an API gateway typically limit requests per IP/end user?
I guess it could limit global request rate. But the idea of unbounded elastic services behind a global rate limiter is just funny to me. Like a Ferrari with a 50mph limiter.
Is it fraud if you declare a wrong birthday on your bank account? Don't they get that information from your documents, instead of relying on you to answer it?
It's nice to see how the backend of my favorite game works. Specially this article, right now I'm developing a chat service for a company and god I hate openfire.
My team also recently built a chat service into a mobile app for a cruise line, and had to have high resiliency to network drops and offline users - while having a mission-critical "guaranteed delivery" requirement. We also chose OpenFire since it was an off-the-shelf XMPP server, and (presumably) was easily extensibile via plugins.
After working with (hacking around) OpenFire for two years, I 100% agree with your statement. The clustering plugin routinely fails (to the point where we have actually investigated not even clustering it anymore), the admin interface routinely displays "wrong" data, and other fun bugs we found along the way.
Does it work for us (with a lot of client XEPs and additional custom plugins)? Yes, it does an acceptable job. Would I choose the same product again, if given the choice? No.
I just switched jobs because of my daughter. Left a job that I liked but didn't pay very well so I could stop having to work 2 shifts.
I'm a programmer btw. It drives me nuts everyday, but this keeps me going https://upload.wikimedia.org/wikipedia/en/thumb/a/ab/Simpson...