Show HN: Hacker News LCD Badge https://ift.tt/8ysPNBf

Show HN: Hacker News LCD Badge https://ift.tt/kXCzBWS March 12, 2023 at 10:04AM

Show HN: ChatGPT Based PR Reviewer and Summarizer https://ift.tt/M29AeJh

Show HN: ChatGPT Based PR Reviewer and Summarizer https://ift.tt/jsGUZWL March 12, 2023 at 01:45AM

Show HN: Andromeda Invaders: Auto Play: Press 'Enter' twice and wait 5 seconds https://ift.tt/4wFM7VZ

Show HN: Andromeda Invaders: Auto Play: Press 'Enter' twice and wait 5 seconds https://ift.tt/us7V0DY March 12, 2023 at 12:18AM

Show HN: Browse and Generate AI Memes for Free https://ift.tt/ZVjvk0a

Show HN: Browse and Generate AI Memes for Free https://meme.koll.ai March 11, 2023 at 11:12PM

Show HN: Find the most climate friendly meeting location https://ift.tt/2VEHdlX

Show HN: Find the most climate friendly meeting location Just enter the locations people will be traveling from. MLC then calculates the location, where the combined aircraft emissions are minimised. Based on data from the European Emissions Agency. https://ift.tt/Ejnlc2z March 11, 2023 at 10:37PM

Show HN: ReplGPT.jl, a ChatGPT shell mode for Julia https://ift.tt/NPOfqL3

Show HN: ReplGPT.jl, a ChatGPT shell mode for Julia https://ift.tt/7diTFOb March 11, 2023 at 08:03AM

Show HN: structured-ripgrep – Ripgrep over structured data https://ift.tt/nc4I78A

Show HN: structured-ripgrep – Ripgrep over structured data https://ift.tt/6BrjRYA March 11, 2023 at 02:49AM

Show HN: Discontent – Extension to fight garbage content on the web https://ift.tt/ANCHrR1

Show HN: Discontent – Extension to fight garbage content on the web Creator here, I made this out of mild frustration with the current state of search engine results. Let me know what you think. https://ift.tt/WtRO9w4 March 10, 2023 at 03:43PM

Show HN: I added autopilot to the lunar lander game https://ift.tt/6buJ38I

Show HN: I added autopilot to the lunar lander game I got pretty good at (and too addicted to) the lunar lander game from a few days ago... so I decided to make an autopilot for the lander based on what I felt like was the best strategy! Now I can have perfect landings every time without lifting a finger :D Writing the autopilot code was a lot more fun than I expected! It felt a bit like programming a robot. Source code: https://ift.tt/uHeZM9s Original lander HN post: https://ift.tt/gPxySv4 https://ift.tt/l1mSGIC March 10, 2023 at 09:00AM

Show HN: Homepage.gallery – Find your web design inspiration https://ift.tt/0peiIDX

Show HN: Homepage.gallery – Find your web design inspiration https://ift.tt/9dh8OqM March 10, 2023 at 01:33AM

Show HN: Send an AI Generated Physical Letter to Congress in Seconds https://ift.tt/T5uZWHl

Show HN: Send an AI Generated Physical Letter to Congress in Seconds https://ift.tt/Dz0LJVy March 9, 2023 at 06:27PM

Show HN: A-Pass – small little password manager https://ift.tt/VjdEntU

Show HN: A-Pass – small little password manager https://ift.tt/vUq5M8I March 10, 2023 at 12:33AM

Show HN: Safe Data Changes in PostgreSQL https://ift.tt/hrwuV5U

