unmus

Valentin

<p>Mathilda is trying to give you back some control of your tweets. The plugin copies your tweets from Twitter continuously and saves them into the WordPress database. The tweets can be displayed on the blog chronologically (but do not have to). Indeed, Twitter is also blogging, micro-blogging so to speak.</p>
<h4>Features</h4>
<ul>
<li>Copy your tweets back</li>
<li>Copy your tweeted images back</li>
<li>Display your tweets on the blog</li>
<li>Shows basic tweet statistics</li>
<li>Import your complete tweet history</li>
<li>Export your tweets as CSV file</li>
<li>Languague: English, German (only FrontEnd)</li>
</ul>
<h4>Live Demo</h4>
<p><a href="https://www.unmus.de/tweets/" rel="nofollow ugc">Here!</a></p>
<h3>Future of this Plugin</h3>
<p>As Twitter has decided to discontinue free access to the Twitter API in February 2023, I have stopped using Twitter, which also impacts the future of this plugin. For a longer period of time, the plugin was still able to execute API calls strangly enough. The plugin is using the Twitter API Standard v1.1. In the meantime Twitter became X and also free write access to v1.1 is still possible, but X has removed the required endpoint to fetch data. As consequence the core feature of the plugin is not working anymore, which is very sad. Independent from this, displaying of already received tweet data is still possible with this plugin. This feature will be kept alive until further notice. But further development in general is discontinued.</p>
<h3>Configuration</h3>
<ol>
<li><a href="https://dev.unmus.de/wp-content/uploads/Mathilda-Twitter-App-Registration.pdf" rel="nofollow ugc">Register</a> your Mathilda-Instance as Twitter-Application for API Access <a href="https://apps.twitter.com" rel="nofollow ugc">apps.twitter.com</a></li>
<li>Activate the plugin in WordPress</li>
<li>Maintain OAUTH Access Token, OAUTH Access Token Secret, Consumer Key, Consumer Secret and your Twitter Account in the settings</li>
<li>Run the initial load (Tools/Tweets)</li>
<li>Create a WordPress page (page slug must match mathilda slug)</li>
</ol>
<h3>Further Information</h3>
<h4>Supported Tweet Types</h4>
<p>Following tweet types are supported.</p>
<ul>
<li>140 Character Tweets</li>
<li>280 Character Tweets</li>
<li>Replys</li>
<li>Quotes</li>
</ul>
<h4>Supported Tweet Objects</h4>
<p>Following tweet objects are supported.</p>
<ul>
<li>Images</li>
<li>Hashtags</li>
<li>Links</li>
<li>Mentions</li>
<li>Galleries</li>
</ul>
<h4>Architecture</h4>
<p>Data storage and process logic is separated from the WordPress Framework. The toots are not saved in the table wp_posts. And TootPress is not registering a custom post type for the toots as well.</p>
<h4>CSS classes</h4>
<p>All mathilda UI elements can be addressed with individual CSS selectors. Please use your debugger to find the right classes.</p>
<h4>Data & Files</h4>
<p>Mathilda creates 4 folders within wp-content/uploads.</p>
<ul>
<li>mathilda-twitterapi = Archive of the Twitter API data</li>
<li>mathilda-images = Tweet Image Folder</li>
<li>mathilda-export = Export Directory </li>
<li>mathilda-import = Import Directory </li>
</ul>
<h4>wpCrons</h4>
<ul>
<li>Autoload Tweets (every 15 minutes, customizable)</li>
<li>Get Embedding Code from External Source (every 15 minutes, customizable)</li>
<li>Import Tweets (every Minute, if Import is running)</li>
</ul>
<h4>API</h4>
<p>WordPress Action: mathilda_tweets_updated (fired on tweet update)</p>
<h4>Related Links</h4>
<ul>
<li><a href="https://www.unmus.de/mathilda/" rel="nofollow ugc">Plugin Page (German)</a></li>
<li><a href="https://github.com/circuscode/mathilda" rel="nofollow ugc">Source Code @ GitHub</a></li>
</ul>
<h4>How to setup Mathilda?</h4>
<p><a href="https://www.unmus.de/mathilda/#screencast" rel="nofollow ugc">Screencast Video</a> (German)</p>
<h4>How to split large JSON files?</h4>
<p><a href="https://github.com/jhsu98/json-splitter" rel="nofollow ugc">JSON Splitter</a></p>


Mathilda

Mathilda copies your tweets from Twitter to WordPress.

k0nsl

<p>This plugin creates a short URL from the blog post permalink and stores it in the database. The URL is displayed below the blog post along with a link to twitter that passes the short URL on, if defined in the settings page. The plugin currently use knsl.net as the only service and stores the data in the database of knsl.net.</p>
<p>Plugin homepage: http://k0nsl.org/blog/k0nsl-short-urls-plugin/</p>
<p>For support use WordPress.org or devNET community forums: http://devnet-software.org/</p>
<p>Thanks!</p>


k0nsl Short URLs

Automatically shortens the blog post URL via knsl.net.

Mathilda vs k0nsl Short URLs