The oil price is too low. Venezuela and now this, it is all part of selling fossil fuels.
1,436 karma · joined December 16, 2013
The oil price is too low. Venezuela and now this, it is all part of selling fossil fuels.
I hope they release a good root cause analysis report.
OpenAI is receiving far more data with a far greater privacy impact than social networks. And all this is happening at a time when the US is transitioning from a somewhat functioning democracy to an autocratic and fascist system.
https://www.rollingstone.com/culture/culture-news/chatgpt-pa...
What's more important is trust. What's to stop them from changing the licence again after evaluating the impact of the first change? Liquibase has collected "anonymous" metrics by default since version 4.30 (do they consider an IP address and timestamp as PII?). As soon as I saw that, I anticipated this scenario. It was not really a surprise. They have a way to analyse the impact. Now, I am reassessing the risks.
I have nothing against someone trying to monetise useful software. However, switching from an open-source software (OSS) licence is essentially a bait-and-switch tactic. This immediately destroys trust. It also destroys the part of the user base that is difficult to monetise but still has the potential to be monetised. I was hoping that the Elastic and TerraForm debacles had taught people a lesson.
Flyway is also questionable at this point. If Liquibase is switching, what's to stop Flyway?
Unless a fork is happening, I'm considering creating my own migration library tailored to our actual needs and usage. It should not be so hard. Liquibase was more of a convenience.
Even minor changes to models can render previous prompts useless or invalidate assumptions for new prompts.
> I wanted to create an architecture that minimized future work on both the admin app and the controller network layer. That way, the business could lean on its in-house development experience to make changes after the project.
From your perspective as a UI developer, you would need to update all clients (in the building) if something on the server changes, e.g. if a new button or game state is added. HATEOAS is a good architectural choice if you want to minimise the likelihood of having to change the client implementation.
I use HATEOAS as much as possible in my daily work. It is a good way to think about state, state transitions and what capabilities a client must have. That's the actual part of the author's motivation. It provides the "in-house development" with paradigms how to make changes.
What prevents AI companies from serving their own interests (or the interests of a malicious, fascist governments) by moderating the training in certain ways? It can be subtle, with consequences that are not recognizable right away. Didn't Musk already complained about Grok being "too woke"?
And how can I trust those companies with my own data?
P/E ratios - VW 6 - BYD 13 - Tesla 200
Tesla's valuation is absurdly crazy.