Show HN: Safe Data Changes in PostgreSQL Hi HN, we're excited to share our open source tool with the community! We previously posted here with the tagline “real-time events for Postgres” [0]. But after feedback from early users and the community, we’ve shifted our focus to working on tooling for manual database changes. We've consistently heard teams describe challenges with the way manual data updates are handled. Seemingly every engineer we spoke with had examples of errant queries that ended up causing significant harm in production environments (data loss/service interruptions). We’ve seen a few different approaches to how changes to production databases occur today: Option 1: all engineers have production write access (highest speed, highest risk) Option 2: one or a few engineers have write access (medium speed, high risk) Option 3: engineers request temporary access to make changes (low speed, medium risk) Option 4: all updates are checked into version control and run manually or through CI/CD (low speed, low risk) Option 5: no manual updates are made - all changes must go through an internal endpoint (lowest speed, lowest risk) Our goal is to enable high speed changes with the lowest risk possible. We’re planning to do this by providing an open-source toolkit for safeguarding databases, including the following features: - Alerts (available now): Receive notifications any time a manual change occurs - Audit History (beta): View all historical manual changes with context - Query Preview (coming soon): Preview affected rows and query plan prior to running changes - Approval Flow (coming soon): Require query review before a change can be run We’re starting with alerts. Teams can receive Slack notifications anytime an INSERT, UPDATE, or DELETE is executed from a non-application database user. While this doesn’t prevent issues from occurring, it does enable an initial level of traceability and understanding who made an update, what data was changed, and when it occurred. We’d love to hear feedback from the HN community on how you’ve seen database changes handled, pain points you’ve experienced with data change processes, or generally any feedback on our thinking and approach. [0] https://ift.tt/DwFjR05 https://ift.tt/9VG76Ly March 9, 2023 at 09:21PM

Show HN: Delete All Your Tweets https://ift.tt/VvEOabL

Show HN: Delete All Your Tweets To use it, go to your Twitter timeline then go to "tweets" tab to delete all tweets, OR go to "replies" tab to delete replies. Paste the following code into the browser JavaScript console. DISCLAIMER! This code deletes all your Tweets - I am not responsible for you deleting all your Tweets. Make sure you set your twitter handle in the code before pasting it! // IMPORTANT IMPORTANT IMPORTANT - SET YOUR TWITTER HANDLE IN THE NEXT LINE! // IMPORTANT IMPORTANT IMPORTANT - SET YOUR TWITTER HANDLE IN THE NEXT LINE! const yourTwitterHandle = "@yourtwitterhandle"; // one every 10 seconds to avoid Twitter noticing const waitTimeSeconds = 10 const sleep = async (seconds) => new Promise(resolve => setTimeout(resolve, seconds * 1000)); const main = async () => { while (true) { await walkTweets(); await sleep(waitTimeSeconds) } } const walkTweets = async () => { let articles = document.getElementsByTagName('article'); for (article of articles) { const spanElements = article.querySelectorAll('span'); for (spanElement of spanElements) { // delete if it is a retweet if (spanElement.textContent === "You Retweeted") { article.scrollIntoView(); try { const retweetElement = article.querySelector('[data-testid="unretweet"]'); if (retweetElement) { retweetElement.click(); document.querySelector('[data-testid="unretweetConfirm"]').click(); } } catch (e) {} return } if (spanElement.textContent === yourTwitterHandle) { // in this case it might be a tweet or a reply article.scrollIntoView(); try { // try to delete a reply const tweetReplyElement = article.querySelectorAll('[aria-label="More"]')[1]; if (tweetReplyElement) { tweetReplyElement.click() Array.from(document.getElementsByTagName('*')).find(el => el.textContent.trim() === 'Delete').click() document.querySelector('[data-testid="confirmationSheetConfirm"]').click(); return } } catch (e) {} try { // try to delete a tweet const tweetElement = article.querySelector('[aria-label="More"]'); if (tweetElement) { article.scrollIntoView(); tweetElement.click() Array.from(document.getElementsByTagName('*')).find(el => el.textContent.trim() === 'Delete').click() document.querySelector('[data-testid="confirmationSheetConfirm"]').click(); return } } catch (e) {} } } } } main() March 9, 2023 at 05:33AM

Show HN: Reverse Proxy as a Service https://ift.tt/gXAdlPQ

Show HN: Reverse Proxy as a Service https://SnowOwl.co March 9, 2023 at 03:13AM

Show HN: BBC “In Our Time”, categorised by Dewey Decimal, heavy lifting by GPT https://ift.tt/wZ9oFCp

