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

Show HN: Postcard Bot – Send Any Photo as a Postcard with a Text Message https://ift.tt/KQ506Ju

Show HN: Postcard Bot – Send Any Photo as a Postcard with a Text Message Hey HN! This is a fun little project that I built over a weekend back in 2016, and then as life happened I let it dwindle and die. Per request from friends and family, I’ve brought it back to life. Check it out if you want! It’s surprisingly fun receiving physical postcards in the mail. I’ve also got WhatsApp integration and some more fun things in the works, so stay tuned! https://ift.tt/2FfJ416 March 8, 2023 at 05:55AM

Show HN: ChatGPT and Document Parser = Ghost https://ift.tt/VTb5DaF

Show HN: ChatGPT and Document Parser = Ghost I've always wanted to just upload a whole book to ChatGPT and ask questions. Obviously with the char limit that's impossible... So some buddies and I built Ghost. We have it limited to 5 pages for uploads for now, but plan on expanding the limit soon. Let me know what you guys think! https://ift.tt/RJ0ZBMK March 8, 2023 at 12:56AM

Show HN: Summarizing long form videos into easy to follow essay https://ift.tt/xKmtsb0

Show HN: Summarizing long form videos into easy to follow essay Introducing ClipRecaps, the ultimate tool for summarizing long-form videos. With advanced algorithms and natural language processing techniques, ClipRecaps provides concise summaries of key points from videos, saving users time and enabling them to make informed decisions about which videos to watch in full. Say goodbye to lengthy videos and stay informed with ClipRecaps. Founded by a team of researchers from NUS, ClipRecaps has become an essential tool for students, professionals, and anyone looking to stay up-to-date in a fast-paced world. Try ClipRecaps today and experience the future of video summarization. https://cliprecaps.com/ March 7, 2023 at 01:45PM

Show HN: Hello World Java Polyglot https://ift.tt/dGOsezP

Show HN: Hello World Java Polyglot I wanted to see how much simpler native code integration has become with GraalVM's polyglot, when compared to JNI. It's less than 100 lines all up (including the POM). (I feel kinda stupid posting a "hello world" to HN, but this is a hell of an improvement.) Linux only at the moment. https://ift.tt/jfIc7X3 March 7, 2023 at 11:31AM

Show HN: Roastedby.ai – Talk some trash, have some fun https://ift.tt/CZ6fjJd

Show HN: Roastedby.ai – Talk some trash, have some fun https://ift.tt/3N2MD6T March 7, 2023 at 06:25AM

Show HN: Simple Log Alerts to Slack https://ift.tt/7c1lVLn

Show HN: Simple Log Alerts to Slack There are many log alerting systems on the market. The best known is probably Datadog. There’s also Logtail, Papertrail, Splunk, Logstash and others. These are well put together products with a host of great features, such as excellent UIs, sophisticated live searching via web interfaces and sometimes query languages and alerting. They require various levels of installation and they have costs, either through volume-based tiered systems or monthly payments. For a bootstrapped business, this can be problematic, for instance when a surge of logs - indicating a possible important problem that needs to be solved - pushes volume on to another tier. Should the “log ransom” be paid? Instead, I recalled from earlier times surely the simplest log watcher: Swatchdog [1]. It is rather venerable software. Its file history from its source download shows dates in 2015, but it was written much earlier - the 90s or possibly 80s by Todd Atkins [2]. We wanted to have alerts in Slack - the blog explains how we did it. In short: *very simply*. The code is available [3]. [1]: https://ift.tt/sar46B8 [2]: https://ift.tt/CS19NA0 [3]: https://ift.tt/2rzjfVn https://ift.tt/rpeQUf5 March 6, 2023 at 03:40PM

Show HN: Total.js – Low-code development (Node-RED alternative) https://ift.tt/P69B47a

Show HN: Total.js – Low-code development (Node-RED alternative) https://ift.tt/Im5hVP4 March 7, 2023 at 12:39AM

Show HN: Open-Source Alternative to Loom https://ift.tt/0ouLtwS

Show HN: Open-Source Alternative to Loom Hey HN, we're excited to introduce Sorbay - an open source alternative to Loom for creating and sharing screen recordings. With Sorbay, you can easily record your screen, camera, and microphone all at once. It is a complete solution that comes with its own backend service, allowing you to instantly share a link of your recording as soon as it is finished. The video is streamed directly to the backend service as the recording happens to make this possible. With both founders based in different countries, we needed a tool to quickly share screen recordings to keep us up to date or to ask for feedback. Meetings are cool if you need to discuss something deeply, but for almost everything else a quick recording works better. We had to settle for one of the proprietary solutions because none of the open source tools allowed us to quickly share something with each other. Doing the recording is one aspect, but having the ability to instantly share a link was crucial. Waiting on a 400mb video upload to a Dropbox is just too much interruption if you want to quickly share something. The tipping point for us to actually build this open source tool came via an interaction from one of our day jobs. A third party provider sent a screen recording full of confidential information and to make things worse, all of it was uploaded by them to a different third party service. We strongly believe that information like this should stay within a company, ideally on infrastructure that they control themselves. Having a fully integrated open source solution is the best way to go for this. Our goal with this first public release is to gather feedback. The critical code paths are working, but it is still a bit rough to use. We deliberately cut out all non-essential features, but have a clear roadmap on what we want to release this year. There are a couple of known issues like audio glitches, non-working videos in Safari and crashing binaries that we hope to fix in the coming weeks. Later this year, we plan on releasing a cloud hosted version of Sorbay that would let you connect your own S3 storage provider. Additionally, we will be releasing an on-prem option focused on features for enterprises (SSO, RBAC, compliance). Both the Sorbay Client and the backend service are completely open source. For licensing we choose the AGPLv3 throughout the stack. The client is built with Vue.js on top of Electron. The use of Electron might be a bit controversial here on Hackernews but given the resources we currently have that was the only way that allowed us to get a working client out on all major platforms. The backend service is realized with Django. We use Keycloak for authentication and Minio for S3 compatible storage. All of this is run alongside Postgres and Redis, running on Docker containers which are managed by Docker Compose. We invite you to try Sorbay for yourself and join us on our issue tracker[1][2], Slack channel[3] or here on HN. Thanks for checking out Sorbay! [1]: https://ift.tt/TAjLas0 [2]: https://ift.tt/anJfI56 [3]: https://ift.tt/nr7vRkX... https://sorbay.io/ March 6, 2023 at 09:35PM

Show HN: OpenBB Terminal – Investment research for everyone https://ift.tt/L0AiCsK

Show HN: OpenBB Terminal – Investment research for everyone https://ift.tt/i3nuqhz March 5, 2023 at 03:34PM