There's a browser extension that reads the content of the article on the page (only when you activate it, using least privilege browser APIs for content scripts) and then narrates the article for you. You get a custom podcast RSS URL that works in (almost) any podcast player, and then you can take articles with you to catch up while driving, walking the dog, etc. All the typical podcast audio controls you're used to like speed settings, skipping, and no new apps to download or learn.

It has genuinely been a big benefit and allowed me to keep up with articles I'd never normally have time to read, plus it allows me to reduce my screen time. My wife also uses and loves it. There have been some interesting bugs in the narration like originally pronouncing "24/7" as "twenty-four sevenths" but I am working through different strategies to get more accurate narration from arbitrary long-form text.

With apologies for the ".AI" domain, it was a bit of an impulse buy: https://earcast.ai/

Comments URL: https://news.ycombinator.com/item?id=48892343

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46542792

Points: 7

# Comments: 2

Seems completely different. See also, this discussion:

https://news.ycombinator.com/item?id=44976568

I feel like this is a reasonable attempt at disclosure, but it also seems like it's lacking. I usually include a summary, not the entire prompt (how would I included tool use?) I don't say which models or "agent" was used (cursor sidebar chat vs calude code, etc). Not sure if this matters though?

How have you been managing this in your own workflows?

Comments URL: https://news.ycombinator.com/item?id=45031549

Points: 4

# Comments: 6

Serious question: what should have been said on this call to do that? There was a lot of "I'm sorry you feel that way" seeming to come from the HR representative, but it seemed to miss the mark.

    >  curl https://unpkg.com/leaflet@1.7.1/dist/leaflet.css

    
    
    
        
    ... a bunch of HTML

Comments URL: https://news.ycombinator.com/item?id=33372128

Points: 3

# Comments: 1

The HTMX and alpine libs were intended to be sprinkled onto existing web apps (my usual python/flask stack), whereas Phoenix would be for building all new projects.

Comments URL: https://news.ycombinator.com/item?id=31413483

Points: 130

# Comments: 108

Comments URL: https://news.ycombinator.com/item?id=30306657

Points: 4

# Comments: 0

This is where having multiple hobbies not only adds depth to conversations & makes you more interesting, it allows you to cross-pollinate your friend groups from each hobby. If you join a cross fit gym and a running group (as others have mentioned in the thread), then you invite someone from the gym to the group or vice versa.

The invitation can either be a "I think you'd really enjoy this activity", in which case you're introducing them to something new and cool, or it can be "I think you'd really like the people I do X with" in which case you're helping them meet friends.

People who take you up on the offer to either try something new or meet new people with you as their guide are sure to become friends. You get to see each other in new elements and your relationship can now trascend simply doing one activity together.

I think this approach feels a lot more natural than jumping straight to "hey, I've seen you at the rock gym a bunch, let's get coffee?" which can feel like a big jump and somewhat forced.

citation or story?

It's not like they called to the plane and said "we'd like to kidnap a passenger, please land" and the pilot went along with it.

Dropbox is "just" a private s3 bucket with s3cmd on a cronjob -- or a million other technical solutions -- but they're a successful business because they nailed the user experience for average joes.

The point of OP's product is that you don't have to cobble together a bunch of hacks to replicate the desired user experience, it's supported out of the box.

    7:55 Angina example
    10:05 Parkinson’s disease example
    13:10 Multiple sclerosis example
    14:52 emphysema example
    18:47 knee pain
    20:40 spine surgery
    21:52 Injection therapy for pain
    24:59 Explain perceived effectiveness 
    26:29 correlation vs causation
    29:33 Improvement not due surgery
    30:33 Natural history
    34:01 regression to the mean
    35:43 concomitant treatment
    39:16 perceived improvement: patient vs clinician
    41:50 therapeutic envelope
    42:38 Intervention: the placebo pill
    44:02 Building the ideal placebo
    47:02 “Why do we still operated?”
    52:00 Determining effectiveness
    52:55 Reducing error in estimating the truth
    54:55 Why we need blinded randomized trials
    55:12 Ethics and Placebo
    59:50 One possible solution
    1:00:20 Current status of placebo RCT in orthopedics
    1:00:44 Summary, questions, and comments

I have used this technique multiple times myself to help with otherwise fraught or overwhelming decisions, and I think it's a great way to shift your frame of reference.

Interview where he describes it here: https://www.youtube.com/watch?v=jwG_qR6XmDQ