So, anybody else massively inconvenienced when #Microsoft took away the usernames/timestamps from copy/paste in #Teams ?
Thanks to the magic of Gluing Other People’s Code Together™️, I’m happy to present a solution!
https://github.com/ajn142/Teams-Markdown-Exporter/tree/UserScript.
It’s a #userscript that can be loaded via TamperMonkey (or GreaseMonkey, untested) or pasted into the F12 Developer Tools console. When you press both shift keys, it begins scraping the open Teams chat starting at the oldest loaded message, and continuing until it can’t load any more messages, then formats as Markdown with a convenient download button.
=> More informations about this toot | More toots from ajn142@infosec.exchange
Fair warning, the README is still from the original project I forked, so it needs a bit of love to match the little I’ve done to extend the code, but that’s ok! With the magic of git, you can diff everything I’ve changed, and I’ll touch up the readme when I can.
=> More informations about this toot | More toots from ajn142@infosec.exchange
The relative lack of engagement tells me most of y’all are fortunate enough not to use Teams 😉
=> More informations about this toot | More toots from ajn142@infosec.exchange
@ajn142 Or have those extensions blocked. :-(
=> More informations about this toot | More toots from cR0w@infosec.exchange
@cR0w still works unless they take away your F12 Dev tools, it’s just more manual to have to add it to the console yourself.
=> More informations about this toot | More toots from ajn142@infosec.exchange
@ajn142 That's a lot of work to put into... Work. Wait, this is starting to sound like my review.
=> More informations about this toot | More toots from cR0w@infosec.exchange
@cR0w hahaha right there with you, but the alternative of synthesizing chat logs into tickets or having to manually add back the missing data is probably still more work xD
When MS made that change the amount of work I logged dropped by half, just because it was so much harder to log all the incidental bullshit that adds up to a significant part of my day.
=> More informations about this toot | More toots from ajn142@infosec.exchange
@ajn142 I'm with you. Those changes that probably seem small to companies like Microsoft make a huge difference to daily users and it generally feels like they DGAF. That really is the worst part.
=> More informations about this toot | More toots from cR0w@infosec.exchange
@cR0w my favorite part is that in the first month after the change, the feedback for “put them back” hit 60% of the total feedback for “throw them away” over like 2 years. Will MS reverse course? No, because that requires admitting you were wrong and didn’t understand your audience. Maybe after they rebrand Teams to Lync 365 Copilot for Enterprise Small Businesses.
=> More informations about this toot | More toots from ajn142@infosec.exchange
@ajn142 But but but New Teams
=> More informations about this toot | More toots from cR0w@infosec.exchange
@cR0w but YMWV, my partner also uses teams but never has anything longer than a screenshot can capture to log, while I’m a stream of consciousness chatter because if I write down what I’m doing in chat as I’m doing it, I d(id)n’t have to write it down again for the ticket.
=> More informations about this toot | More toots from ajn142@infosec.exchange
@ajn142 I guess it's a nice reminder that offering a setting switch somewhere is the nice way to act when modifying a widely use behavior.
That being said I personally considered the former behavior as a rude annoyance. More often than not, I was forced to copy paste text in a text editor to remove metadata before inserting them in wherever I wanted the actual useful text to go.
Hopefully Microsoft will manage to make copy/pasting of images not buggy in a future version...
=> More informations about this toot | More toots from marhoff@piaille.fr This content has been proxied by September (3851b).Proxy Information
text/gemini