Right. It's the "People's car". The strategy was in the name.
...with our expensive EVs...
They can't compete on price primarily.
There is no genocide untill every last one of them is dead.
/s
Config is fine, but Yamls biggest problem is people use it to describe programs. For example: playbooks. For example: CI steps.
If YAML wasn't abused in this way it would have a lot less hate.
I don't view free-use models as open-source. Open-source means I can rebuild it from scratch and I can't because I don't know what the training data is, or have access to it.
The scale is the difference and who is harmed.
Billion dollar company losing $100. Who cares?!
Billion dollar company stealing from all artists in the world. We care.
Subscribed in case people shift.
Points 2 and 3. Basically make restrictions on normal user accounts which are fine for humans but that will make bots swear and curse.
Unless you mean "what should the registration process be" I think API keys via a user account would do.
Sometimes your longest serving engineers can be your biggest anchor. Good engineers are (justifyably) highly opinionated about what can be done, but sometimes it turns into "what I do works, so all other ways are wrong". At that point the best move for them might be to go learn how somebody else does it. Wish them well, and back a different horse.
-
Make bot accounts a separate type of account so legitimate bots don't appear as users. These can't vote, are filtered out of post counts and users can be presented with more filtering option for them. Bot accounts are clearly marked.
-
Heavily rate limit any API that enables posting to a normal user account.
-
Make having a bot on a human user account bannable offence and enforce it strongly.
view more: next ›
wewbull
joined 1 year ago
Right, so you just have a single step and then hand over to a proper script. I've seen many people try to put much more complex logic in there before handing over to a proper language.