why not try huggingface?
Readit Newsyy77 commented on Running Llama2 Models Locally · Posted by u/waelbs
yy77 commented on TikTok Is a Chinese Superweapon gurwinder.substack.com/p/... · Posted by u/sethbannon
This biased post pollutes HN.
if the author truly buy-in the idea of new cold war, then holywood, youtube, and facebook are weapons too. the author even try to use blog platform and public forum like HN as weapon as well.
yy77 commented on macOS Drops to Third Most Popular Desktop OS pcmag.com/news/macos-drop... · Posted by u/miles
both macOS and ChromeOS are bind to the device in most case. So this conclusion means that Chromebook device had already sold more than the whole macOS device volume?
why will we need such service? If we have to include the detailed IP address in the URL, why not direct access use IP address itself?
yy77 commented on To Break Google’s Monopoly on Search, Make Its Index Public bloomberg.com/news/articl... · Posted by u/JumpCrisscross
The key for goolge's monopoly is not only its index algorithm capability, but also the brand, the chrome browser, the android and all other google product integration.
airdrop is actually like a security hole when Apple set "open to everyone" by default.
There are already quite some cases using it to send * photos as sex harassment.
Apple should set default to "only contacts".
criticism on SQL does not make it meaningful for a new database. I mean, an ORM with its own query language, a new SQL dialect, some language that compile to standard and optimized SQL are all good ideas.
yy77 commented on Facebook's role in Brexit – and the threat to democracy [video] ted.com/talks/carole_cadw... · Posted by u/dredmorbius
Please admit that the old way of communication using newspaper magazine & public speech is out of date, social media has stronger impact.
An quick stop for the possbile privacy disaster for Apple is to stop group facetime call at once but not wait for later this week for bug fix.
Could image that quite some one might already try to peek for privacy using this.
>However, in those discussions, a related concern was identified; confusion between QUIC-the-transport-protocol, and QUIC-the-HTTP-binding. I and others have seen a number of folks not closely involved in this work conflating the two, even though they're now separate things.
>
>To address this, I'd like to suggest that -- after coordination with the HTTP WG -- we rename our the HTTP document to "HTTP/3", and using the final ALPN token "h3". Doing so clearly identifies it as another binding of HTTP semantics to the wire protocol -- just as HTTP/2 did -- so people understand its separation from QUIC.
https://mailarchive.ietf.org/arch/msg/quic/RLRs4nB1lwFCZ_7k0...
TL;DR the rename is to resolve the confusion.
why not just http/quic?
using 3 seems strongly suggest that it is the next generation of http.
They knew that but pretend it is not relavent.