Yes, a dystopian future of censorship and human rights abuses. If that's the price of progress, no thanks. I'd rather have an AI that is slightly less capable than it could be, than a totalitarian regime that is actively abusing me
The N64 was extremely constrained by its cartridges. If it had a CD-ROM drive, it could have easily won the console wars of its generation, or at least would have gotten ports of many more PS1 games. Probably one of the biggest blunders in gaming business history. Ah well.
That is very interesting. So far I am extremely careful to avoid putting negative statements into my instructions, to avoid poisoning the AI's thinking with exactly the concepts I do not want it to have. This might be from my use of much older models where if you say "do not X", then "X" gets put into the context and the "do not" kind of gets lost. It was especially visible with stable diffusion where you would ask for a picture without a feature and get exactly that feature. Maybe current models are better at that.
> Just bundle [...] everything except base system libraires
That means everything above libc. There are no "base system libraries" in the Linux world for GUI. Not even libX11, that has been deprecated in favour of libxcb, which has been deprecated in favour of not having X11 and running Wayland. Some days I am amazed that the ELF binary format hasn't been deprecated yet...
LibX11 is still alive and kicking. It is however possible to bundle libX11 and/or libxcb (libX11 today sits on top of libxcb) because the wire protocol between them and the X server is also backwards compatible.
And of course Wayland has XWayland to continue compatibility. This doesn't give you access to new toys but neither does restricting yourself to a 30-year old Win32 API.
And beyond libc/libX11/libxcb, libasound has also provided good backwards compatibility with newer systems implementing shims to make it work. You can also use libpulse directly if you don't care about old/opinionated systems though.
Then add the option, but make it default to soft caps. Or bake the default into the tiers. If I sub with a $20 spending limit, I will probably be ruined by a $2000 bill. On the other hand, if a company subs with a $1000 limit, it can probably cover the occasional $10000.
At the very least, there should be an optional hard limit that is obviously indicated in the UI. When you're signing up where you set your "usage cap" warning, next to it should be an optional hard cap with big bold red letters "THIS WILL CUT YOU OFF THE MOMENT YOU GO ONE CENT OVER". So I can set e.g. a warning at $20 and a hard cap of $100.
I would say the game should generate some kind of a grand staircase every time a slope is the right shape, but let the player replace it if they wish. Would be even better if the element was chosen based on zoning policies, local ordinances, land value, etc. Soul by default, but infinitely customisable.
What does a "script" mean in this context? Like a Python script that runs a series of agents with small tasks? I'm still getting used to doing things with AI, this is all very new to me.
Yeah and look at where this soft approach landed us. We have entitled crybabies voting for Hitler 2.0 because they can't stomach the uncomfortable feeling of seeing a diverse person in their pure white neighbourhoods. Children and young adults need to be hit with the big hard fist of reality repeatedly until they become good people. If some should fall through the cracks, they would not have made for good members of society anyway, so best they fall early and not drag the rest of us with them.
reply