Show HN: Related Website Finder Experiment Thingy https://ift.tt/OxkXipB

Show HN: Related Website Finder Experiment Thingy Been messing with cosine similarity and decided to try calculating nearest neighbors over the entire link graph for the marginalia search engine. Turns out that you can just bruteforce that in a day or two. And the results are pretty good. One drawback is that depending on if you're looking at an older website, a lot of the links are dead. The deduplication isn't great either. https://ift.tt/Wpy4QEl October 9, 2022 at 10:52PM

Show HN: Simplepdf.eu – a browser-based PDF annotator / editor https://ift.tt/duSCHxj

Show HN: Simplepdf.eu – a browser-based PDF annotator / editor Hi HN! I've been working on SimplePDF to solve a problem I encounter weekly: filling out non-editable PDFs [1] --- # About SimplePDF - The documents you load, edit, fill never see the light of my server, everything is processed locally – no remote uploading anything. This includes the PDF generation. - There are no analytics / third party tracking your every move (I do collect usage data, but it's fully anonymous and processed and stored on my server): therefore no annoying cookie banner. You can read more on the Privacy Policy [2] - If someone before you has filled the same document, upon opening it you'll see fields already set, ready to be filled-in, think crowd-sourced fields positioning – saving you time and effort. --- # How does the crowd-sourced positioning of fields work? When a document is loaded in your browser, a fingerprint of the document binary is made, and sent to the server. The document table consists of: document_id, fingerprint and created_at. As soon as you start editing a document, a template is created, containing metadata about the fields (x, y, width, height, type of field, background color...) that is then tied to this document you created. Once you save, this template gets sent to the server. The template table consists of: template_id, document_id, fields (the metadata) as well as created_by_customer_id if you're a customer. As a result, someone else on the other side of the world opening the same document will see the fields you positioned already there – you just saved them the 5min it took you to position them. --- # What's the tech stack of SimplePDF? - NextJS on the frontend - Koa with GraphQL on the backend - Postgres (Managed Database on Digital Ocean) - A 10€ droplet on Digital Ocean --- If you have any questions, comments or feedback (good or bad), I'm all ears! --- [1] The assignments my estonian teacher gives me are usually scanned documents that do not have any editable fields in them. [2] https://ift.tt/xYR9IG2 https://simplePDF.eu October 9, 2022 at 10:17PM

Show HN: BlockTalk – Banter about what your friends are doing on Web3 https://ift.tt/WFXztVk

