nwparker

I enjoyed seeing all the 'privacy notice' emails in my inbox today thanks to this

FWIW this is why we built Orca (https://github.com/stablyai/orca), we beleive in the TUI world but just want a GUI wrapper to help bridge the chaos

Thanks! I actually did check it out but was worried by number of issues and the last release being in Dec (ref: https://github.com/coder/ghostty-web/issues/137 )

Crossing my fingers for a more official libghostty soon for the web! I know Hashimoto is working on it.

Oh whoops. Fixed!

`gh` CLI

I wouldn't say change your workflow if you're happy, but I'll answer anyhow!

I also actually tried cmux, but I didn't like they way it did tabs. I like my tabs top-level and not inside panes (but I realize this is a personal choice).

We also do good GH native integrations (linking PRs, showing statuses, and linking GH issues). We also do AI status indicator even for non-focused terminal panes. You can also manually mark a worktree as 'unread' (kind of like a star in Gmail) In addition Orca has a built in file viewer, search, git diff viewer (see all changes like VsCode does)

Also cmux is Mac only (doesn't matter for you, but for others)

So tl;dr -- alot of small things. But those build up for me in a tool that I basically find myself living in

^ I updated the post to reflect some of these

Slack Connect just has a network effect, TBH. It's hard to move away.

Yeah you're definitely right, it's there. It's just an API they document so it's subject to change etc (which presents some challenges)

There's a few open issues/PRs that I'm working on getting in! Feel free to drop any request there (it's the best way for me to track it).

For UNREAD messages... Sadly, I'm not sure that Slack has an official API for that. There may be an "unofficial" API there that we could discover, but I'm hesitant for adding support there. With that being said, it's not that I wouldn't entertain the idea (it would be REALLY useful) but it would require a bit more thought.

I don't use Slack Grid, but if you open an issue I'm more than happy to work with you on it!

You could ask it to convert the names (and it would), since it uses the slack internal userIds

But I will add a flag to do for `slack message read/list`, since it makes sense.

I think the exploit you demonstrate in your video is pretty reasonable/realistic. There's plenty of times where I eye-ball a repo in the GitHub UI before downloading it since I want to know what's happening under the hood for trust reasons. And this def throws a little bit of a wrench into that process.