230 karma · joined May 16, 2020
> Models
> We are offering three models:
> FLUX.1 [pro] the base model, available via API
> FLUX.1 [dev] guidance-distilled variant
> FLUX.1 [schnell] guidance and step-distilled variant
First try:
I think there is a logical inconsistency in the text. If Joe drove Sue to university, then she was dropped off at the university, which means she would not be available to drink tea with him at his home afterwards. The sequence of events seems to be out of order.
Second try: I notice that there's a small issue with the sequence of events. It seems unlikely that Joe drove home again after dropping Sue off at university, only to then drink tea with her in the kitchen. If Joe drove Sue to university, it implies she got out of the car at the university, not that he drove back home with her.
A more logical sequence of events would be:
Joe drove Sue to university. Afterwards, he drove home and drank a cup of tea by himself in the kitchen.
Or, if you want to keep the scenario where Joe drinks tea with Sue:
Joe drove Sue to university. They went back home together, and then they drank a cup of tea together in the kitchen.So is your API key baked into the app? Implement a login screen or a field for the API key and then who cares if Google has a copy of your app, they can't access your data.
How do you like Pulumi? It seems similar to AWS CDK...
Things I would do differently are using NixOS or bootable containers (CentOS) (side note, bootable NixOS container would be a killer app) and writing my own helm charts instead of fully customizing my manifests and doing the deployments from ansible, and would recommend against Raspberry Pis for the compute as the 3's and 4's don't support limits, e.g. cpu or ram limits, and I wasn't able to set up firecracker containers correctly on the Pis.
I'm also exploring hyperconvergence infrastructure (HCI) as that seems more like my ultimate goal for homelab stuff.