@jgmac1106 I think I managed to fix the idno/Twitter issue by updating the tmhOAuth library to the latest version and also updating the cacert.pem. Please see https://
After quite the rush today through #Known 's theme customization and CSS styling, I'm finally settling with the current design. In the meantime I also fixed the Known #Bookmark plugin form - on my own instance - to allow for selecting if a bookmark is a "Like" or a "Re-post". Will send a #PR on #GitHub to fix [this Issue](https://
Gave up on integrating the #idnoTwitter plugin for my #Known site, even-though I solved the previous #issue with it after correctly setting the URL. For some reason, not shown in the error logs, my Web host does not seem to be able to send the oAuth connect requests. It fails with this error message "'Your Twitter credentials could not be saved." and the code ``0``, which means the *tmhOAuth* library could not connect to #Twitter 's API. Sticking with Brid.gy for now. Additionally, the tmhOAuth library does not seem very much maintained anymore. It's last release was in February 2013.
#Fixed the #issue on my #Known site where I had wrongly configured the ``url`` in the ``config.ini`` file.
My web server error is full of these useful and informative messages:
> Backend log: Known (social.johanbove.info): warning - Base URL has defaulted to "/" because Known was unable to detect your server name. This may be because you're loading Known via a script. Try setting url="http://yourdomain.com/" in your config.ini to remove this message\n, referer: https://