ksjskskskkk

rclone is garbage if you need performance or just copy between two points you control.

it shines when you need to sprinkle your data over many "clouds"

because in the very near future everywhere will only accept a couple issuers.

not even paranoia, already happened once. just like oauth in the beginning and then everyone cried about how ugly their design was with "oauth nascar" and then only accept google or apple. it already happened once. today you can only login on saas with github (Microsoft). etc.

this passkey push will boast openess, then on day one spam will take over and will serve as the excuse to limit to google or apple attestation only. as usual. and by then it will be too late because everyone was mislead by the initial promissed openess, and like you, might even have happily added it to your service, increasing the adoption momentum.

this is part of the: passkeys as the ultimate centralized online identity plan.

every single newpipe problem is google actively breaking them.

every time it crashed failing to parse some video is even more reason to use it!

yaml, all the xml mistakes for the new generations!

can't wait for yamxslt.

karpersky writes about then from time to time. since its not the CA key but some CA signed by those CA they just revoke that one and move on and nobody cares. last year (or the one before) they discussed this at length on the mozilla chats before the meeting

you forget systems have humans in them. most online banking scams hijack bank domains and use CAs for that country gov, which usually have keys leaked or sold on the right (wrong?) places. just look at india or brazil list of small govt CA revocations. those are usually CAs signed by the CAs in your browser.

so, yeah, a gov abusing this is very bad and visible. scammers profiting from the complexity and humans in the machine, is very common.

on 2: caches for one

https everywhere is literally throwing the baby with the bathwater. yeah we got a little better at hiding content, still leaking ton of metadata, and still vulnerable to all the root CAs in your browser... and lost cache and everything else that http had.

lol. kids down vote literal history

ironically, the seminal paper in economy about information asymmetry bringing overall quality downfall to the entire market was on lemon cars

> [sw] took more than six months just to get set up with the wrong information, an overly manual process, and in the end, wasn’t nearly worth the squeeze for the clients.

southwest is the only one that won't give "gifts" to your company employee making the decision (not telling outright bribes, which does happen, but some 1st class tickets thrown around now and then). that's why sw is often not present in company policy.

everyone in this thread agrees google problem is all management and product and that buying a company is just a palliative way of acquihiring a still ungoogled management team. which don't last long, obviously.

you're all just telling each other exactly this in hundreds of different ways.

you're wrong most of the time and google is too big and disfunctional to have a goal. it's just PM fiefdoms to extract profit from half done projects.

if google actually had one maintenance coder it could conquer the world

when dual booting recently, i realized all the wifi security in windows is handled by the wifi driver!

only noticed that because one laptop lost wpa3 after a driver update so i went looking into what's packaged on those.

it's insane. expecting all wifi exploits to be covered and no bugs on crucial crypto done by the likes of driver authors on broadcom and such other companies... just crazy!

sell a better solution and get rich.

btw what we have today is the worse of both worlds. apple et al can tie you to a identity which you cannot use to recover your data but they can sell to advertisers or act on police requests from that profile metadata.

it was a group effort.

started with ISP selling your mistyped dns queries to google or whichever search engine they could sign a deal.

from there there was a race to capture as much mistyped domains until google had the end-game idea to pay Firefox to send non-standards domains to google directly, not even wait for it to fail dns resolution.

when later google launched Chrome, initially as a cost saving for the firefox deal, they dialed the dns to search hack so aggressively that they broke the internet (search for chrome type ahead incident).

all search engines (called portals at some point in time) goal was to be the dns replacement. AOL had "keywords" which they advertised heavily in their tv channels like TNT ("we will be back with Terminator. see more at Terminator keyword on AOL")

you mean optimizing for profit alone?

what two people do with their hidden browser settings is irrelevant to the world.

they darkpatterned the world into using AOL Keywords.

the new "think of the children"

the same reason you deliver a big project you don't want to work on in the last minute

in this thread: people who is still learning nix, or people who barely got hooked on nix. and lastly people who looked at nix and didn't like it.

absent: everyone who understand the finer details on software packaging and already implemented different trade-offs than nix

shoot the messenger.

since you have stocks of the billion dollar message

big tech hires the same researchers as Philip Morris in the 50s

compare google QA and release process to someone bound by auto or medical industry.

imagine a google peace maker. lol

Occam's razor: Google processes are all built around hosted software. they're still learning how to actually ship code to users device.

most of those examples don't even have a webapp or website.

oh, right. let me talk to the devs of imessage, which is one of the notifications hinted at the origin of this discussion last week

DRM by definition is on the client and opaque.

I'm not sure where you are getting all that misplaced goodwill and hopes of lack of capabilities

it doesn't. companies can't author works, just own them.

that's the reason de etre of the silly "made by ai" discussions.