Noli equi dentes inspicere donati.
And because their LLM generated advice to people is bound to kill some of them, they can ‘see’ even more of them!
Ah, another pterodactyl aficionado!
Yeah, everyone knows the new standard will be whatever gets the backing of the porn industry.
Or Jathon (pronounced like Mike Tyson would pronounce JSON)
Yes, those levitating shits are really eye opening.
Well obviously they’re an expert in nameology.
Why did you switch up the title?
That’s not how it works. Right now the situation is: it doesn’t work. You claim it should be a workable situation. Show how it should work, don’t ask people to prove a negative.
Unless you bring a solution to the table, taking the position that it isn’t impossible is just cheap contrarianism on your part. Sure we can try new things, but if it doesn’t work and everyone is commenting the approach isn’t helping, then maybe take the hint. Or not, and keep swimming against the stream (in which - seeing OP’s other comments - they seem to be more interested than actually solving the problem)
If someone is trying to achieve a goal through (what they might not know are) impossible means, “letting them be” isn’t going to help them.
Although it might not seem very helpful (and indeed there are better ways of helping) pointing out the flaws in the approach is contributing more than “letting them be”. Doesn’t cost a thing to be civil about it though.
Number 2 is exactly where my hesitancy lies. Is a CDN still chugging along - not serving stuff to a select user group that has passim enabled is actually finding the fw - saving enough energy for it to cancel out a whole p2p network. I don’t think so (and again, I’d need some metrics before I will. you can’t just waive that away with 'local == fast&less steps == obvious; don’t need statistics)
As for number 3: p2p can only say if there are peers. if there are no peers, there still can be an update (what about the first person to download the firmware for example). It would be a security risk for the system to not give you updates if there are no peers, so I highly doubt that’s the case.
Sending traffic through the LAN is extremely quicker and saves a lot of steps, you dont need statistics for that, it is obvious.
That’s an overly simplistic way of looking at it, and in no way does it say anything about the energy efficiency of the system as a whole. Next to that, you still need the CDN server running 24/7 to serve hashes and fw that isn’t available in the p2p-network (just think how much less power efficient it will be to first crawl the p2p-network, make the conclusion the fw isn’t available on it, only then to still have to contact the CDN and download the fw the ‘old school’ way)
Don’t get me wrong, it’s a cool new feature and a great way to get less dependent on CDNs and save money. But I’m just not buying the energy saving argument.
They still need to contact (actually look for) and download from peers though. I can see how it can save money on CDN costs.
But with claims of climate friendliness, I would at least expect some energy consumption metrics to back that up (from all participants in the network)
Climate-friendlier
Press X to doubt.
Good luck trying to update systemd
“If it’s a legitimate interest, the browser has ways to try to shut that whole thing down”
Schisms are just feature branches, it all makes sense!