sarvind

They are losing a whole lot of valuable sales through this channel, not to mention seeing a higher than average return/refund rate that could flag some risk alerts. So there's plenty of incentive to fix it - although this sort of thing could presumably be pretty hard for them to detect, troubleshoot and rectify.

I suspect this comment is aimed at segments like this one with Ted Nelson of Hypertext fame: https://www.youtube.com/watch?v=Bqx6li5dbEY

On first viewing, I too felt it was incomprehensible wordsoup in some sense - but upon learning more about Nelson and the history and context around which his ideas were developed, I've grown to find this interview almost magical.

It's not like words cannot be overloaded. Lots of languages use the plural form to show respect or politeness, or regard somebody with esteem (like the royal "we") for instance.

You were uncomfortable with textbooks when they used 'she', and against them trying to include you once more with 'they/them'?

So the only acceptable option by this line of thinking is that the default pronoun should be 'he/him'. This attitude seems something a little different from 'conservative'.

You require AWS to at least activate and set up DeepRacer [0].

You don't strictly speaking need the cloud for training a DeepRacer model, although cloud access (via the DeepRacer console) could be the path of least friction.

Much of the source code for training DeepRacer on AWS can be found on the amazon-sagemaker-examples github repo [1].

The sample training environment relies on Gazebo [2] which, while freely available, has a managed AWS offering [3]. But ultimately, you should just be able to deploy an RL Coach model to the device [4].

[0] https://docs.aws.amazon.com/deepracer/latest/developerguide/...

[1] https://github.com/awslabs/amazon-sagemaker-examples/tree/ma...

[2] http://gazebosim.org/

[3] https://docs.aws.amazon.com/robomaker/latest/dg/simulation-t...

[4] https://docs.aws.amazon.com/deepracer/latest/developerguide/...

The models should be limited to within the confines of the s3 location you specify (and the physical deepracer device) unless you explicitly permit otherwise. Nothing that I see in the terms of use [0] cover access to the model.

[0] https://aws.amazon.com/deepracer/device-terms-of-use/

The blog post [1] provides additional insights that imply it can work well clients despite its ephemerality, and is optimized for client connection pools.

"Scaling operations are transparent to the connected clients and applications since existing connections and session state are transferred to the new nodes."

As for the public subnet concern, you can apply security groups to your database instance to ensure only authorized CIDR ranges can call it. Additionally, you can use IAM authentication [2] for DB callers (only recommended for light-weight applications with low concurrency),

[1] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Using...

[2] https://aws.amazon.com/blogs/aws/aurora-serverless-ga