Hello all! I had an account on the old forums but it looks like they have since been deleted. Very sad! I love phpBB and vBulletin and it’s sad to see the internet migrating away from forums.
I had a partially working version of this plugin but it was very fragile because it required updating the OpenSSL version whenever there was a TeamSpeak 3 update. Instead, I’m now using SChannel which should make the plugin more resilient. I started working on this plugin in 2011 but development stymied on it in 2017 and I did not receive the support I needed in order to finish it. Finally, after 15 years it is now complete and working.
Look at this Website Preview (forgive the pun):
Isn’t it ridiculous that in neither TeamSpeak 3, nor TeamSpeak 6 even, that we have website previews?
That is the problem that my plugin solves! My plugin takes URLs and provides their title just like Discord, WhatsApp, text messaging… basically every other modern app does. Download it here:
Once the TeamSpeak 6 API is released, I will be porting this plugin to TeamSpeak 6 unless it becomes default functionality.
Here are the VirusTotal links for each architecture (is 32-bit TeamSpeak 3 still supported anymore?) :
As a long time proponent of implementing client side OGP parsing and embedding I really like this plugin. I would only prefer the binary to be built and published via a GitHub action. This would also allow you to publish the plugin for Linux and MacOS relatively easily.
If you want I’d be happy to write a PR for that.
As long as you don’t mind contributing under the MIT license, that sounds great! Please do.
It’s funny that you suggest GitHub actions, as that was the first thing I did in my Software Engineering Studio capstone class that I just finished last month. It was easy to “set it and forget it” because I was supposed to add code coverage to it for the final release and forgot. Should the binary also be built into a .ts3_plugin file? I assumed that was the standard for posting here.
Having a Linux/macOS build for reference would be very convenient. I already have my next TeamSpeak 3 plugin in the works that I tried last decade and never got off the ground. I need to use my Ubuntu box to test it though since it requires two users to be running the same plugin, so I look forward to reading your code.
Sooooo, things might have gotten slightly out of hand, but there is a PR.
I just noticed that the message is sent twice, once the original and once the edited one. Returning 1 in the onMessageReceived handler only hides the message on your end but still sends it. There is sadly no way in the plugin API to prevent this.