In this case, they are static elements, which can even be cached locally to share more easily.
If someone wants a massive build system to render a static HTML page, that's on them, and their personal interpretation. Increasingly, and maybe more often than not, there is more than one way to get the same outcome.
The fact that there's hundreds of downloads for a single web page is up to the constructor of that page. Still, these things can be reasonably cached. For example, host it on the Pi, then put a cloudflare in front of it or something.
The Pi Zero might not be for you, or easy to try to undermine. Which criticisms would go away if it was on a regular pi?
Even then... it's usually built before it's deployed n the server.. the server is still delivering text, css, js, images and images have always been pretty large. So your connection is tied up for a little bit longer... and as content was smaller in the 90's, connections themselves are much faster today... in the 90's you were lucky to be hosting on a T1 or faster and clients on modems. Today, you've likely got between 100mb to 2gb uplink on your home connections, let alone business connections that generally start at 1gb. 600x the bandwidth for the server from a T1
I'm just not sure how this gives me control of my information, whether I want it sent or not to Google, and if they're retaining it for training or not.
That last question I don't even want to ask because the first two doesn't seem clear.
This could be simply fixed by adding the feature, and defaulting it off, and letting people learn about it and enable it.
> I'm just not sure how this gives me control of my information, whether I want it sent or not to Google, and if they're retaining it for training or not.
That's not the goal. Turning your information into their information is the goal. If training an LLM on some data isn't copyright infringement but instead makes it a brand new non-derivative work, then training an LLM on your personal information arguably means it's no longer your personal information, but instead a legally distinct work.
It's not that crazy. It can take time to do and get right, and is time away from other things.
Even if done for fun/learning, it can teach how the details of auth work to better appreciate and understand how other systems work and what to look out for.
I prefer to use existing things if possible, but if it was getting unreasonable to get it how it was needed, it wouldn't be off the table.
This will also let the telco further train agents to handle calls without the humans once enough scenarios are in place.
Still, they could just give the employees training to learn additional accents.
The English accents around the world were left behind with the subsets of English people were taught to be able to aspire to entry level administrative jobs.
People should do what has always been needed, rather than focus on how hard it is to build something, or easy, find what is needed, what right is, what good is, what quality is that actually solves problems and do those things.
HTML code, CSS, Javascript, Images.
In this case, they are static elements, which can even be cached locally to share more easily.
If someone wants a massive build system to render a static HTML page, that's on them, and their personal interpretation. Increasingly, and maybe more often than not, there is more than one way to get the same outcome.
The fact that there's hundreds of downloads for a single web page is up to the constructor of that page. Still, these things can be reasonably cached. For example, host it on the Pi, then put a cloudflare in front of it or something.
The Pi Zero might not be for you, or easy to try to undermine. Which criticisms would go away if it was on a regular pi?
reply