Recent submissions

Comment · 2 years ago
plaque and food under gum line
Comment · 2 years ago
Please don't disturb the FUD with facts.
Comment · 2 years ago
My (human) heuristic LLM score for this text is very high.
Comment · 3 years ago
Specify what languages are supported
Comment · 3 years ago
You don't need bone conduction for that, air pods pro 2 work just as well. Bone conducting headphones are mainly good for sports involving water (or sweat) IMO, but the quality is significantly subpar to regular headphones.

Also, you can definitely hear bone conducting headphones in the environment if the volume is high enough as the vibrations also vibrate the air.

Comment · 3 years ago
391
Comment · 3 years ago
People are hating because Elon == Bad. Twitter is pretty good these days, I see almost no spam and content quality has improved.
Comment · 3 years ago
O'Dowd picked this route specifically to fail FSD, as he obviously has a financial interest and a vendetta against Musk. It was clear as day Gerber was gonna get tricked but he didn't care.

As can be seen in hundreds of uncut hours of driving, FSD is already pretty good and improving fast. Most rides don't req

Comment · 3 years ago
Brave gives a very bad vibe (mostly due to the affiliate links scandal), I prefer to just use my favorite browsers (ff/edge) + uBlock Origin and Privacy Badger which give good privacy/adblock experience, are open source and customizable to my liking.
Comment · 3 years ago
It's the internetz' eye-roll, shorts are perfectly fine in nyc.
Comment · 3 years ago
> One day you’ll find yourself wearing shorts. Fair enough, it’s probably hot out. One day you’ll also find yourself wearing a t-shirt. Again, fair enough. Unless you’re playing a sport, however, you will not be wearing the two together because you’re also no longer a ten-year-old boy.

Yikes, OK boomer

Comment · 3 years ago
Filter by "ip.addr == 1.1.1.1" and look at the "Time" column. With UDP you'll see 2 datagrams - request and response. TCP you'll see a SYN,SYNACK,ACK handshake and then 2 segments. TLS you'll see a longer handshake and then (encrypted) request and response (2 segments).
Comment · 3 years ago
On Windows DNS/UDP/WiFi to 8.8.8.8 with query=www.google.com is 3-4ms

TCP is around ~10ms including overhead, 3ms excluding.

TLS is ~100ms including overhead, 5ms excluding.

1.1.1.1:

udp - 5ms

tcp - 15ms / 10ms

tls - 70ms / 4ms

Use a sniffer (e.g. wireshark) to get a better idea for timing, I wouldn't count on dig for that.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton