I've been building a PR-review tool and it's ready for real repos — would love a few of you to try it. It's called RepoSignal. The short version: it learns from your repo's own history which kinds of changes tend to cause problems later, and when a new PR opens it leaves a comment telling you whether this one fits that pattern — so you know where to spend your review attention. What I think makes it worth a look: - It's trained on your repo specifically, not generic rules or other people's code - It's honest about its own limits — if your repo doesn't have enough history for a reliable signal yet, it says so instead of pretending 📊 - You get a security + dependency scan on day one, so it's useful while it learns Free to try — public repos are free, full product, no card required. Setup is ~2 minutes — install the GitHub App, pick a repo, open a PR. One thing worth knowing: it gets better with mileage. Repos with a longer commit history (500+ commits) give it the most to work with — so if you've got an older, active repo, that's the ideal test. 📈 If you try it, I'd genuinely appreciate honest feedback — useful, annoying, confusing, anything. That's what I'm after at this stage. 👉 reposignal.io

We had a crappy first impression. Immediately several links were identified as broken in the repo. but they are all fixed and I would like to reintroduce Citadel. If you are into cyber security please take a look at this post quantum crypto implementation. I Don't have the funds for outside audits and validation yet but it feels complete from my standpoint. I would love it if any of you could try and break it. It would mean the world to me. I know that is a big ask so I'm not expecting much. I'm just so excited to have this off my plate. I've been obsessing over it for so long and now I can finally move on to other things. The crazy part is nobody asked me for it. I just heard about it and couldn't stop touching it. Criticism desired, look it over and light me up. really it would have taken me another at months with the ICM. I was doing insane amounts of iterating back and forth with all my Ai. This group brought to a different way of approaching my time with AI and we just started blasting through the work. "The post-quantum mandate. The migration to post-quantum cryptography is no longer optional for a growing set of systems. A future quantum computer would break the RSA and elliptic-curve algorithms that protect most data today, and because an attacker can record encrypted data now and decrypt it later, the risk already applies to anything that must stay secret for years. The United States has set firm timelines in response. National Security Memorandum 10 (2022) and the NSA's Commercial National Security Algorithm Suite 2.0 require National Security Systems and their vendors to move to quantum-resistant algorithms on a staged schedule, with most technology categories reaching exclusive use between 2030 and 2033 and full transition by 2035. The Quantum Computing Cybersecurity Preparedness Act (Public Law 117-260, 2022) and OMB Memorandum M-23-02 place parallel inventory-and-migration obligations on federal civilian agencies. Who it reaches, and the sources. For everyone else the direction is the same, even where it is not yet law: CISA, the NSA, and NIST jointly urge all organizations, and critical infrastructure in particular, to begin migrating now, and NIST's transition guidance (IR 8547) schedules the classical public-key algorithms for deprecation after 2030 and disallowance after 2035. The replacement standards are already published: ML-KEM in FIPS 203, ML-DSA in FIPS 204, and SLH-DSA in FIPS 205, all finalized in August 2024. Together these define what to migrate to and by when: the algorithms in FIPS 203/204/205, the deadlines in CNSA 2.0 and NIST IR 8547, and the mandates in NSM-10, OMB M-23-02, and Public Law 117-260."

@Carla Bosteder made a post about us all sharing and collaborating instead hoarding. A lot of people here share a lot of great works. But, I am guilty of keeping secrets and I was moved by the argument Carla made for the value of sharing more. There are so many genuinely powerful minds in these threads that I have been learning from, I feel I need to be more forthcoming. SO... I have decided to share my scrapyard, it is a library of modular components I've been putting together to help me build without always starting from scratch. It is probably very rudimentary compared to what some of you have but I'm sharing anyways. Do what you can with it and if you have better parts, I would love to see them. Lets work together like Voltron, Power Rangers, Bad News Bears, The Goonies and any other team you can think of. Carla post: https://www.skool.com/cliefnotes/what-if-sharing-is-the-advantage My Repo: https://github.com/mrcord77/scrapyard

Cloudflare dropped a browser made for AI agents instead of people. No tabs, no themes, no pixels. Just the parts a machine actually reads, running in their cloud on a fraction of the compute. Free beta, built in 12 weeks. Now I ain't the sharpest tool in the shed, but this smells exactly like the paper Jake dropped this morning in the VIP lounge. His numbers said: stop making the model read the whole history when 3 files answer the question, and the cost drops 95%. Cloudflare is saying: stop making the browser draw the whole page when the agent only reads the text, and the compute collapses. Same lesson twice in 1 day, from a research paper and the company that sits in front of a massive chunk of the internet: stop paying for what the machine doesn't consume. That's the folder thing. That's the whole reason the ICM stuff works. Feed the machine only what the step needs. Am I reading this right, or am I connecting dots that ain't there? https://techcrunch.com/2026/08/07/cloudflare-launches-kitesurf-a-browser-built-for-ai-agents/ The sharper tools in this shed will know better than me. I'm still learning what half everyone is saying. It's like a foreign language to me still and I can kinda' get around town and order a meal, but once it's a full blown conversation ... I'm a deer in headlights.

I built another workspace, this one answers security questionnaires. It takes the questionnaire a company sends, SIG, CAIQ v4, Google VSAQ, or an Excel file, and turns it into a question list. Every answer cites a source in the approved content, and what it can't cover gets flagged. I review the gaps myself before anything goes out, and the checks that run are plain deterministic scripts. I ran the whole thing end to end against a practice questionnaire, 30 real questions, with a real company trust page as the content. I have not run it for a real company yet. The company facts are still not set and the content folder has nothing in it. Right now I do not have a way of getting it in front of others to use, so I don't know if there is value in it. I was just looking into whether this is a good topic. Has anyone here had to answer one of these for a company? Do you think there is value in it? How do you answer them now?