I can imagine loopholes to this... nothing stops facebook/google from buying this data from companies not in Massachusetts? and facebook/google don't have to give advertisers the location information but can still use that information when determining the advertisement to return, right? In theory the big silicon valley "targets" of this bill don't actually have a huge incentive to give this data away, do they? They just need to be able to read/access it, which I don't think this law stops? Assuming the data broker is not doing business in Massachusetts itself

avg500 -4.6 last 500 episodes

peak 3959.3 best window

roll/s 20.68 20-step avg

progress 4388 562749 episodes

So it's not... On AWS... ?

This statement sounds.... Backwards?

I get they have another option that is in AWS, but this continues the cryptic naming problem AWS already is overloaded with

When that water source is underground wells, this can take years (on the fast end) or decades (on the moderate end) to get back down. Look at California's water issue -- so many wells extracting water for farming has changed the land topography.

Also, when water 'comes back', it might come back in the ocean and not on land... reducing the available fresh water without desalination.

Data centers need the water to cool... but maybe there's room to find incentives for them to do so while making sure our water bills don't go up like our electric bills are because of the extra load they are putting on utilities.

[0]: https://www.theregister.com/2024/08/19/virginia_datacenter_w...

In the US at least, any private homeowner/renter can deny entry to their property, barring legal warrants and exceptional circumstances. A business can have a policy, and is generally legally protected as long as the policy is 1) equally applied, and 2) does not violate ADA... A court would have to weigh in if glasses are allowed or not for ADA... but I suspect there's already a case where a movie theater banned such glasses and they would probably(?) win, since such individuals could be expected to have non-recording glasses.

Some brands are okay with impressions.. you can build trust in your product be advertising it for weeks/months and when the user does make a purchase that brand is on the mind.

So they can't sell the fact that you're at Target at 8:00 p.m. on Thursday to anybody... Nor build profiles to sell to advertisers... And if that's the case that's very similar to cloud storage vendors.

If I access hacker news, and the record of my visit is stored in an AWS S3 bucket, I can't submit to AWS to delete my visitor record, even though the server, network cards, wires, and storage medium are AWS property, it was hacker news' website that generated that record and their responsibility to take my request to delete it.. AWS' stance would rightly be "talk to the website operator for CCPA requests"

If I see a flash on a speed camera operated by a business on behalf of a police department, your argument states I should be able to use CCPA to force the business to delete my picture and the record of me speeding If I can get the request to them before the police can file with the court and request that data as evidence.

The data belongs to the government, and you can't get around that right by going to business that holds the data and asking them to delete it.

Flock seems to leave the data in ownership of the government. They are just providing the service of being custodians for storing and accessing that data.

You probably would get a similar response by submitting your request to Amazon web services or Google cloud or whoever has Flocks data: "sorry, we're just holding the data on behalf of Flock"

In either my example case or your stated case, you would have a very hard time convincing the host business to destroy their customers data without a court order or court case that shows their policy is invalid and they must comply.

Not a lawyer, just noting the parallel.

I do appreciate that Flock's response says that they cannot use the data they've collected for other purposes.. which further reinforces my cloud storage analogy -- the cloud vendor can't look at your data you upload to storage to e.g. build profiles on you/your business.

> Here we account for the influence of three main natural variability factors: El Niño, volcanism, and solar variation.

All of these events are decades-long (or longer) cycles that don't have a substantial amount of data points... Sure, solar cycles seem to be 11 years, but we don't have a lot of scientifically usable (for forecasting) data points on that -- maybe 8 cycles? less? And the cycles are not consistent. It's not like Year 4 of one cycle is like year 4 of another cycle, we just determined there's a period of about 11 that looks significant.

Same with El Niño -- it's not like its 'true' or 'false', there's degrees of it.. and when it starts, and if other conditions are right to make additional hurricanes that year, and how much cloud cover that generates, etc. etc. a lot of which we don't have data on past 1960 when we launched our first weather satellite ...

As for volcanos... there's lots of them, and we are not great at predicting the high-impact events... we certainly don't have sufficient data to accurately predict what happens if we had a huge eruption on an El Niño strong year during the height of a solar cycle.

I was frustrated that (because my posts are less frequent) changes in Hugo and my local machine could lead to changes in what is generated.

So I attached a web hook from my websites GitHub repo to trigger an AWS Lambda which, on merge to main, automatically pulled in the repo + version locked Hugo + themes. It then did the static site build in-lambda and uploaded the result to the S3 bucket that backs my website.

This created a setup that now I can publish to my website from any machine with the ability to edit my git repo. I found it a wonderful mix of WordPress-like ability to edit my site anywhere along with assurance that there's nothing that can technically fail* (well, the failure would likely, ultimately block the deploy, but I made copies of my dependencies where I could, so very unlikely).

But really the main thing I love is not maintaining really anything here... I go months without any concern that the website functions... Unlike every WordPress or similar site I help my friends run.

Comments URL: https://news.ycombinator.com/item?id=46015034

Points: 2

# Comments: 1

Advancements in solar also are improving with clouds.

Also, you know, batteries. When someone makes it cost effective to install a device to sell your car battery power on the grid we'll also have a better time managing the grid during spikes... Would be nice if that also did home battery backup in blackouts... 70 kWh would get me through most of the ones I've experienced.

And I think that's what the parent post is talking about. Today's companies make you agree to 3 50-page documents which they can update at any time and your continued use after such silent updates constitutes consent.. and at some point they will sell your financial status/well-being to people for profit. So the more you feed them the more of your data that is being easily sold.

We ultimately probably can't stop that, but we can make it more difficult. Many apps like this would take your information and sell it.. having an option that lets you track your own finances without becoming a product is nice.

I wish these were also commercially available... I'd love to pay for one of these... I know it's open sources, but I don't know the language nor do I have the skills to construct one myself.

It is cheaper/easier for me to hire cloud infrastructure _capable_ people easier and cheaper than a server _expert_. And a capable serverless cloud person is MUCH cheaper and easier to find.

You don't need to have 15 years of a Linux experience to read a JSON/YAML blob about setting up a secure static website.. of you need to figure out how to set up an S3 bucket and upload files... And another bucket for logging... And you have to go out of your way now to not be multi-az and to expose it to public read... I find most people can do this with minimal supervision and experience as long as they understand the syntax and can read the docs.

The equivalent to set up a safe and secure server is a MUCH higher bar. What operating system will they pick? Will it be sized correctly? How are application logs offloaded? What are the firewall rules? What is the authentication / ssh setup? Why did we not do LDAP integration? What malware defense was installed? In the event of compromise, do we have backups? Did you setup an instance to gather offloaded system logs? What is the company policy going to be if this machine goes down at 3am? Do we have a backup? Did we configure fail over?

I'm not trying to bash bare metal. I came from that space. I lead a team in the middle of nowhere (by comparison to most folks here) that doesn't have a huge pool of people with the skills for bare metal.. but LOTS of people that can do competent severless with just one highly technical supervisor.

This lets us higher competent coders which are easier to find, and they can be reasonably expected to have or learn secure coding practices... When they need to interact with new serverless stuff, our technical person gets involved to do the templating necessary, and most minor changes are easy for coders to do (e.g. a line of JSON/YAML to toggle a feature)

You don't buy Apple to use your computer they way you want to use it. You buy it to use it the way they tell you to. E.g. "you're holding it wrong" fiasco.

In some ways this is good for general consumers (and even developers, with limited config comes less unpredictablilty)... However this generally is bad for power users or "niche" users like Mac gamers.