I left Pennsylvania and the Eagles turned into a real football team..
Pottsville, PA.
Joined December 2017
- Tweets344
- Following345
- Followers116
- Likes1.3K
Jeff 🏈 retweeted
1/ We open-sourced the mail engine behind Nitrosend.
NitroMTA is a self-hosted delivery engine that speaks the Amazon SES v2 API. Keep your SES code, change the endpoint, send from your own IPs.
It's on Product Hunt today: producthunt.com/products/nit…
Jeff 🏈 retweeted
Campfire 🔥 a new #Omarchy theme, made for OmaFire by Wes Grimes @ncfrontiersman
Night lake, moonlight, pines, and a fire that really burns behind your windows, crackle included.
github.com/piermark/omarchy-…
Coming soon on OmarchyTV too.
Jeff 🏈 retweeted
I’ve accidentally turned our construction company into a group chat company that occasionally builds decks
volume has grown for us recently and it is causing things to break, so I’m hoping to tap into the hive mind here
our internal communications currently run through a WhatsApp community, with separate group chats for each department (sales, design, procurement, project management, finance, etc.) and each field crew
As we’ve grown, the volume of messages has become overwhelming. Important questions get buried, requests go unanswered, action items fall through the cracks, and nobody has a great way to track what’s outstanding.
it’s really hard for our field crews, who are actually building things all day rather than sitting at a computer monitoring messages
thinking the fundamental problem is that we’ve built our communication system around conversations rather than accountability and execution
So we’re rethinking the entire architecture…
Should communication be organized by department? By project? By crew? Some combination?
How do you make sure every request has an owner, every action item gets tracked, and nothing falls through the cracks, without creating an admin nightmare where everyone spends their day managing software instead of doing their jobs?
I’m less interested in debating Slack vs. WhatsApp vs. some project management tool, and more interested in understanding how to architect the underlying system
Surely this is a solved problem
Has anyone built or seen a really effective internal communication system for a growing, operationally complex business, especially one coordinating office and field employees? (construction or not)
I’d happily pay someone who’s solved this problem to help us figure it out (tag your friend)
Jeff 🏈 retweeted
🗓️ Weekly recap (Oct 24-Oct 31) for GitHub Copilot App
🚀 2 releases
🛠️ 124 improvements
126 features & enhancements in this release
Top features:
• Cloud automation forms now have a Suggest tools button that adds tools based on instructions while keeping existing selections ⚙️
• CSV and TSV files open as tables with sticky headers and a Table/Source toggle in the file viewer 📊
• Drop files onto the sidebar 'New' item to start a new session with them attached
• Agent merge options available from the merge status button in pull request views for easier PR review
• New sessions for enterprise-managed Copilot accounts show the managed default model in the model picker before first prompt
Enhancements:
• Resuming sessions with a long history is much faster, reducing load times significantly ⚡
• Large Mermaid diagrams no longer freeze the app during rendering
• Added a floating 'Scroll to bottom' button in full pull request Overview for quick access to latest activity
• Pin or unpin multiple sidebar sessions at once from context menu when several are selected
• Markdown files with YAML frontmatter show a source indicator in Live mode and a read-only table in Read mode
• Plugin install links now support including marketplace, allowing single-step plugin installation
• The Pinned section in Project Overview offers 'Archive merged PRs' to declutter pinned sessions
• Added and removed lines in diffs have stronger background colors for better visibility in low-contrast themes
• Agent merge action options remain editable even when off; must select at least one action before enabling
• Checklist items indent and outdent like bullet lists; Markdown tasks can be reordered with nested items by dragging
• Issue and pull request filters now show explicit Discard and Save buttons, plus Save as new view and Revert to default options
• Issue and pull request pages show responsive breadcrumbs that collapse into menus on narrow widths
• Resuming a session with disconnected WSL environment explains the issue and offers to reconnect instead of generic failure
• Selecting another PR from stacked PR menu opens it as a tab in the current session without creating or switching sessions
Bug fixes:
• New cloud automations now require write access to trigger; fixes save errors when repository policies are enforced
• Automation editor respects repository's read-access and trigger-scoped write policies to prevent errors
• Resuming a session no longer hangs on remote session setup failure; falls back to local resume
• Fixed session detach does not lose conversation when separating chats nested under workspaces or other chats
Misc:
• Improved docs and tooling around cloud automation and session management
• Updated UI components to support new table views and session management features
github.com/github/app/releas…
#GitHubCopilotApp
Jeff 🏈 retweeted
From the week's #openSUSE Planet blogs: Tumbleweed shiped Plasma 6.8.0, Qt 6.12.0, and kernel 7.2.11, PHP 8.5.12 patched critical “PHP2Shell” flaws, the 2026 Board Election kicked off, and Agama 25 added a web terminal for installs. #Linux news.opensuse.org/2026/10/30…
Jeff 🏈 retweeted
A good CLI saves more time than a good dashboard.
A dashboard is built for exploring and understanding. A CLI is built for doing the same task quickly, repeatedly, without needing to navigate anywhere first.
For a developer running the same deployment or checking dozens of times a week, that difference compounds fast, and a well-designed CLI often ends up saving far more time than the more polished interface built to look good in a demo.
Great tools aren't always the ones with the nicest interface. Sometimes they're the ones that get out of the way fastest.
Jeff 🏈 retweeted
🚀 PI NETWORK: SUBSCRIPTION – RECURRING PAYMENTS WITH PI
Pi is developing a Subscription mechanism that allows apps to offer subscription-based services and collect recurring payments, similar to Netflix and other membership platforms.
Subscription could unlock many new business models:
• AI applications with monthly subscription fees.
• Software services and online platforms.
• Digital content, education, and entertainment.
• Paid membership plans within Pi apps.
The key point: Pi could go beyond one-time payments and become a means of making recurring payments for services across the Web3 economy.
------
The mechanism has two main operations:
🔹 1. Subscribe – Customer Sign-up
• Customers select a service plan and confirm the transaction through Pi Wallet.
• The Smart Contract checks whether the service exists and meets the subscription requirements.
• If a free trial is available, customers can use the service before making their first payment.
• If there is no trial, the first subscription payment is collected immediately.
• The Contract records the subscription and establishes payment authorization for future billing cycles.
🔹 2. Process – Recurring Payment Collection
When a payment becomes due, the Merchant manually initiates the Process function using the App Wallet.
• Charged: Pi is successfully collected, and the next billing cycle is updated.
• Skipped: Accounts that are not yet due or have disabled auto-renewal are skipped.
• Failed: Payment cannot be collected, for example, because the customer has insufficient Pi or payment authorization is no longer valid.
If a payment fails, the Contract disables auto-renewal to prevent further collection attempts. The Merchant's application must notify the customer so they can resolve the issue.
🔹 3. Two Important GitHub Milestones
✅ PR #462 – Merged (October 8, 2026): Added Subscribe and Process interfaces to the Demo App for `core_team` users, integrating Pi Smart Contract subscription functions.
⏳ PR #465 – Open: Improves the user experience with a demo store called Pi Bakery Club, subscription plan selection, Pi Wallet confirmation, and a `/club` page for active subscribers.
github.com/pi-apps/demo/tree…
Jeff 🏈 retweeted
Packers win 27-19 over the Panthers to improve to 5-3 on the year
• Love 30/41, 288 yards, 3 TD, 1 INT
• Golden 7 catches for 79 yards
• Watson 8 catches for 113 yards (while going to the hospital and back)
5 sacks from the defense too, the good times keep rolling in Wisconsin #GoPackGo
Jeff 🏈 retweeted
Autonomous driving meets autonomous expense management.
Business travel just got easier.
Expensing a work ride shouldn’t take longer than the trip.
That’s why Waymo for Business now connects to @tryramp, so your trip receipt automatically matches to the charge.
Your ride can handle itself, and now so does your receipt.
Jeff 🏈 retweeted
Duo
-Tonka Hemingway gets pushed by the RG/RT combo
-Maxx Crosby gives ground to TE/TE combo
-Eric Stokes doesn't get off the WR's block
-Jeremy Chinn doesn't keep Corum on his inside shoulder
-17-yard gain
#Raiders
Jeff 🏈 retweeted
Clone any website with one command 😳
> Analyzes desktop + mobile design
> Extracts images, fonts & assets
> Rebuilds in clean Next.js
> Works with Claude Code, Cursor, Codex
Free + open source
37.3k stars
Repo: github.com/JCodesMore/ai-web…
Jeff 🏈 retweeted
Working with outside collaborators can add more work for a repo owner, from confirming access to changing permissions.
To keep up with manual housekeeping for one shared org, we decided to use Evergreen: a GitHub App built with native GitHub features.
The workflow 👇
github.blog/engineering/plat…
Jeff 🏈 retweeted
📢 A new Linux kernel vulnerability, tracked by Trend Micro’s Zero Day Initiative (ZDI) as ZDI-CAN-33367, is the same kind of bug as Dirty Frag and Fragnesia.
AlmaLinux 8, 9, and 10 are affected. Patched kernels are available for testing!
almalinux.org/blog/2026-10-2…
Jeff 🏈 retweeted
AI agents are starting to interact with crypto on their own. But how do we decide which wallets an autonomous agent should trust?
That’s where @zerufinance is getting interesting.
Their latest product update introduces zScreen as an MCP server, allowing AI coding tools like Claude Code and Cursor to screen wallet addresses, inspect risk verdicts, and trace fund flows without manually working through API documentation.
Think about the implications an agent could evaluate a wallet before interacting with it instead of blindly trusting an address.
This is a meaningful intersection of AI and onchain security. As autonomous agents gain more financial responsibilities, understanding wallet behavior could become a critical part of their decision making.
The next generation of AI needs more than intelligence. It needs a way to assess risk.
That’s a use case worth watching.
🤝 Paid partnership
Jeff 🏈 retweeted
The #Eagles are signing G/T Evan Neal, the former No. 7 overall pick out of Alabama.
Jeff 🏈 retweeted
"I'm just hoping when I go out there, we're up at half and the fans will be in a lot better mood."
Larry Fitzgerald talks his "Irish" goodbye and the excitement of returning to the Red Sea.
Jeff 🏈 retweeted
Interviewed Erik Allen Ford, co-founder of Buck Mason. We talked about building a company around nerdy menswear products, Erik's love for vintage, and why so many great heritage brands have lost their way.
pod.link/blamo/episode/NmUyY…