skysight-inc/HackerNews huggingface dataset:
I like this. Here are a few more:

"We maintain a lot of BAZ we think no one needs anymore but we don't know for sure" is called a Yikes.

"You just have to know which alerts matter and which don't" is called an Uh-oh.

And of course "securing the QUUX wasn't an explicit requirement for launch so we haven't done it yet" is already called a vulnerability.
The court did not even see this issue, i.e. the distinction between issuing a suggestion or directive vs. actually executing the request directly. The court, in fact, states that the was the website itself that did the sharing. The ruling suffers from unsound reasoning.

It could be, however, that the website owner never brought up these arguments. The court does not have to do its own investigation. This is called the “maxim of disposition” in German law. Whatever both parties agree on what is true has be treated as true by the court.

So if the claim that the website itself issued the request to Google servers was uncontested, then this ruling is sound, based on the claims brought forth by the parties in this particular case.
That's true but the mitigation to that is that it would have been OK if the user has consented to this "data processing".

The court isn't ruling this sort of technology en bloc but says in its ruling that it is a problem because the user didn't consent to his personal data (IP address) being given to a third party (Google in this case).

Personally I have mixed feelings about this ruling too because this sort of technical solution is widespread and an army of GDPR vigilantes has the potential to cripple large portions of the web by filing similar suits. Or we won't be able to access websites without having to go through entire multi-page EULAs and consent forms for every and all kinds of similar 3rdparty technology embedding.

