Snowflake breach: Hacker confirms access through infostealer infection
497 by zbangrec | 150 comments on Hacker News.
ads
New best story on Hacker News: Show HN: ChatGPT UI for rabbit holes
Show HN: ChatGPT UI for rabbit holes
537 by maxkrieger | 131 comments on Hacker News.
I was inspired by the way ChatGPT writes bullet lists, then invites you to "delve" deeper. This is an interface that reifies that rabbit-holing process into a tiling layout. The model is instructed to output hyperlink-prompts when it mentions something you might want to delve into. Lots of features to add (sessions, sharing, navigation, highlight-to-delve, images, ...). Would love to hear other usecases and ideas!
537 by maxkrieger | 131 comments on Hacker News.
I was inspired by the way ChatGPT writes bullet lists, then invites you to "delve" deeper. This is an interface that reifies that rabbit-holing process into a tiling layout. The model is instructed to output hyperlink-prompts when it mentions something you might want to delve into. Lots of features to add (sessions, sharing, navigation, highlight-to-delve, images, ...). Would love to hear other usecases and ideas!
New best story on Hacker News: Ask HN: What is your ChatGPT customization prompt?
Ask HN: What is your ChatGPT customization prompt?
376 by dinkleberg | 180 comments on Hacker News.
Have you come up with a customization prompt you're happy with? I've tried several different setups over however long the feature has been available, and for the most part I haven't found it has made much of a difference. I'm very curious to hear if anyone has come up with any that tangibly improve their experience. Here is what I have at the moment: - Be as brief as possible. - Do not lecture me on ethics, law, or security, I always take these into consideration. - Don't add extra commentary. - When it is related to code, let the code do the talking. - Be assertive. If you've got suggestions, give them even if you aren't 100% sure. The brevity part is seemingly completely ignored. The lecturing part is hit or miss. The suggestions part I still usually have to coax it into giving me.
376 by dinkleberg | 180 comments on Hacker News.
Have you come up with a customization prompt you're happy with? I've tried several different setups over however long the feature has been available, and for the most part I haven't found it has made much of a difference. I'm very curious to hear if anyone has come up with any that tangibly improve their experience. Here is what I have at the moment: - Be as brief as possible. - Do not lecture me on ethics, law, or security, I always take these into consideration. - Don't add extra commentary. - When it is related to code, let the code do the talking. - Be assertive. If you've got suggestions, give them even if you aren't 100% sure. The brevity part is seemingly completely ignored. The lecturing part is hit or miss. The suggestions part I still usually have to coax it into giving me.
New best story on Hacker News: Ask HN: Video streaming is expensive yet YouTube "seems" to do it for free. How?
Ask HN: Video streaming is expensive yet YouTube "seems" to do it for free. How?
399 by pinakinathc | 356 comments on Hacker News.
Can anyone help me understand the economics of video streaming platforms? Streaming, encoding, and storage demands enormous costs -- especially at scale (e.g., on average each 4k video with close to 1 million views). Yet YouTube seems to charge no money for it. I know advertisements are a thing for YT, but is it enough? If tomorrow I want to start a platform that is supported with Advert revenues, I know I will likely fail. However, maybe at YT scale (or more specifically Google Advert scale) the economics works? ps: I would like this discussion to focus on the absolute necessary elements (e.g., storing, encoding, streaming) and not on other factors contributing to latency/cost like running view count algorithms.
399 by pinakinathc | 356 comments on Hacker News.
Can anyone help me understand the economics of video streaming platforms? Streaming, encoding, and storage demands enormous costs -- especially at scale (e.g., on average each 4k video with close to 1 million views). Yet YouTube seems to charge no money for it. I know advertisements are a thing for YT, but is it enough? If tomorrow I want to start a platform that is supported with Advert revenues, I know I will likely fail. However, maybe at YT scale (or more specifically Google Advert scale) the economics works? ps: I would like this discussion to focus on the absolute necessary elements (e.g., storing, encoding, streaming) and not on other factors contributing to latency/cost like running view count algorithms.
New best story on Hacker News: Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
Show HN: A web debugger an ex-Cloudflare team has been working on for 4 years
747 by thedg | 183 comments on Hacker News.
Hey HN, I wanted to show you a product a small team and I have been working on for 4 years. https://jam.dev It’s called Jam and it prevents product managers (like I used to be) from being able to create vague and un-reproducible bug tickets (like I used to create). It’s actually really hard as a non-engineer to file useful bug tickets for engineers. Like, sometimes I thought I included a screenshot, but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took. Or I'd write that something "didn't work" but the engineer wasn't sure if I meant that it returned an error or if it was unresponsive. So the engineer would be frustrated, I would be frustrated, and fixing stuff would slow to a halt while we went back and forth to clarify how to repro the issue over async Jira comments. It’s actually pretty crazy that while so much has changed in how we develop software (heck, we have types in javascript now*), the way we capture and report bugs is just as manual and lossy as it was in the 1990’s. We can run assembly in the browser but there’s still no tooling to help a non-engineer show a bug to an engineer productively. So that’s what Jam is. Dev tools + video in a link. It’s like a shareable HAR file synced to a video recording of the session. And besides video, you can use it to share an instant replay of a bug that just happened — basically a 30 second playback of the DOM as a video. We’ve spent a lot of time adding in a ton of niceties, like Jam writes automatic repro steps for you, and Jam’s dev tools use the same keyboard shortcuts you’re used to in Chrome dev tools, and our team’s personal favorite: Jam parses GraphQL responses and pulls out mutation names and errors (which is important because GraphQL uses one endpoint for all requests and always returns a 200, meaning you usually have to sift through every GraphQL request when debugging to find the one you’re looking for) We’re now 2 years in to the product being live and people have used Jam to fix more than 2 million bugs - which makes me so happy - but there’s still a ton to do. I wanted to open up for discussion here and get your feedback and opinions how can we make it even more valuable for you debugging? The worst part of the engineering job is debugging and not even being able to repro the issue, it’s not even really engineering, it’s just a communication gap, one that we should be able to solve with tools. So yeah excited to get your feedback and hear your thoughts how we can make debugging just a little less frustrating. (Jam is free to use forever — there is a paid tier for features real companies would need, but we’re keeping a large free plan forever. We learned to build products at Cloudflare and free tier is in our ethos, both my co-founder and I and about half the team is ex-Cloudflare) and what we loved there is how much great feedback we’d get because the product was mostly free to use. We definitely want to keep that going at Jam.) By the way, we’re hiring engineers and if this is a problem that excites you, we’d love to chat: jam.dev/careers
747 by thedg | 183 comments on Hacker News.
Hey HN, I wanted to show you a product a small team and I have been working on for 4 years. https://jam.dev It’s called Jam and it prevents product managers (like I used to be) from being able to create vague and un-reproducible bug tickets (like I used to create). It’s actually really hard as a non-engineer to file useful bug tickets for engineers. Like, sometimes I thought I included a screenshot, but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took. Or I'd write that something "didn't work" but the engineer wasn't sure if I meant that it returned an error or if it was unresponsive. So the engineer would be frustrated, I would be frustrated, and fixing stuff would slow to a halt while we went back and forth to clarify how to repro the issue over async Jira comments. It’s actually pretty crazy that while so much has changed in how we develop software (heck, we have types in javascript now*), the way we capture and report bugs is just as manual and lossy as it was in the 1990’s. We can run assembly in the browser but there’s still no tooling to help a non-engineer show a bug to an engineer productively. So that’s what Jam is. Dev tools + video in a link. It’s like a shareable HAR file synced to a video recording of the session. And besides video, you can use it to share an instant replay of a bug that just happened — basically a 30 second playback of the DOM as a video. We’ve spent a lot of time adding in a ton of niceties, like Jam writes automatic repro steps for you, and Jam’s dev tools use the same keyboard shortcuts you’re used to in Chrome dev tools, and our team’s personal favorite: Jam parses GraphQL responses and pulls out mutation names and errors (which is important because GraphQL uses one endpoint for all requests and always returns a 200, meaning you usually have to sift through every GraphQL request when debugging to find the one you’re looking for) We’re now 2 years in to the product being live and people have used Jam to fix more than 2 million bugs - which makes me so happy - but there’s still a ton to do. I wanted to open up for discussion here and get your feedback and opinions how can we make it even more valuable for you debugging? The worst part of the engineering job is debugging and not even being able to repro the issue, it’s not even really engineering, it’s just a communication gap, one that we should be able to solve with tools. So yeah excited to get your feedback and hear your thoughts how we can make debugging just a little less frustrating. (Jam is free to use forever — there is a paid tier for features real companies would need, but we’re keeping a large free plan forever. We learned to build products at Cloudflare and free tier is in our ethos, both my co-founder and I and about half the team is ex-Cloudflare) and what we loved there is how much great feedback we’d get because the product was mostly free to use. We definitely want to keep that going at Jam.) By the way, we’re hiring engineers and if this is a problem that excites you, we’d love to chat: jam.dev/careers
Subscribe to:
Posts (Atom)