Hacker News new | past | comments | ask | show | jobs | submit login

Fuck slack. They're hostile to user choice and preferences, pushing a one-size-fits all attitude. Communication preferences are extremely personal and must be respected.

I have a custom ssl proxy to intercept slack.com and modify their api, eliminating what I believe to be dark patterns. Some things I do:

* Force dark mode always

* Disable favicon.ico updating when there are notifications in DnD

* Group channels based on name prefix (stealing behavior from an add-on)

* Ignore bots

It's hard to keep this up to date so it's not really that robust. If I open source it I know I'll get legal pressure from slack, not to mention they'll probably try to block it.




I’m just curious about the ssl proxy + api modification part in general - got a ref for that for a more mundane application?


I'm using something I wrote for work. Basic steps:

- Create and trust a CA

- Issue SSL for api.slack.com

- Deploy something like https://github.com/chimurai/http-proxy-middleware/issues/97 with your code to modify the response body

- Strip HPKP headers, if present

- Strip CAA in DNS, if present




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: