Live data from Hacker News

Show HN: Bring-your-own-key browser extension for summarizing HN posts with LLMs

github.com

21–30 of 33 posts

Re: Show HN: Bring-your-own-key browser extension for summarizing HN posts with LLMs

#24

This is so weird, why does every user has to use their LLM subscriptions/keys instead of just storing the summarization of the HN posts as a static website somewhere? (e.g. summarize once for all users)

That costs money to host a server, summarize yourself, etc. While it is possible, such a service would require advertisements, a (probably monthly) fee, or a benevolent patron to pay for the costs. With this, the only necessary benevolence is the creator of the extension.

the server cost is basically nothing since since it's static content. probably fits into free offerings from cloudflare.

the summarization is where the cost is and it would be cool to have some crowdsourced contributor model there.

smells like a cool crypto/ai crossover project in the making (or maybe drop the crypto and have upvote-driven "moderation").

Re: Show HN: Bring-your-own-key browser extension for summarizing HN posts with LLMs

#25

This is so weird, why does every user has to use their LLM subscriptions/keys instead of just storing the summarization of the HN posts as a static website somewhere? (e.g. summarize once for all users)

.. because being a threaded extension of some central hub connected to some other central hub is exactly the "vibe" ?

Re: Show HN: Bring-your-own-key browser extension for summarizing HN posts with LLMs

#26

This sounds possibly useful, but I just don't trust extensions unless I can see the code.

hmm even though the code is open source, how do you know that the published extension is bundled using the same code as what is open sourced? I guess I'm trying to say you'll have to be okay with some level of trust here unless you clone the open source project use it to load an unpublished extension for yourself

Re: Show HN: Bring-your-own-key browser extension for summarizing HN posts with LLMs

#27

This sounds possibly useful, but I just don't trust extensions unless I can see the code.

hmm even though the code is open source, how do you know that the published extension is bundled using the same code as what is open sourced? I guess I'm trying to say you'll have to be okay with some level of trust here unless you clone the open source project use it to load an unpublished extension for yourself

That's understandable, I feel same when I install extensions. In both browsers, you can install the extension from local disk instead of the browser stores. The release artifact is a ZIP file with plain JS inside, no bundling, minification, preprocessing, you can check it out. Both Chrome and Mozilla did some inspection during several business days, but I can't say exactly what they checked and how diligently.

Re: Show HN: Bring-your-own-key browser extension for summarizing HN posts with LLMs

#28

This is so weird, why does every user has to use their LLM subscriptions/keys instead of just storing the summarization of the HN posts as a static website somewhere? (e.g. summarize once for all users)

That costs money to host a server, summarize yourself, etc. While it is possible, such a service would require advertisements, a (probably monthly) fee, or a benevolent patron to pay for the costs. With this, the only necessary benevolence is the creator of the extension.

[deleted]

Re: Show HN: Bring-your-own-key browser extension for summarizing HN posts with LLMs

#29

This is so weird, why does every user has to use their LLM subscriptions/keys instead of just storing the summarization of the HN posts as a static website somewhere? (e.g. summarize once for all users)

When I was incubating the idea, I thought about different concepts:

1. The current bring-your-own-key.

2. A central summary storage, filled by me.

3. A central summary storage, crowdsourced.

4. A paid subscription, where I effectively run some LLM proxy.

I wanted something low overhead and be just the right size for yet another weekend project which I could drop at any moment. Supporting some infrastructure, having moderation headaches, let alone receiving payments ruled out pretty much everything but the current approach.

Post reply on HN