Show HN: BlockTalk – Banter about what your friends are doing on Web3 Hey HN, I’m Kamil and one of the two people working on BlockTalk. BlockTalk is going into public beta today! (We're also on Product Hunt, come check us out!) We previously posted about this project under the name “WalletWatch” in a Show HN about 3 weeks ago, and have since integrated your feedback to make it better [1] [problem] As we were trying to see how our friends were using crypto, we noticed that other products were either too complex or only let us passively view what our friends were doing. [solution] BlockTalk is a social network centered around Ethereum transactions. You can easily see, understand, like, and comment on the Ethereum transactions of anyone on the platform. We don’t ask for your email or password, and instead authenticate by asking users to sign a transaction with their Ethereum wallet; we ask for usernames to give a more familiar and user-friendly experience for people that haven’t purchased ENS or other crypto domain names. At the moment, we’re storing user data in Firestore instead of on-chain because the current decentralized channels are too expensive or slow. This also has the added benefit of making the app completely free to use. [what’s changed] Since our last post, we improved the UI/UX, made transactions more understandable, made the app compatible with all viewports, and now don’t require you to create an account to get a feel for the app. [ask] We’d love any feedback you all have! My e-mail is kamil@fwd.exchange if you want to contact us about anything related to the project :) P.S. here's a very old demo of a prototype from a while back [2] [1] https://ift.tt/hoxTuPs [2] https://youtu.be/xhajqKq4G9Y https://ift.tt/eZLoB6W October 9, 2022 at 08:50PM

Show HN: Building a Git teaching tool that runs Git in the browser https://ift.tt/cmSMwyi

Show HN: Building a Git teaching tool that runs Git in the browser Repo: https://ift.tt/F6Uy4HY Harmony was born as a tool to create and/or modify local files, on the fly, in your browser. Few weeks ago I decided to try to implement a sort of version control system in it. I think it would be cool one day to either use it for personal use or to teach Git concepts in a sandboxed area. Harmony is powered by web assembly and it runs all the git related stuff in-memory. In this release I brought an initial support for directories and the possibility to checkout to a particular commit https://ift.tt/j6BpQSm October 9, 2022 at 07:10PM

Show HN: If Spotify and Tinder Had a Baby https://ift.tt/ktQHgXv

Show HN: If Spotify and Tinder Had a Baby https://ift.tt/R6wHUrM October 9, 2022 at 11:38AM

Show HN: Simple Checklists for Digital Security https://ift.tt/FajnWDu

Show HN: Simple Checklists for Digital Security I developed some simple checklists to help stop me and my family from getting our accounts or IDs hacked. I turned it into a product. Also on Product Hunt: https://ift.tt/sgSzelk https://ift.tt/7Hjl6xu October 9, 2022 at 12:43AM

Show HN: Reflame – Deploy your React web apps in milliseconds https://ift.tt/CQuxELl

Show HN: Reflame – Deploy your React web apps in milliseconds Hi HN! I've been working on Reflame since I quit my job at Brex last year, excited to finally open it up for everybody to try out! Here's a demo: https://www.youtube.com/watch?v=xZ4KyfGbUFA Reflame deploys client-rendered React web apps instantly, to previews and to production. In concrete wall-clock terms, deploys generally take: - ~50-500ms from our VSCode extension - ~500-3000ms from our GitHub app (Jump to this comment ( https://ift.tt/eB4PNSv ) for what makes Reflame so fast) The Reflame GitHub App automatically deploys default branches to production, and other branches to previews. If you've used Netlify/Vercel's GitHub apps, you should feel right at home. The difference is it’s multiple orders of magnitudes faster. Fast enough that you'll probably never see an in-progress deploy on GitHub ever again , only ready-to-go preview/production links. No more having to babysit builds or having to context switch to and from other tasks before being able to see our changes deployed in previews or production. Previewing, sharing, and even shipping, can now become part of the so-called inner loop, giving us the superpower to stay in flow state for much longer. The Reflame VSCode extension is yet another order of magnitude faster than even the GitHub App. It was designed to offer an experience that can rival local development workflows in both speed and ergonomics, while addressing many of local dev's limitations around collaboration and production-parity. Every time we make a change (e.g. by saving a file), the extension will deploy that change (in ~50-500ms) to a "Live Preview", and will immediately update the app in our browsers to reflect that change. Live Previews can operate in one of two modes: - Development mode delivers updates through React Fast Refresh, offering the familiar state-preserving instant feedback loop we know and love from local development workflows. - Production mode delivers updates by triggering a full browser reload on every change, and in exchange for this extra bit of friction, we get to develop against a byte-identical version of the fully optimized production deployment that customers will see once we ship, with a tighter feedback loop than was ever possible before. Live Previews deliver updates over the internet, meaning we can effortlessly test out our changes on multiple devices simultaneously, and show our changes to anyone in the world, just by sharing a Live Preview link, all while having our updates reflected automatically across all connected devices in real-time (with live reload or React Fast Refresh over the internet ). Being able to ship quickly is valuable on its own, but Reflame's true north star has always been to enable customers to ship quickly with confidence . One way Reflame helps customers ship with more confidence today is by making previews with full production-parity available at every step of the development process. Previews in Reflame are accessible at the exact same URL customers will use to access the production deployment, instead of at a different subdomain for each preview (i.e. every preview is accessed through https://reflame.app instead of at https://ift.tt/AtFHblU ). Behind the scenes, this is implemented using session cookies that our CDN will check to determine which version of the app to serve. This is only the tip of the iceberg. We have some really exciting prototypes around testing and typechecking that we've been exploring that could allow us to ship with even more confidence without ever slowing us down . If any of this sounds interesting for the apps you're building or planning to build (taking into account this comment ( https://ift.tt/TMxHIYa ) below describing what Reflame is not well suited for), please sign up and give it a try! I can't wait to see what you’ll build with it! :) https://ift.tt/6fg0Ehp October 8, 2022 at 10:40PM