<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Twitter on ads' corner</title><link>https://andreas.scherbaum.la/tags/twitter/</link><description>Recent content in Twitter on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 02 Mar 2023 18:21:00 +0100</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/twitter/index.xml" rel="self" type="application/rss+xml"/><item><title>Dynamic content in static websites in Hugo</title><link>https://andreas.scherbaum.la/post/2023-03-02_dynamic-content-in-static-websites-in-hugo/</link><pubDate>Thu, 02 Mar 2023 18:21:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2023-03-02_dynamic-content-in-static-websites-in-hugo/</guid><description>&lt;p&gt;With people &lt;a href="https://andreas.scherbaum.la/post/2022-11-21_migration-from-twitter-to-mastodon/"&gt;moving away from &lt;em&gt;Twitter&lt;/em&gt;&lt;/a&gt;, mostly to &lt;em&gt;&lt;a href="https://joinmastodon.org/"&gt;Mastodon&lt;/a&gt;&lt;/em&gt;, discovering the new accounts became a problem.&lt;/p&gt;&#10;&lt;p&gt;For people in the &lt;em&gt;PostgreSQL&lt;/em&gt; community I created a &lt;a href="https://postgresql.life/social/"&gt;website&lt;/a&gt; which lists different social media accounts. This website is part of the &amp;ldquo;&lt;a href="https://postgresql.life/"&gt;PostgreSQL Person of the Week&lt;/a&gt;&amp;rdquo; interview project, however the data source is dynamic, and stored in a different repository. This allows me to keep the repository for the website private, but publish the data for the social media links - this data is public anyway. The interview repository is private, because who wants to see upcoming interviews anyway? ;-)&lt;/p&gt;</description></item><item><title>Migration from Twitter to Mastodon</title><link>https://andreas.scherbaum.la/post/2022-11-21_migration-from-twitter-to-mastodon/</link><pubDate>Mon, 21 Nov 2022 16:15:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2022-11-21_migration-from-twitter-to-mastodon/</guid><description>&lt;p&gt;Many people (I don’t like this phrase) are leaving &lt;em&gt;Twitter&lt;/em&gt; these days, and looking for a new social media home. One of these places is &lt;em&gt;Mastodon&lt;/em&gt;. This blog post aims to summarize the steps necessary for a migration, and includes pointers to websites which can help with said move.&lt;/p&gt;</description></item><item><title>Remove duplicates from Huginn event stream</title><link>https://andreas.scherbaum.la/post/2020-10-21_remove-duplicates-from-huginn-event-stream/</link><pubDate>Wed, 21 Oct 2020 17:25:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2020-10-21_remove-duplicates-from-huginn-event-stream/</guid><description>&lt;p&gt;One of the things I&amp;rsquo;m using &lt;a href="https://github.com/huginn/huginn"&gt;Huginn&lt;/a&gt; for is monitoring for &lt;em&gt;Twitter&lt;/em&gt; keywords. Some of them might appear in pairs, as example people like to tag Tweets about &lt;a href="https://www.postgresql.org/"&gt;PostgreSQL&lt;/a&gt; with both &lt;a href="https://twitter.com/search?q=%23postgresql&amp;amp;src=typed_query&amp;amp;f=live"&gt;#postgresql&lt;/a&gt; and &lt;a href="https://twitter.com/search?q=%23postgres&amp;amp;src=typed_query&amp;amp;f=live"&gt;#postgres&lt;/a&gt;. When I was using &lt;a href="https://ifttt.com/"&gt;IFTTT&lt;/a&gt; this always created two emails, one for each hashtag. With &lt;em&gt;Huginn&lt;/em&gt; I can deduplicate the events, and only notify about the first occurrence.&lt;/p&gt;</description></item><item><title>Enable Huginn Twitter integration</title><link>https://andreas.scherbaum.la/post/2020-10-20_enable-huginn-twitter-integration/</link><pubDate>Tue, 20 Oct 2020 19:56:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2020-10-20_enable-huginn-twitter-integration/</guid><description>&lt;p&gt;&lt;a href="https://github.com/huginn/huginn"&gt;Huginn&lt;/a&gt; comes with a number of Twitter agents, but before they can be used you need to authenticate them. That process requires multiple steps, and they are not well documented.&lt;/p&gt;&#10;&lt;p&gt;The basics are described on the &amp;ldquo;&lt;a href="https://github.com/huginn/huginn/wiki/Configuring-OAuth-applications"&gt;Configuring OAuth applications&lt;/a&gt;&amp;rdquo; Wiki page.&lt;/p&gt;&#10;&lt;p&gt;For the Twitter integration one must know that you are using a single Twitter app for all users, but every &lt;em&gt;Huginn&lt;/em&gt; user can (and should) have this app authenticated against their own Twitter account. Therefore if you want to use multiple Twitter accounts in &lt;em&gt;Huginn&lt;/em&gt;, you need multiple &lt;em&gt;Huginn&lt;/em&gt; users.&lt;/p&gt;</description></item><item><title>Huginn: Filter Retweets</title><link>https://andreas.scherbaum.la/post/2020-10-11_huginn-filter-retweets/</link><pubDate>Sun, 11 Oct 2020 23:23:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2020-10-11_huginn-filter-retweets/</guid><description>&lt;p&gt;A while ago I started using &lt;a href="https://en.wikipedia.org/wiki/Hugin_(software)"&gt;Huginn&lt;/a&gt;, as a replacement for &lt;em&gt;IFTTT&lt;/em&gt;. That&amp;rsquo;s going quite well. &lt;em&gt;Huginn&lt;/em&gt; offers more features, integrations, and especially your chains (scenarios) can be as complex as you wish. &lt;em&gt;IFTTT&lt;/em&gt; is quite limited in this area.&lt;/p&gt;&#10;&lt;p&gt;I use the &lt;a href="https://huginnio.herokuapp.com/agents#TwitterSearchAgent"&gt;Twitter integration&lt;/a&gt; to find certain Tweets. Now this does not only find &lt;a href="https://en.wikipedia.org/wiki/Twitter#Tweets"&gt;native Tweets&lt;/a&gt;, but also finds every &lt;a href="https://en.wikipedia.org/wiki/Twitter#Hashtags,_usernames,_retweets_and_replies"&gt;Retweet&lt;/a&gt; made for a native Tweet. Obviously I am not interested in duplicate content.&lt;/p&gt;&#10;&lt;p&gt;&lt;em&gt;Huginn&lt;/em&gt; offers a way to filter out Retweets.&lt;/p&gt;</description></item></channel></rss>