Law is a blunt tool and will have unintended consequences, unfortunately :(
In Roman Law a contract requires consent, which cannot be forced, https://www.lawteacher.net/free-law-essays/contract-law/cont...

So it's not just your jurisdiction, it's probably at least half of the entire world and I imagine even systems not based on Roman Law have something equivalent.
I'm not sure it's "arbitrary" that people living longer is considered an upside.
This was the case once upon a time.

Nowadays, cache is partitioned by website (https://developers.google.com/web/updates/2020/10/http-cache...)
Hey, this could be cool, I’m always on the lookout for fast graphing software for dashboards - grafana was what I used last but it didn’t quite hit the spot for me

Some site feedback and first impressions:

As a user I need to see your product early, I see lots of generic corporate graphics but no screenshots (visiting from mobile). So I can’t figure out what I’m getting. I watched the video but it was just the same, and at that point I’d internally made the call not to invest more time searching

I’d ask you to turn down the scroll entry animations, these are more of a hinderance than attractive. I understand the signal is to be flashy, but that needs to be used with tact to work

However, If I was linked to this page instead:

https://gravametrics.com/docs/content/

I’m 100x more likely to explore the product, it’s plain and clear and makes a good impression. If I found the homepage in the wild I would have given up before finding that page
I stayed there a bit and there isn't so much of a single people meeting up type thing. A lot of people stay home, go shopping go home. There was much more of an events happening meet people vibe in NYC.
In jurisdictions with juries. It's judges, otherwise.
The Ticking Clock for Miami’s Condo Empire
This is such a cool project, it's almost indecent.

I think it would be a force multiplier to also showcase the "ecosystem" (e.g. 3D printed adapters, mounting points, suitable DCDCs for specific applications, etc).

Even just "caveat implementor" links would show the possibilities and help people (like me) go from "that's cool but I'll struggle to trivially make it relevant to my devices" to "huh, all I need is to use something like this STL and use a scrap of strip board like this and mount it here with that DCDC, huh".
Yeah i reckon some 80 year old grandmothers struggle with some Android functions.
Google rate limits and then blocks your server ip? oops

Doubling your bandwidth costs vs hosting the woff files? oops

Still forwarding the ip address in the X-Forwarded-For header? oops

Not following the license agreements of font providers? my bad
What’s your fav ?
The Importance of Fyodor Dostoevsky
It's depressing to reflect on the extent to which the quality of political debate in the U.S. has declined since then.
> And what if they're already cached in the browser.

It is a common misconception that CDN objects are cached. They are not: https://httptoolkit.tech/blog/public-cdn-risks/
It's loading fonts. So squarespace needs to host those fonts, fine. But more to the point, it could be argued even the Squarespace CDN is "different" from the actual website, so we need CDN shims that forward local domain requests to the CDNs and return the results. All to hide an IP number for downloading fonts." Moreover, "host it yourself" is easy if you're technically skilled, but very, very difficult if you aren't.
It also depends on how recently you graduated and how much commute you’re willing to have. I like walking to work which often means much higher rent.
I switched to using ublock origin to do that, since I can quickly add an exception for a site. Some sites use fonts for icons. Most of them are still usable but just look a bit silly, but sometimes it's annoying to the point that I want to add an exception.
This ruling has nothing to do with opt-in or consent. It has to do with the concept of data minimization. According to the GDPR you should only process as much data as necessary and this applies no matter what legal basis (eg consent) you have. So basically the point with GDPR is that you as a user should not even have to care, the company that processes your data is responsible to care for you. And it's actually cool that we see this enforced now.
Reading our layman developer interpretations of the legalities here is very interesting, but that aside this really makes me rethink my own use of Google hosted fonts in my projects. Whether it is the browser responsible for making the request or my website being responsible for asking the browser to make the request, hosting the font myself is a readily available option. From the perspective of respecting users' data, why call out to Google at all when I don't really have to, for _any_ resource where there's a straightforward alternative?

I say this as someone who does use Google Analytics as well (which I am removing). But mostly for me it isn't a case of dropping all third party convenience services, but a case of remembering to be _mindful_ of what I'm doing.
I remember seeing one occurence of bubblesort in the source code of Crafty chess engine with a comment explaining that this was unexpectingly the fastest sort in that particular case. (It was the ordering of a few moves in the quiesce algorithm I think).
Under the GDPR, an IP address is personally identifiable data, so you can't leak it.

And for someone with masses of extra data like Google it is enough to identify who is doing the browsing, so this isn't some crazy overreach.
Try making this argument with compiled code instead of HTML:

"The company included the code to do $BAD_THING in the binary executable, but it was the user's choice to run it, and he could have easily modified the binary to ignore $BAD_THING, but didn't. Therefore, it was the user doing $BAD_THING, not the company."

A lot of people in this discussion are splitting hairs here, trying to blame the user or the browser. The technical details of what a browser does are less important than the end effect: Fundamentally, the web developer added "stuff" to the HTML, knowing that this "stuff" will cause most browsers in the field to access these fonts on another computer. The fact that the end user could technically block it, doesn't change the developer's intent.
Am I the only one who thinks this is ridiculous?
> The mantra of “the GPL is not a contract” is a mistruth that has been so often repeated that it became widely accepted and typically unchallenged. (We expect you'll hear this theory repeated even more loudly now that the our Vizio lawsuit brought the question to the forefront in a federal court case.) Yet, prominent legal experts outside of FOSS social circles have long scoffed at the assertion. Indeed, case law in the USA has held the opposite. In multiple cases, courts have been convinced, specifically, that the GPL operates as both a contract and a copyright license. The law appears clear on this, and this is among the reasons why we believe our motion to remand will succeed. In short, we'll say it plainly here and now for everyone: the GPL operates both as a copyright license and as a contract; litigation can proceed under either of those legal theories.

I think that if this case succeeds, it would actually be a huge blow for the GPL. We are actually just now starting to get over all the FUD about the GPL and convince corporate lawyers to allow using GPL. However, if they win this case on those terms, I expect every corporate lawyer to to have major heartburn about GPL. If for example, they successfully are glue that GPL gives every user of the software the right to sue, doesn’t that massively increase liability for the corporation? I can see many lawyers pushing to completely ban copyleft licensed software use.
The plaintiff’s IP address was also leaked to every intermediate router and potentially to the DNS server(s) that resolved the IP address.
Consent forms are not required, just host the font. They are also way more expensive and complicated to implement than self-hosting fonts. Asking for consent over usage of third-party fonts borders on pettiness from the website owner.

> User agents should have the ability to convey and enforce privacy preferences on behalf of the user, and website providers should be legally required to comply with these if possible (or refuse service if not).

The burden of respecting privacy choices in every single other case (data in the backend, data shared with partner, paper data) is already with the website. Every non-privacy-respecting implementation in the frontend is made by website owners.

Keep in mind that sometimes websites don't work with blocking other stuff, or are more difficult to use when blocking fonts (Google Material). So this is not even a practical suggestion.
True. I’m not sure the Valar ever did anything en masse.
If that was true, how does Google work within China?
By that logic it sounds like you must use your own servers to host the data, otherwise you are sharing the IP with a cloud provider.
The case is simply about giving a second way for GPL compliance to be enforced. The copyright holders (the original authors or probably their employers) have always been able to enforce the GPL against violators, but when a large portion of the electronics industry is violating the GPL on Linux, it becomes infeasible to enforce it against every company, so outsourcing that enforcement to people actually affected by that GPL violation, and possibly even opens up GPL enforcement via class actions, which makes things much more even again. I don't think the creators of the original code would have any liability and anyway as the original authors who chose the GPL as a license, they probably know how to comply with it and are already in compliance.
On BTC, you could send things to the wrong address, yes. But you can't send the wrong type of currency or send it to a nonexistent address. In this case it seems like the contract has created the black hole (not the Ethereum blockchain itself), but that's even more absurd since someone ultimately should have control over everything that was put into the contract, regardless of the source.
> Technically the victim activates the mechanism, but surely the one who sets the trap carries the blame?

Well said.
Law is not a programming language, the fact that the website didn't _technically_ share the IP, but did it through the browser, is not relevant.
Discourse Running on TruffleRuby
Most DAOs are indeed DOA
The "women negotiate less" theory is just one of many. I don't think it is actually accurate. For example engineers used to be notorious for being bad at negotiation and accepting underpaid jobs. Bookshelves in bookshops used to be full of career advice books (when bookshops still existed). So it is not as if men are naturals at it. (Also, women are more expensive for employers, because they have more sick days and are more likely to drop out completely once they have kids).

Incentives however are completely different for women. They usually don't have to support a family. At most they have to support themselves if they remain single or childless. So they can choose "nicer" jobs in exchange for lower compensation. They can also simply drop out if they don't like a job or a profession.

You can try to stir your daughters in another direction, but a valid question should be "why"? Are you sure it would make them more happy? Many women just decide to study literature, for example. Would they be happier with an engineering degree? Who knows? I personally will try to get my daughter interested, but in the end, it will be her choice.

As an example, because I had such a discussion one with a paediatrician and a hospital manager. She was a bit annoyed that colleagues for example from radiology earned more. But it is nicer to work with children all day than to sit in front of machines all day, so more women (most women) choose to work with children. There certainly is nothing preventing women from becoming radiologists, but they simply choose differently. In fact few people choose radiology, so wages re higher due to supply and demand.

I also know women who changed from becoming surgeons to some more family friendly specialty. You can not walk away in the middle of surgery to pick up your kids from school. That is not because of discrimination in the profession of surgery, but inherent to the job. Similar for truck driver. How would you make truck driving more family friendly? If you are on the road for a week to deliver goods to the other end of the continent, you won't be able to see your family in between. That is just inherent to the job.

However, in the wage gap statistic you will just see "female physicians earn less than male physicians" without accounting for the different specialisations. It is all very misleading.
OTOH Apple is a public company and whatever they do and spend money on is scrutinized by the shareholders who will calculate ROI and ask questions.
Why is it not the author of your NIC driver who is responsible for the leak? Per default the driver isn't asking whether to send a packet to Google's IP address.

Here's why: the driver is just doing what it's told to do. The responsible falls on the party who does the telling. If a website tells my browser to load resources from Google, it's not on my cpu or my nic or its driver or kernel or firewall or the browser.
If the water has epsom salt you're going to be more out of the water, no?
This is called plausible deniability- the site owner knows what he is doing, but does not care. He could have downloaded the font or used a analytic service which does not collect IP address. Great ruling.
> and cookies set on the *.google.com domain.

The request doesn't include cookies (and they're served from fonts.googleapis.com so wouldn't include google.com cookies).
As an example, the home DSL router my ISP supplied violates the license of at least Linux (GPL), samba (GPL) and microhttpd (BSD).
By that logic you must self-host any landing page, otherwise you are leaking IP addresses to whoever is hosting your website.
If no one ever moved coins out of their burn addresses I'll eat my socks.
As a middle aged dev type who prefers pretty girls to middle aged dev types, film / acting events are kinda fun. You can even do an acting class and be an unemployed actor on the side like the rest of them.
Something happening once does not mean it will happen again. There have been numerous huge hacks in the past 5 years, even where the losses were from the most influential of holders and no action was taken (e.g. parity bugs).

A bug and reversal occurred in the first few years of Bitcoin's existence that has effectively meant that Bitcoin won't reach the stated 21m coins exactly.

It's guaranteed at this point that there won't be any further reversals.
> passing the burden of filtering those requests to the customer doesn't really scale

I think it scales better than forcing millions of website providers to engage in the legal fiction that they are an intermediary between the user and all external content providers that are embedded on their page
This is, for better or for worse, how the internet works. There may be better alternatives, but we're stuck with this for now. The truth is that an extraordinary amount of websites use a third-party resources, jQuery from CDNs, fonts from Google, etc. This ruling will never stand in higher courts imo, because it would break the internet through fear.

I'm curious to know whether DNS and your IP being in the the header of packets travelling through various different countries that can be sniffed is also considered as unwilful data sharing?
What if mankind always had such sleeping problems? Without historical baseline you cannot tell if that 70m is high or low.
I can recommend Fastmail. Switched to them a few years back. Privacy they aren't the greatest - Australia based company.

Besides that:

* They do mail, and do it well

* Calendar/contacts support

* they use standards (IMAP/caldav/cardav)

* Webclient is OK - faster than Google, and for me it just works better.

* They have labels! This is a killer feature, I really did miss it coming from Google. I have a bunch of filters that label my mails accordingly, I just hit archive when I'm done with them so they disappear from view

* Android client is 'ok'. To get the contacts/calendar in the Android apps I recommend DavX5.

* Catchall

* Recently added "Masked Email" - you create a random alias on your mail account to use to sign up for services. If you have 1Password it'll even generated a pw for you.

When I first switched I had issues with an iCal feed from O365 where MS didn't honor the spec, and this caused duplicate issues. FM implemented a fix. Forget about this kind of service from Google or MS, unless you are an international multi-million dollar company.
> even though the provider has nothing to do with the interaction

I beg your pardon, but in this case "the provider" (website) has directly sent the user's browser to a third party (google fonts) by including an instruction in the code (HTML) that the provider has sent to the user's browser. The browser did not decide to contact google fonts all by itself; it was directed to do so by the provider. Arguing the provider "has nothing to do with the interaction" looks a bit disingenuous to me.
MDX and Svelte in Markdown etc are definitely cool, but unfortunately they are not at all adequate for the job. You can not define a new component in MDX/MDSVEX, only use existing Svelte/React components in prose.

Further what about the arguments of those components, can they themselves contain markdown? How about markdown with React or Svelte component? Would you really with straight face say this is powerful:

<Penguin text="Some text, which itself contains <Another />" />

Just try nesting it or writing multiline text, its complete torture.
It's not really a pancake if it's baked now is it? Every "pancake" I can think of is always pan-fried. What is it called in Dutch?
It’s really incredible how easy some of these scams appear to pull off. “I’m your oldest child and no my microphone doesn’t work so I can’t talk to you and I need $2000 immediately” and the parent bypasses warnings from the bank about possible fraud and shoves the transaction through…

It also shows how many of these scams can be defeated with a few simple precautions. Most of them would be defeated by calling the bank back… in other words don’t answer your phone, make all your calls outgoing. Others are defeated by simply not doing anything hastily and under duress (like urgently wiring all your money to an external account for “safekeeping”).
If you build with the explicit goal to learn and explore the process and problem domain, and then have to rework code because of new insights and understanding, we are as close to the original definition of technical debt.

But it is my impression that this is the rare exception. In most cases, people are just bullshitting to cover up their ineptitude.
if my nans had that kinda money she'd have an iPhone.
No because hacking generally circumvents the intended system design. The architecture of the World Wide Web explicitly allows for user discretion in fetching and executing linked content. There's no slippery slope from using a system within design parameters and executing malicious instructions on other people's systems without their permission and/or knowledge.
So this is my view.

The immortal organism would not evolve. Imagine you and I lived 100K years from now. Other humans would evolve somewhat during that time but we would be fixed. Climate change might happen, new humans would adapt to the changing environment via evolution, but we would be stuck suffering the new environment.

The humanity example takes a long time to be noticeable. But for early multi-cellular organisms this would kick in much faster. Thing about micro organism fighting against toxins. The ones that do not evolve and adapt would die off sooner. And while they are still alive they are competing for resources with the newer versions of themselves. So for the colony it is advantageous for the older ones to die quicker since we already know they will be unnecessary sooner or later.

Now we evolved from these primitive creatures. And the mechanisms for things like aging, circadian rhythm, sexual reproduction, etc - we inherited from the early creatures. So regardless if the advantage of dying sooner is beneficial or not to the humanity now - the mechanism itself is far more ancient than humanity or even mammals.
Have used a stack like that on one application, a rather simple "knowledge vault", a few years back. It worked very well, and at the time I liked it very much. But these days, I'm no longer fond of client-side scripting (because it gets very complex very quickly, and npm+webpack is a monster). So my next stack would be closer to BCHS [1], only with Linux, Golang, and nginx instead of BSD, httpd, and C. I might add in a tiny bit of client-side scripting such as [2], but no more npm, webpack, etc. for me.

[1] https://learnbchs.org/index.html
[2] https://htmx.org/ https://unpoly.com/ https://hotwired.dev/
If inflation was bad, would destroying ETH not be a good thing since it leads to what's effectively an instant deflation of supply?
>Seems like laws don't understand how tech works...

That's pretty much the definition of a law. Laws are written for people, by people. Not for computers.

This is sadly an unintended consequence of a very broad interpretation of GDPR, where an IP address is deemed as personally identifiable information.

If someone wanted to take this to absurd levels, similar argument, as has been made by this court, could be used to make the entire Internet illegal under GDPR - sending a packet exposes personal information of the sender to various third parties (routers of various ISPs) that the sender didn't consent to. And given that the recipient (service provider, website, whatever) could have arranged for having the data transferred on a floppy disk or by a pigeon instead ...

It is not only GDPR that suffers from this - e.g. in Austria it is illegal to drive with a dashcam because their court has ruled that a dashcam amounts to recording someone without their consent - and if you do so, it exposes you to a 20k€ fine!