Загрузка видео...

Не удалось загрузить видео

На главную

introducing Join Repo: easily invite users to your private GitHub repos 🚀 useful if you're selling a boilerplate/library 🤑 make a page & protect it with: 🍋 Lemon Squeezy license 🍬 Gumroad license 🔑 password when user redeems, they get added as a member to the repo/org 🤝

38,358 просмотров • 2 лет назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

CONFIRMED 🚨 Yesterday I shared a Contractor exposing illegals use a loophole to be able to get paid for working in America This woman confirms her illegal dad used this SAME LOOPHOLE to get an American drivers license and to work This woman’s dad was an illegal and got deported. He had a drivers license. One of her commenters asked how he had a drivers license if he was illegal, she responds: “So another fact that a lot of people don't know is with the ITIN number that you get from the IRS, you're able, you are able to get a privileged driver license from the DMV. So you would just have to have your, you know, identification from Mexico, your ID from Mexico, your birth certificate, your ITIN number, things like that, and you'd be able to get that privilege driver license. That's how people get it.” “So that's how that's done is the ITIN number, you can look it up, and the privilege driver license that immigrants get with the ITIN number.” How many people ILLEGALLY voted with these? - Illegals get an Individual Taxpayer Identification Number from The IRS - Have their foreign documents - They get a drivers license it’s that easy This also confirms what the Florida contractor was saying, this is the same process illegals use to get paid in America - Illegals are not required to be citizens or have any legal status to form an LLC in America - They just need to apply for an ITIN number from the IRS - All you need for the ITIN number is a foreign birth certificate or foreign identification documents They do this quick, simply loophole and illegals can then get paid to work in America

Wall Street Apes

138,891 просмотров • 1 год назад

The number one question I get in the Claude Code / Cowork Community: "how do I share my Cowork skills with my team?" Here's the problem. You build a great skill. You zip it up. You drop it in Slack. Your teammate downloads it, uploads it, and maybe it works. Maybe they upload it wrong. Maybe you update the skill next week and nobody gets the new version. You're now maintaining skills through chat messages and hoping for the best. That doesn't scale. I just put out a video breaking down the three methods I've tested for sharing skills and plugins across a team. From dead simple to fully synced. Method 1: Shared drive (Google Drive, SharePoint, etc). You put your skill files in a shared folder. Teammates download and upload them into Cowork. It works, but updates are manual and there's no version control. Method 2: Built-in sharing on Team and Enterprise plans. You can share any skill directly with a colleague or publish it to your org directory. When you update the skill, everyone gets the update automatically. This is the easiest path if you're on a paid plan. The catch: there's no approval workflow for org-wide sharing, so set a clear owner. Method 3: GitHub repo. This is what I use. Your entire Cowork workspace -- skills, plugins, claude.md, folder structure, project files -- lives in a private repo. Teammates clone it. When you push an update, they pull it. Everyone stays in sync. You get version history, access control, and a single source of truth. The GitHub method sounds technical, but it's really just two steps: clone the repo, point Cowork at the folder. I walk through the whole thing in the video, including how to use .gitignore to keep personal files (like your morning briefing) out of the shared repo. This works for Cowork, Claude Code, and Open Codex. The infrastructure is the same. Full video linked below. If you've found a different approach that works for your team, I want to hear about it. Comment or reply and let's figure out the best practices together.

JJ Englert

16,176 просмотров • 3 месяцев назад

New mass surveillance technology is being deployed in America, it will track Americans via Bluetooth connection from their devices If “you thought Flock was bad, something even more terrifying is being installed all over America. It's made by a defense contractor called Leonardo, and here's what it does” So the biggest problem with these LPRs, license plate readers like Flock, is that it needs to use a license plate to identify you This company has found a way around that They've made a device that can be installed next to any existing license plate reader that once it's installed, that next time they pull your license plate, it will pull all the unique Bluetooth identifiers from all the smart devices in your car. But it doesn’t stop there, it gets worse Once they have those devices, they link them to you via your license plate, and now they never need to scan your license plate again. These new sensors can be installed anywhere, and they can even see who's traveling with you It’s made by Leonardo DRS, they are a defense and technology company that works with U.S. military, law enforcement and intelligence agencies These devices are reportedly being deployed or tested in various US cities alongside existing LPR networks It’s called SignalTrace and it can be easily added onto any existing camera of their or Flock It’s described as “An advanced intelligence system that upgrades standard license plate readers to track people by their smart devices they carry, rather than just by their vehicles This is insane and should be federally banned. This is the surveillance state

Wall Street Apes

393,573 просмотров • 1 месяц назад

Toyota had a single access key sitting in a public GitHub repo. Nobody caught it for years. By the time it was found in 2022, customer data belonging to hundreds of thousands of people had been exposed the entire time. That’s not a hypothetical. That’s one hardcoded secret, forgotten in a repo, doing quiet damage for years. It’s called Infisical, and it exists because “just put it in a .env file” is how almost every credential leak starts. → Centralizes every API key, secret, and cert across dev, staging, and prod, with full versioning and point-in-time rollback → Scans 140+ secret types across your files, directories, and entire git history, the same kind of scanning that catches leaks like Toyota’s before they sit exposed for years → Agent Vault brokers your AI agents’ access to external APIs: the agent only ever sees a placeholder, the real secret gets injected at a proxy layer it never touches, so a prompt-injected agent can’t leak what it was never given → Honey tokens plant decoy credentials next to your real ones, so the second an attacker touches a fake key, your team gets an alert instead of a breach report → Full audit trail on every credential your team and your AI tools use, plus a private PKI to issue and manage certificates without a third-party CA GitGuardian tracked over 28 million new secrets leaked on public GitHub in 2025 alone. Most companies still find out the same way Toyota did: too late, by accident, years after the fact. MIT License (core). 12,700+ GitHub stars. Self-host free, unlimited users.

Harman

29,372 просмотров • 22 дней назад