sha666sum

Could you please elaborate? I wouldn't think this causes an issue unless they need to link against it, which I don't think they do.

This URL includes a bunch of tracking parameters. Cleaned version: https://news.gandi.net/en/2020/07/why-we-retired-the-securit...

Something nobody else seems to have said here, is that Valve's work on Linux, Proton, streaming from one device to another (even phones), etc, puts them in an excellent position for cloud gaming, as pointed out by [1]. Namespaces support seems like an obvious next step here.

Valve is already in the best position for this, since they're the dominant market player and gamers already have their game libraries in Steam. Buying a game from Valve makes more sense than buying a game from Google Steam users get to keep a playable product even if the streaming product is a flop.

[1] https://www.gamingonlinux.com/articles/looks-like-valve-coul...

If there was, they could've communicated it clearly already a year ago. There is no reason to give Google the benefit of the doubt, since it's clear they're not trying to get it.

If this rolls out, I'm going to very loudly tell my friends to use Fox, and not stop.

The announcement makes it seem like they were doing so anyways, but they are willing to open source it first.

Almost everyone in Finland speaks either good or fluent English. Movies and TV shows aren't dubbed apart from some animated content, usually for kids. Domestic media can only create so much content for a population of 5 million, so the population is constantly subjected to English language media.

There's also regions along the coast where a sizable portion, or even the majority of people, are Swedish speaking[1] (and bilingual to various degrees). Swedish is an official language, and if you want to be a pain in the ass to the 95% of the population that doesn't speak Swedish apart from the mandatory school courses, you are entitled by law to get service in Swedish.

Working only in English is obviously harder, but if you want to live here, don't let that stop you.

https://en.wikipedia.org/wiki/Swedish-speaking_Finn

It runs locally, and if the attacker has that much access, in most scenarios there isn't anything stopping your adversary from just logging your keystrokes and curling the keystore to a remote server.

SMS 2FA is better than nothing if, and only if, you don't allow password resetting by owning the SMS.

> It just seems to mean "this language catches more errors at compile time than the previous language I used."

That is a fair interpretation. I've programmed mostly in C# and Java because that's what was required at the time. I also know enough C and C++ to aim at my toes instead of the entire foot. So the comparison is between strongly typed imperative programming languages which are syntactically close to Rust.

Also, I like that Rust isn't OoP, but try to not get baited into that discussion.

It is (or should be) read as slightly hyperbolic, as there isn't to my knowledge a language that actually works that well. I could water down my message by saying "it mostly works", but then I fail to convey the main reason why I posted in the first place.

I could also instead spend a lot of time and words to explain things about Rust's design that I presume anyone who is slightly interested in the language would already know (specifically: lack of null, strict ownership checking, having to explicitly deal with errors), in order to explain that the language succeeds at solving some of the problems it was specifically designed to solve. But then I would just be repeating things that HN readers presumably already know. Instead I can use a shortcut in my communication which is perfectly understandable if you assume minimal intelligence, and take the other person's comment in good faith.

See, by the time we've reached the bottom of this wall of text, anyone who read this far through my intentional rambling has presumably forgotten my initial point: I had a positive experience with the language.

My experience with Rust is that I have to fight the compiler a lot, but when the program compiles, it works. If it doesn't work, it means there's an error with my file/network paths or I did something in the wrong order, errors which no language can save me from.

Rust also becomes a lot less verbose when you get better at it. The ? operator is especially useful.

Non-shortened url: https://techerati.com/news-hub/google-3-billion-data-centres...

Data mining as a business model is fine, as long as the customer is making an informed decision, there are equally good alternatives out there which you can pay for in other means, and you're not drawn to a particular service because of network effects or platform lock-in.

However, customers aren't well informed, and if they were, they wouldn't use these services. Currently customers are getting scammed for their data. This is why we need regulation.

If the copyright expires on author's death, then you're incentivizing convenient accidents and straight up murder.

I've heard about this before. Which manufacturer? Although I'm never buying a smart TV, it's interesting to maintain a mental blacklist of vendors.

