<?xml version="1.0" encoding="UTF-8" standalone="yes"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-us"><id>https://blog.pgxn.org/tags/twitter/</id><title>Twitter</title><updated>2023-02-18T22:53:46Z</updated><link rel="self" type="application/atom+xml" href="https://blog.pgxn.org/tags/twitter/feed.xml"/><link rel="alternate" type="text/html" href="https://blog.pgxn.org/tags/twitter/"/><author><name>The PGXN Maintainers</name></author><generator uri="https://gohugo.io/" version="0.167.0">Hugo</generator><entry><id>https://blog.pgxn.org/post/709635160523620352</id><title type="html">Hello Mastodon 🐘</title><link rel="alternate" type="text/html" href="https://blog.pgxn.org/2023/hello-mastodon/"/><updated>2026-10-07T16:13:48Z</updated><published>2023-02-18T22:53:46Z</published><author><name>David E. Wheeler</name></author><category scheme="https://blog.pgxn.org/tags" term="pgxn" label="PGXN"/><category scheme="https://blog.pgxn.org/tags" term="mastodon" label="Mastodon"/><category scheme="https://blog.pgxn.org/tags" term="twitter" label="Twitter"/><category scheme="https://blog.pgxn.org/tags" term="postgresql" label="PostgreSQL"/><category scheme="https://blog.pgxn.org/tags" term="listen/notify" label="LISTEN/NOTIFY"/><summary type="html"><![CDATA[<p>Hey all you Postgres people out there! Just wanted to make a quick post
regarding the PGXN <a href="https://twitter.com/pgxn">twitter bot</a>. In light of the recent announcements by
Twitter to charge for API use, I updated <a href="https://manager.pgxn.org">PGXN Manager</a> to also post to
Mastodon! If you&rsquo;re have joined the exodus to the Fediverse, give it a follow:</p>
<p><a href="https://mastodon.social/@pgxn">@pgxn@mastodon.social</a></p>
<p>In fact, I made some time to rewrite the notification bits of the manager
service. Previously there was just some code jammed into the upload controller
that would make an API call to Twitter. I ripped that out, and added a trigger
to the distributions table that posts a a <a href="https://www.postgresql.org/docs/current/sql-notify.html">LISTEN/NOTIFY</a> message.</p>]]></summary><content type="html" xml:base="https://blog.pgxn.org/" xml:space="preserve"><![CDATA[<p>Hey all you Postgres people out there! Just wanted to make a quick post
regarding the PGXN <a href="https://twitter.com/pgxn">twitter bot</a>. In light of the recent announcements by
Twitter to charge for API use, I updated <a href="https://manager.pgxn.org">PGXN Manager</a> to also post to
Mastodon! If you&rsquo;re have joined the exodus to the Fediverse, give it a follow:</p>
<p><a href="https://mastodon.social/@pgxn">@pgxn@mastodon.social</a></p>
<p>In fact, I made some time to rewrite the notification bits of the manager
service. Previously there was just some code jammed into the upload controller
that would make an API call to Twitter. I ripped that out, and added a trigger
to the distributions table that posts a a <a href="https://www.postgresql.org/docs/current/sql-notify.html">LISTEN/NOTIFY</a> message.</p>
<p>Then I wrote a little service that checks for new notifications every 5
seconds and dispatches to one mor more configured consumers. Today there are
just two: Twitter and Mastodon; in the future the might be more, especially
since I also added triggers to the users and mirrors tables, so we could have
the bot announce new mirrors and users. Should be pretty easy to do, might put
in the time in the next few weeks.</p>
<p>Oh, and for fun, I also added some emoji to the Mastodon posts, as well as the
abstract from new releases. Makes the messages more informative than on
Twitter. Of course, we could probably do the same, there, especially since the
post length was extended to 280 characters sometime after the original bot. I
have in mind to make a little library that allows the customization of
messages via configuration.</p>
]]></content></entry><entry><id>https://blog.pgxn.org/post/900982991</id><title type="html">Blog and Twitter</title><link rel="alternate" type="text/html" href="https://blog.pgxn.org/2010/blog-and-twitter/"/><updated>2026-10-07T16:13:48Z</updated><published>2010-08-04T03:01:00Z</published><author><name>David E. Wheeler</name></author><category scheme="https://blog.pgxn.org/tags" term="twitter" label="Twitter"/><category scheme="https://blog.pgxn.org/tags" term="news" label="News"/><category scheme="https://blog.pgxn.org/tags" term="announcement" label="Announcement"/><category scheme="https://blog.pgxn.org/tags" term="fundraising" label="Fundraising"/><summary type="html"><![CDATA[<p>I&rsquo;m pleased to announce two things:</p>
<ul>
<li>
<p><a href="https://blog.pgxn.org/">This blog</a>. Here I&rsquo;ll make regular posts as I develop <a href="https://pgxn.org/">PGXN</a>, and to keep
it up to date with regular operational updates and release announcements
(for extensions on PGXN, not just PGXN itself) once the site goes live.
Subscribe to <a href="https://blog.pgxn.org/rss">the feed</a> to stay up-to-date in your favorite reader.</p>
</li>
<li>
<p>The <a href="https://twitter.com/pgxn/">PGXN Twitter stream</a>. Follow along as our fundraising draws to an
exciting conclusion and development begins. Once the site is launched, new
extension releases will be tweeted, as well.</p>
</li>
</ul>]]></summary><content type="html" xml:base="https://blog.pgxn.org/" xml:space="preserve"><![CDATA[<p>I&rsquo;m pleased to announce two things:</p>
<ul>
<li>
<p><a href="https://blog.pgxn.org/">This blog</a>. Here I&rsquo;ll make regular posts as I develop <a href="https://pgxn.org/">PGXN</a>, and to keep
it up to date with regular operational updates and release announcements
(for extensions on PGXN, not just PGXN itself) once the site goes live.
Subscribe to <a href="https://blog.pgxn.org/rss">the feed</a> to stay up-to-date in your favorite reader.</p>
</li>
<li>
<p>The <a href="https://twitter.com/pgxn/">PGXN Twitter stream</a>. Follow along as our fundraising draws to an
exciting conclusion and development begins. Once the site is launched, new
extension releases will be tweeted, as well.</p>
</li>
</ul>
<p>Thank you for your support! More news to come, so stay tuned!</p>
]]></content></entry></feed>