Jack

founder @

[Jack @JRKCodes]

@Railway Was impacted but seem to be seeing some recoveries

[Jack @JRKCodes]

@ecommilan This is why "label created" can do more damage than an actual delay. If the carrier mix changes but scan timing, promised transit windows, and exception messaging do not change with it, support gets buried and the review score starts eating margin.

[Jack @JRKCodes]

@SmallParcelGuy The blind spot is usually not the fuel surcharge itself, it is not knowing which orders created it. If accessorials are not visible by zone, carton profile, residential mix, and service overrides, teams renegotiate the contract without fixing the operation.

[Jack @JRKCodes]

@TCGsealed @jamiepine @TalhaMehar007 someone else will do it so why try type guy. Will never get anywhere thinking that way🤣

[Jack @JRKCodes]

@TalhaMehar007 @jamiepine Not seeing any contributions from you 🫥

Always the open source sideline bros expecting the most contributing the least

[Jamie Pine @jamiepine]

This is my take on the perfect AI assistant.

A Rust-based agentic operating system designed to scale for large Slack and Discord communities. The channel is the ambassador to the human. Branches think. Workers execute. Nothing ever blocks.

Meet Spacebot 🟣

The biggest issue with OpenClaw is when it's doing work, it can't talk to you. Spacebot's architecture fixes this by design the conversation layer never touches tools. It delegates thinking to branches and heavy tasks to workers, so it's always responsive even with 100 people talking at once.

Dump your memory files, notes, documents and chat histories into a folder — Spacebot turns them into structured memories automatically. Eight typed memory categories, graph associations, hybrid search. Not markdown files. Not vibes in a vector database.

Built-in @OpenCode workers for deep coding sessions. Browser automation. Brave web search. Cron jobs. A skill system compatible with your existing OpenClaw skills. And a gorgeous control UI at https://t.co/aAEbMp4LSh.

The cortex oversees the whole system — auditing memories, actioning goals and todos. You teach your Spacebot by talking to it. Structure and speed over config files and markdown.

Self-hosting is a single Rust binary. Or one-click cloud deploy at https://t.co/aAEbMp4LSh.

This is for teams, communities, and personal assistants. It will blow you away.

⭐️ https://t.co/H8pCoE9R4h

[Jack @JRKCodes]

Most WMS platforms lock you in—limited automations, restricted APIs, minimal room to customize. We built Cybership differently.
Our API was designed with one principle: if we can build it, so can you. With over 200 endpoints, you have the flexibility to customize everything

[Jack @JRKCodes]

@AWSSupport DM'd case ID

[Jack @JRKCodes]

Some new metrics on https://t.co/gQ0sPVYN6P to help brands and fulfillers alike understand their business better.

[Jack @JRKCodes]

@prisma Yeah haven't seen any improvement on executions or type performance improvements. Wasn't sure if it was just our codebase size or what. But the initial claims were quite crazy and set expectations high.

[Jack @JRKCodes]

@seskis Steaks included?😏

[Jack @JRKCodes]

More ShipHero chaos, just another day.

Our new customer who wants to burn through their minimum wants us to fulfill the orders we can.

But ShipHero is in the wild west once again, and they are fulfilling orders assigned to our app location, hilarious. Customer isn't happy.

[Jack @JRKCodes]

Shopify has app specific locations inventory, which is great for managing inventory for your app you don’t want anyone modifying manually

Until @weareshiphero’s poorly developed app decides to reset your apps inventory to 0. Our customer cannot wait to uninstall ShipHero’s app🙄

[Jack @JRKCodes]

@aaronrubin if you’re going to call me stupid, at least don’t delete it. Did you figure out how Shopify works half way through and get cold feet?

[Jack @JRKCodes]

Shopify has app specific locations inventory, which is great for managing inventory for your app you don’t want anyone modifying manually

Until @weareshiphero’s poorly developed app decides to reset your apps inventory to 0. Our customer cannot wait to uninstall ShipHero’s app🙄

[Jack @JRKCodes]

@Shopify And this means if you wanted to self fulfill (and maintain stock) alongside your 3PL, or transition 3pls with another software. You wouldn’t be able to😳

[Jack @JRKCodes]

For any Shopify nerds, we use Shopify fulfillment services, and they’re “app specific locations”. Not sure why a @Shopify app can modify another apps inventory. I feel like that’s the whole point of stocking inventory at an app specific location so no one can mess with your stock

[Jack @JRKCodes]

https://t.co/gQ0sPVZkWn Reporting just released! shadcn charts making things too easy

[jeff annaraj @jeffannaraj]

Cybership this year:
0->$X MM ARR
100->70k orders per month (ATH)
1->20 employees
1k->12k sqft
Full warehouse management platform.
Only the beginning 🚀

Thanks to @ChadCarleton, @SchroedsBiz @ShipSmarter and clients our for their incredible advice and insight into fulfillment and 3PL.

[Jack @JRKCodes]

we building @cybership_io

[Jack @JRKCodes]

"not using the GitHub fork function looks shady, usually that's a sign of people not caring about the previous fork"

Very rich, coming from Peer RICH who cannot even properly fork a codebase which he took over and originally gave no attribution.

https://t.co/NJ0HzIAjM2

[Peer Richelsen @peer_rich]

a couple takes on the "vscode continue pearAI YC drama"

for context:
- i did YC in W19, big fan of YC
- i run a large OSS project https://t.co/svpVpBOIvu
- i have the most respect for @garrytan, who also signed my O1 petition 💪

my takes:
- i agree with my cofounder @pumfleet on this, its a bad look for everyone involved

- i give the benefit of the doubt to @garrytan and will wait for more context

- i don't think funding forks is a winning strategy, i have yet to see a fork be more successful than the initial steward (see bitcoin cash, ...)

- i only see a reason to fund forks when the initial steward is widely unpopular or shuts down (i.e. RomeJs becoming biomeJS)

- as of today i don't see how VScode needs a fork, and my POV is all these cute AI extensions are in-fact VSCode extensions (i use supermaven A LOT – big fan)

- funding a fork of a fork is next-level uncertainty

- to make it in open source, you need strong open source ethics. you are looking to build a community. starting day 1 saying "its ours now!" is crazy disrespectful, even if the fork is technically legal its highly unethical and i don't think that's a great start to find PMF among developers (who are also working in open source btw.)

- i am not sure if YC actually did their due diligence on this knowing its a fork. the founder profile looks very strong, there is a chance they applied with something else or whether it was a fork or not was never discussed

- $500k is a preseed investment and my honest guess is that this team of founders might work on something else very soon if this doesn't work out. clearly forking a popular project shows a lot of signs of "taking shortcuts without much buy-in"

- on the other hand, maybe VScode has reached "infrastructure level" where its just too big to rebuild, similar to Chromium. Every browser today out there is a chromium fork and we don't seem to care this much

- "build with continue" is straight-up WILD to claim when it's really just a fork with a CMD+F replace function

- AGPLv3 helps a lot to mitigate a lot of this

- not using the GitHub fork function looks shady, usually that's a sign of people not caring about the previous fork, not contributing back (no obligation but always nice). this also causes the history to die, old contributors are left-out of the git history and credits

- and lastly: if you wanna make it in open source build something yourself – only fork if the initial steward is not trustworthy anymore or shuts down

building is always more dope than forking 🥳