I agree.

What makes IRC good is that it's a text-only chat with a wide range of highly configurable, blazing fast clients. Not supporting images, quoting or reactions could be considered a feature, since these distract from the actual conversation at hand (consider newbies clogging the conversation with screenshots, or 100 people adding reaction emojis to a message).

When you aim for the lowest common denominator, you lose the users at the other end of the Bell curve.

You know, the people who talk about USENET and IRC are people who don't want to be "updated" to what modern users demand. I don't know if you've had a look around you lately, but the modern internet is a dumpster fire.

Anyways, ideally you would be able to connect to services with whichever client you want. You could use a pretty eye candy client, or then not. With the web, however, it's an impossible feat to implement a standards compliant browser.

Although this comment was already debunked, I'll add Arch's Firefox PKGBUILD here [1].

And to save you a click, they compile it from a source tarball.

[1] https://git.archlinux.org/svntogit/packages.git/tree/trunk/P...

I usually adjust my brakes so that my front brake isn't tight enough to throw me over the handlebars in panic. I used to bike a lot (and quite recklessly) in my teens, so I got kinda paranoid about overly sensitive front brakes.

Anyways, and without knowing the details of your accident, if you were biking 30km/h in an area where you can't see if someone comes from around a corner, then you were biking too fast. Still the girl's fault for jumping in front of you without looking.

Dawn of War hasn't aged very well for me. The camera is super zoomed in and the user interface takes up huge swathes of screen real estate.

It's funny, but whatever remains should actually be html, css and images.

Not once in their announcement did Mozilla mention VPN's.

So is this just a VPN that's baked into the browser?

One of the problems with VPNs is that you're putting a lot of faith in your VPN provider. I trust Mozilla, and would gladly pay them for that service (I would use Freedome, but afaik they don't support Linux). However, it would have to be usable outside of my browser.

Tangentually, I wish Mozilla also offered paid email (or email with a premium plan), which is another service that requires a lot of trust. It would help provide alternative sources of income to keep Firefox alive, and Thunderbird could be a stunningly good email client if they had more resources to pour into it.

Mozilla's product is trust and control. Although they are non-profit, I see no issue with them offering paid services.

> We have a similar levy in the USA, except it's mostly paid by people that can pay for healthcare, so an aspirin costs $100 when administered by a hospital.

> And since insurance companies are smart, they negotiate down those exorbitant rates to something more reasonable

This is just absurd, though. The market value of aspirin administered by a hospital is not 100$, but closer to what the insurance company negotiates it to.

This is a weird case, as it turns the question of scraping on its head. Normally you'd think "am I allowed to scrape?", but instead the question becomes "am I allowed to prevent scraping?".

Anyways, I disagree with the court's judgment here. The users have consented that their data be used in accordance with LinkedIn's privacy policy. Even if it is publicly posted does not mean that the user has relinquished control over their personal information for another company to do with as they wish.

This is a weird case, as it turns the question of scraping on its head. Normally you'd think "am I allowed to scrape?", but instead the question becomes "am I allowed to prevent scraping?".

Anyways, I disagree with the court's judgment here. The users have consented that their data be used in accordance with LinkedIn's privacy policy. Even if it is publicly posted does not mean that the user has relinquished control over their personal information, for another company to do with as they wish.

You just unironically argued that chat applications are not about communication, while Slack is. This makes no sense, as chatting is communication.

MSN Messenger with Pidgin as the client is the best IM experience I've ever had, at least for one to one conversations. There's also something to be said for identifying contacts by their email addresses, since even when the IM inevitably dies, you have a way to reach these people.

Google ignoring their customers is a recurring theme,, and I'd like to think that I have a pretty good list of tech news that I follow.

Since this is HN, which (at least used to) primarily cater to the startup crowd, I hope it goes without saying that Google does not fix this issue because they don't have a financial incentive to do so. This is basic capitalism at play, and what you as a developer/advertiser/user need to do is use and pay for competing products if you're not happy about the status quo.