Hacker Newsnew | past | comments | ask | show | jobs | submit | duckmysick's commentslogin

I can't get it to work on my end. Tried sending/receiving with Firefox, Chrome, mobile phone, a laptop.

Got this in the console: `WebRTC: ICE failed, add a TURN server and see about:webrtc for more details.` Not sure how to troubleshoot this. Most of the suggestions I found are for the devs not users.

EDIT: Ok, figured it out. It works if I disable Tailscale.


DataGrip (and Pycharm by extension) lets you apply heatmap colors to dataframes and database tables: https://www.jetbrains.com/help/datagrip/tables-view-data.htm...

Another option would be to load data in pandas and display it in a Jupyter notebook with style.background_gradient()

Polars delegate styling to Great Tables, but it's also doable there: https://posit-dev.github.io/great-tables/get-started/coloriz...


It doesn't make sense to have "lose" pronounced as it is. We have rose, pose, dose, nose all pronounced with ō. And then you have lose pronounced as loo͞z. It feels natural to put two O's in there when you write it.

English is not a rules-based language, esp wrt pronunciation. Words can be pronounced as anything.

When I discovered the pronunciation of Houston, TX and Houston, NY... my mind was blown

This is true, but if the goal is to be understood, it's in the speaker's best interest to pronounce words in a way they'll best be understood. So I think even if the language itself lacks formal rules, we as a society of communicators should align on some loose set of rules.

I am at a loss; should we change the way “lose” is pronounced or the way it is written? I feel like if we just add an “o”, connections with other derivative words may be lost or those need to change too.

Also, the “s” in “loose” (the actual word) should be pronounced as “z” sound, as it lies between 2 vowels. Should we also change that? Should we change the way it is pronounced or the way it is written? Maybe if we change this to “loosse” we can free space for “lose” to add an “o”?


As much as I'd like it to be the case, there's too much to unlearn, and I think this would be Pandoras box. Too many weird words and spellings to change.

This language comedian does a bunch of humorous sketches about how many languages make no sense! But in particular, this video tackles false "rhymes" like allow and shallow.

https://youtube.com/shorts/6ZE5zMnBwVc?si=gBiwe9QjT-Co-MVu


... at the mental cost of the reader.

Do you not want people to read what you write?


How does writing “lose” as “loose” help? For one, not all learn English spoken-first.

I don't see how it's possible to support Linux with Wayland, unless you limit the automation only to the browsers.


https://github.com/patrickjaja/claude-desktop-bin seems to be trying hard to but I haven't tried it.


Does anyone else remember Epic 2014? It was a video made years ago that speculated about the future of the internet and media, with the end game being personalized news written by a computer. The timeline is off but the brand names are mostly the usual suspects. Rewatching it now gives me this uncanny feeling.

https://www.youtube.com/watch?v=eUHBPuHS-7s

https://en.wikipedia.org/wiki/EPIC_2014


Did Claude point out that under this proposal the Spanish clubs would be bared from entering European competitions? Since the clubs under the same ownership (more than 30%) can't enter the same UEFA club competitions.


Why don't have all the telemetry opt-in instead? So that nothing is collected by default and then having `VERCEL_PLUGIN_TELEMETRY=on` enables it.


Because their boss said so and they're paid the big $$$ to create not to think or push back about the damage they are doing to their users.


Sometimes you need to bump a dependency version, adjust the code to a changed API endpoint, or update a schema. Even if the core features stay the same, there's some expected maintenance. I'd still call that being worked on, in a sense that someone has to do it.


For comparison, here are the official hardware recommendations for Debian: https://www.debian.org/releases/stable/amd64/ch03s04.en.html

"With Desktop" has 1GB minimum and 2GB recommended - along with Pentium 4, 1GHz cpu.


> "With Desktop" has 1GB minimum and 2GB recommended - along with Pentium 4, 1GHz cpu.

This seems like a recommendation to just really get to the desktop itself + maybe some light usage. Anything more than that and the "recommendation" is fairly useless with the memory hog of apps that are commonly used.


How did they access your Airbnb account?


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: