11–20 of 110 posts
I'm not going to do this on every refresh. I predict the market/ecossytem for guerrilla browser extensions targeting technical Slack users hotting up.
How hard would it be to run Slack in a special VM that brokered UI events from another application? I.e. the latest Slack would be running in a VM that made everything seem normal to it, but in reality the UI input and output would be supplied by another application which was presenting a "Slack Classic" interface to the actual user.
Wouldn't this make more sense as a tampermonkey / greasemonkey userscript? That way it loads automatically when you visit slack, no need to repeat anything. Disadvantage would be that you need a browser extension.
I'm often removing some "functionality" of a website I visit often (e.g. removing annoying chat boxes)
There are also repositories of scripts like GreasyFork (https://greasyfork.org). I suggest that maybe your script could be ported to Tampermonkey instead of distributing it as a bookmarklet.
Wouldn't this make more sense as a tampermonkey / greasemonkey userscript? That way it loads automatically when you visit slack, no need to repeat anything. Disadvantage would be that you need a browser extension.
I personally don't mind the new WYSIWYG. Doesn't get in the way much at all really. The only thing it's weird with I find is the code blocks, (previously 3 backticks, linebreak, code, linebreak, 3 backticks). Not a massive fan of how after 3 backticks it now puts an inline code format 'block', seems a bit weird.
Doing some security debugging on Slack desktop a year or so ago, I saw that you could easily open up a Chrome debugger port via CLI option to use with puppeteer/chromedp/etc. I haven't checked lately, but in theory it should be easy enough to connect to the debug port and run this short script to get the same benefit in the Electron app.