Show HN: BBC “In Our Time”, categorised by Dewey Decimal, heavy lifting by GPT I'm a big fan of the BBC podcast In Our Time -- and (like most people) I've been playing with the OpenAI APIs. In Our Time has almost 1,000 episodes on everything from Cleopatra to the evolution of teeth to plasma physics, all still available, so it's my starting point to learn about most topics. But it's not well organised. So here are the episodes sorted by library code. It's fun to explore. Web scraping is usually pretty tedious, but I found that I could send the minimised HTML to GPT-3 and get (almost) perfect JSON back: the prompt includes the Typescript definition. At the same time I asked for a Dewey classification... and it worked. So I replaced a few days of fiddly work with 3 cents per inference and an overnight data run. My takeaway is that I'll be using LLMs as function call way more in the future. This isn't "generative" AI, more "programmatic" AI perhaps? So I'm interested in what temperature=0 LLM usage looks like (you want it to be pretty deterministic), at scale, and what a language that treats that as a first-class concept might look like. https://ift.tt/DEueKh6 March 9, 2023 at 12:58AM

Show HN: SearQ, RSS are still useful https://ift.tt/zk3iwJU

Show HN: SearQ, RSS are still useful https://searq.org March 8, 2023 at 07:28PM

Show HN: Construct Animate – our new browser-based animation tool https://ift.tt/sONqHG2

Show HN: Construct Animate – our new browser-based animation tool https://ift.tt/2ivsYQ1 March 8, 2023 at 03:47PM

Show HN: Co-locating Debian Bullseye with an evil maid https://ift.tt/q3pd4If

Show HN: Co-locating Debian Bullseye with an evil maid In order to facilitate the secure co-location of a server, I looked into protecting a Debian Bullseye system from evil maid attacks. In addition, since I've enjoyed using ZFS for some time, I decided to rely on a natively encrypted ZFS root file system. Basically... I'd like to take a system containing sensitive information, box it up, and drop it in the mail without worrying about losing it or having it wind up in the wrong hands. A couple of things became clear while researching how to do this. First, there should be little chance that a rogue data-center admin can insert malicious software. When the system reaches the data center and gets powered on we should be confident that it's running our software completely unmodified. As I understand things, Secure Boot is designed to help with this and therefore should be enabled. However, by relying on Secure Boot alone, there will be no remote method of knowing that it hasn't been disabled until after the ZFS pass-phrase is provided to the initramfs via dropbear. At that point it's too late. An evil maid could have already subverted dropbear, for example, and just now stolen the pass-phrase. To avoid this I realized that a second requirement of using a TPM device to automatically unlock the ZFS root was in order. TPM devices have the ability of "sealing" data to so-called Platform Configuration Registers (PCR). This feature allows the data to be accessed only if the "measured" system state matches some original expected state. The TPM can fully start the system unattended but, if anything's unexpectedly meddled with, act like a tripwire requiring the pass-phrase to be typed in manually. If we ssh in and reach dropbear requesting the pass-phrase, we'll know that we either need to update our sealed data after a grub/kernel/initramfs update... or someone's been messing with our start up code. This window of opportunity will be too small for an evil maid to take practical advantage of. This sounded like the right track and I set out to try and configure both, Secure Boot and TPM unlocking of an encrypted ZFS root. I thought it'd take a few hours at most but it actually turned out to be a fair challenge. After a few failed attempts I started tenaciously documenting every avenue. Ultimately I developed helper scripts that can reproduce the configuration should the time come to actually ship a machine out the door. I'm reasonably satisfied with the outcome. However, the scripts haven't been reviewed and neither has the overall process itself. There were a lot of guides I followed that contained typos, bugs, dubious information or simply different requirements. I'm not sure everything is exactly "bullet-proof" for this show HN. For example, I'm beginning to wonder if Secure Boot is necessary and if the TPM alone is sufficient. So naturally, comments and criticisms regarding everything are greatly appreciated. The script files can be found here: https://ift.tt/NRnJrEf and here: https://ift.tt/2tk1TDS Finally, I hope this effort will be useful to others facing similar needs. March 8, 2023 at 02:49PM

Show HN: Salesforce Announces Einstein GPT https://ift.tt/RsuAxob

Show HN: Salesforce Announces Einstein GPT Salesforce Announces Einstein GPT, the World’s First Generative AI for CRM https://ift.tt/7C83FWH March 8, 2023 at 11:38AM