hypothesis

I think Fedora release is officially supported for 13 months, which allows one to upgrade every other release, or be a release behind at all times, if desired.

They seem to do go a good job updating major components for latest-1 release: kernel, Firefox, etc.

However, I noticed that say Chromium updates are not as fast or at latest version. So using Fedora that way might not be best choice.

I see frequently on HN this idea that big company behind said web browser can simply throw more devs at it, adding things and features (useful or not) and simply drown any competitors with churn of changes. But you still want security patches too, so you have to install and keep up to date with upstream. Is this also causing relentless update cycle? I think so.

That’s fair. Although I personally don’t need that tied to my phone. Maybe it could be substituted with contactless cards?

I’m just acknowledging the reality.

There is now a very nice summary comment from worik elsewhere in the thread, but basically end-users are no longer the same from Canonical’s perspective and so it’s probably wise to thank them for good things they did and move on.

Are those people paying customers?

Likely the idea is to let upstream to package once and ship it on all supported platforms. This way there is no constant support/packaging required from distro itself.

As to why snap format specifically, that’s probably allows them to make changes as needed without asking anyone.

Are you somewhere where banks won’t let you use their website and force app usage?

Chromium I think. Basically anything that is a moving target.

To me it was clear on the day when they pulled the plug and dumped everyone back into regular gmail: this was a product that was worked so well, that you no longer saw things that you were not going to interact with and were not wasting your time in this attention economy. And that was a “bees against honey” situation and it not allowed to continue.

People who created Inbox they should be proud of themselves!

> Yeah, bugs that are discovered after release can be fixed.

I definitely understand that real benefit.

But I was questioning the premise that having blob in ROM is somehow better than needing same blob in firmware, simply because that one doesn’t need/want to distribute non-free firmware on media.

If one wanted libre hardware, then both cases are not great.

Is hardware becoming more complicated without being more capable? I just think that we’re taking lots of things for granted nowadays, which require complexity to be managed successfully.

ROM to firmware creep is understandable, given flexibility that you mentioned. But to an end-user, is there a difference between having a blob in ROM vs firmware, if both are closed source?

> My experience is the same as the author's: there's more today that needs non-free support to use Linux on the desktop than there was in the past.

Is that a function of Linux Desktop simply being more capable nowadays?

Also, there is a world of difference between not publishing signed closed-source firmware for a driver that does not exist vs having an open source driver with published firmware.

So it says that ~6500 members are driving this by ponying up ~$511 annually. Interesting.

The scenario I had in mind would pertain to California where they aren’t allowed to ask your salary history. So if one didn’t not disclose salary info, then offer was likely not based on that info (nor on work number info). In which case they can’t pull offer due to misleading salary info. However, all bets are likely off in states with no such protection…

As in you had to interact directly with work number for that? Or do you mean that lender “magically” knew and pre-populated your salary info during application process?

If they pulled salary info after making an offer, then this is likely qualified as verification of data that prospective employee submitted. They can probably revoke that offer if one provided misleading info during application.

That last link says that data is exempt from CCPA.

> The Work Number® database is subject to the Fair Credit Reporting Act (FCRA)

> Data that is regulated by the FCRA, as well as data used for employment purposes, is exempt from the CCPA.

Is there a plan to have corresponding 1.0 release of reference implementation?

Latest 0.6.1 release was couple months ago…

> Despite the missing details from Apple on the technical design of Private Relays, the provided description by Apple leads us to conclude that private relays do not provide privacy by-design, but privacy by-decision.

This sounds vaguely familiar, as in: this will mostly work against surveillance by other corps.

Ironically, someone recently attributed “hope is not a strategy” to Google’s engineering…

I definitely understand the sentiment and curious if you researched options before making this switch?

For hobbies and even general PC hardware, there are definitely companies out there that are hostile towards Linux. When possible, vote with your money towards better alternatives.

As for remoting, rdp-ing from linux is a solved issue, as long as VPN is not too esoteric… at which point driver compatibility is not an issue anymore. That’s Looking Glass scenario for me :)

Better for whom? It’s EOL. Are they just plugging high-visibility issues? That’s not doing anything for individual device’s security. They need a giant INSECURE sign instead of giving that false hope for people: “they might patch me past EOL if it’s bad enough”.

That’s like trying to disable all those similar things in Firefox. But you can’t really, not unless you stop updating it, because you’ll miss something at some point. And that’s not even an ‘evil corp’ we’re talking here.

Are we talking about ‘at work’ scenario? Which is probably fine, because that’s a business decision.

It would be prudent not to use company equipment for anything personal anyway.

What’s interesting is the fact that telemetry is a feature at this point (how old is Windows 10?) and you can’t win a fight against a core OS feature. Why are people still trying to fight this?

But does it really do anything to secure a device that’s past EOL? Or is it a marketing action?

Long official support is absolutely a benefit when looking at smartphones, however, articles keep popping up about Apple basically buying and sitting on vulnerabilities for latest and greatest iOS, because that’s what works economically.

I see.

It’s a bit sad that everyone is so hung onto full-auto driving and car subscription models, that no one is trying to make current things more practical.

I’m not even talking about gas cars, is there an EV car that can park itself at charger and charge without human being involved?

Interesting… so it would not simply connect another device using dhcp?

I never needed to use it and I’m not sure what was the motivation to introduce it into hdmi, but requiring cooperation would explain why it wasn’t used widely.

> Mercedes drivers can get their cars to pay for their fuel.

Does anyone know more about this? Is this for EVs only? Or is there a standard of some sorts or is it a custom agreement/implementation between car manufacturer and gas stations?

I wonder why they never used that Ethernet-over-hdmi, which is a thing for many years now. There is likely something plugged into TV using hdmi that is connected to network.

Also, I recall reading that TVs from certain manufacturers had/has bugs in them that will prevent TVs from functioning after periods of time without connection or firmware updates.

I can see those cheery iStalking ads already, telling you to get anti-stalking subscription.

And, of course, for adventurous devs they’re going to introduce a StalkingKit!