<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Daniel Sieradski on Medium]]></title>
        <description><![CDATA[Stories by Daniel Sieradski on Medium]]></description>
        <link>https://medium.com/@sieradski?source=rss-eae7d2c9dcc5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JDdsG79cD46InA3JpZUgyA.png</url>
            <title>Stories by Daniel Sieradski on Medium</title>
            <link>https://medium.com/@sieradski?source=rss-eae7d2c9dcc5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:35:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sieradski/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[I’m Breaking Up with Digital Ocean]]></title>
            <link>https://sieradski.medium.com/im-breaking-up-with-digital-ocean-7e40bfbc69e3?source=rss-eae7d2c9dcc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e40bfbc69e3</guid>
            <category><![CDATA[managed-service-provider]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[digitalocean]]></category>
            <dc:creator><![CDATA[Daniel Sieradski]]></dc:creator>
            <pubDate>Thu, 03 Mar 2022 18:25:59 GMT</pubDate>
            <atom:updated>2022-03-03T21:51:22.275Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3aGBaEtcPnokr8R5ht05fg.png" /></figure><p>I have used DigitalOcean as my primary cloud provider for the past seven years. Part of that decision was ideological: I don’t want to support Amazon because of its abhorrent exploitative practices, nor Microsoft because of its contracts with ICE. Part was economical: Google Cloud, also not the nicest company but with a greener datacenter footprint, is simply far more expensive. And part was pure laziness: DigitalOcean is just really easy to use compared to other, more complex cloud offerings, and has suited my needs as a freelance web developer. Frankly, I was a big fan. Until now.</p><p>About a year ago — right around the time they started offering MySQL — I switched from using a third-party database hosting platform to DigitalOcean’s managed database service. I set myself up a small cluster in just a few minutes, migrated over my databases, and ever since then, I haven’t really had any complaints about its performance. But then yesterday at around 4PM ET, the roughly dozen websites on my droplets (DigitalOcean’s cutesy name for VMs) lost database connectivity. I could still connect to the database directly from my local machine and if I SSHed into the droplets. But for some inexplicable reason, none of my websites could reach them.</p><p>I immediately opened a trouble ticket, linking to different sites erroring on different droplets and selecting “Something is broken,” which supposedly escalates the issue for faster triage. Then I waited for a response. And waited. And waited.</p><p>Three hours later, I received:</p><blockquote>Hi there,<br>Thanks for the follow-up<br>I understand you are having some connection issues between your site and the managed database<br>In other to better assist here, please can you share with us the screenshot of the error message you are seeing and the time of the connection error</blockquote><p>Three hours waiting only to be asked, “Can you send screenshots of the erroring websites to which you provided links I could have just clicked?”</p><p>I patiently responded with the requested error messages. And waited again. And waited. Another three hours passed. Then my patience wore thin and I fired off another email, expressing my annoyance. Thirty minutes after that, I finally received a reply from someone on the database team. They told me that beyond a handful of CPU spikes, nothing looked particularly out of the ordinary, and suggested I temporarily disable the IP access restrictions on my database — to no avail.</p><p>I decided to go ahead and clone my database cluster and swap it in place of the other to see if the problem would persist. And it did. When I explained to the agent that I am able to connect to the new and old clusters locally and from the droplets, but still my sites would not connect, they declared that there is nothing wrong with the database cluster and passed me off to droplet support.</p><blockquote>Hi there,<br>Thanks for the additional information.<br>As you are able to connect the managed database cluster, this implies there is no issue with the cluster. <br>For further investigation, I have forwarded this to our droplet team for further review.</blockquote><p>An hour later (now eight hours of downtime), droplet support reached out with a boilerplate message about WordPress database connectivity, RAM usage, and tuning locally installed MySQL databases. Because that’s just what I need for my managed MySQL database service — to tune the non-existent MySQL server on my droplet!</p><p>At this point, it’s 12AM ET and I’ve had enough. I responded simply:</p><blockquote>oh my god read a ticket before you respond for the love of god</blockquote><p>And you know what this joker did? They sent me back almost the same exact boilerplate message about tuning a local MySQL database installation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*2XYmCK8m7P3qnjMqvLHA2g.png" /></figure><p>It took <em>17 hours</em> for the database connectivity issue to <em>self-correct</em>. It just randomly started working again on its own. DigitalOcean had no follow-up, no explanation, no nothing. My best guess is something happened with the CA certificate (DO’s managed databases require SSL even if you’re connecting internally via VPC to a server open to only your IP, but okay) but I wouldn’t even know how to begin to debug that and shouldn’t have to! That’s why I paid for managed database services! Because, as DigitalOcean claims, it’s supposed to be “Worry free!”</p><p>Well, you should worry. Because if your DigitalOcean “managed” database cluster suddenly becomes unreachable by your web applications, you’re apparently on your own, SLAs and customer loyalty be damned. Thus, after seven years of paying a not-insignificant sum of money to DigitalOcean, I examined their competitors, selected one, and have started migrating my clients’ websites away from their platform.</p><p>Look, I have a lot of empathy for tech workers and I know from my own past experience that working in technical support can be unpleasant when dealing with frustrated customers. And I know that the burden on tech support agents has increased because fewer people want to work in such an underpaid and undervalued role and therefore their workload has grown in some cases to an unmanageable degree. But I can’t allow my clients’ websites to be down for 17 hours because your company isn’t adequately staffed and your workers are too busy to read a ticket beyond scanning for keywords let alone to provide an answer that isn’t cut-and-pasted from a knowledge base. I can’t afford to spend literally thousands of dollars a year only to have to troubleshoot by myself the issues I thought I was paying your company to solve.</p><p>It’s time to get your shit together, DigitalOcean. Only then can we rekindle what was once a great love.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*AkLvdod5AZSrlLa2nkmZfA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e40bfbc69e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Things That Would Make GitHub Actions Even Better]]></title>
            <link>https://sieradski.medium.com/10-things-that-would-make-github-actions-even-better-a376bb0d624e?source=rss-eae7d2c9dcc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a376bb0d624e</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cicd]]></category>
            <category><![CDATA[github-actions]]></category>
            <dc:creator><![CDATA[Daniel Sieradski]]></dc:creator>
            <pubDate>Wed, 09 Feb 2022 20:07:31 GMT</pubDate>
            <atom:updated>2022-03-10T13:55:48.259Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C84zDOMo8nbJTRWkx9kIZg@2x.png" /></figure><p>As a DevOps engineer, I spend a great deal of time working on CI/CD pipelines, knee-deep in YAML, API documentation, and web search results, writing and re-writing workflows, running and re-running them over and over again, trying to smooth out the kinks. As such, I’ve come to develop strong opinions on how these things ought to work for developer’s ease. And having spent the last several months working intimately with GitHub Actions specifically, I’ve come to develop some strong opinions about it in particular.</p><p>Overall, I find GitHub Actions to be an excellent service that’s incredibly flexible, generally reliable, and has a wonderful, sizable community contributing to its vast catalog of pre-built workflows and workflow steps. However, there are some improvements that I believe should be made to GitHub Actions that will significantly enhance developers’ experience.</p><h3>1. A less disjointed user interface</h3><p>Currently, if you want to check out the status of a job run, you have to:</p><ol><li>Navigate to the corresponding repository in your browser (1–3 page loads if you start from the homepage)</li><li>Click the actions tab (+1 page load)</li><li>Select the workflow (+1 page load)</li><li>Click the run (+1 page load)</li><li>Click on the job (+1 page load)</li><li>Unfurl the step you want to view</li></ol><p>That’s 5–7 page loads just to check a job’s status.</p><p>Sure, GitHub shows the final status of your job runs on the notifications page. But if you have a high velocity repo with a lot of contributors, that page is essentially useless noise.</p><p>There has to be a better way.</p><p>GitHub could, for example, add a run status view to the GitHub homepage that shows all your currently running jobs. Or, when you click the Actions tab on a repo, there could be a dropdown menu that shows the latest jobs. Anything is better than what it is now.</p><h3>2. Subscribe to watch specific workflows</h3><p>GitHub will notify you about the result of any job you initiate, but it won’t notify you about the result of scheduled jobs triggered by GitHub’s crontab or jobs initiated by other users. GitHub should therefore add the ability for users to subscribe to workflows so that they get notified of their outcome whenever they’re run and by whoever.</p><h3>3. Modular workflows</h3><p>It’s a little frustrating to have to manage multiple copies of the same block of YAML — especially a big block of YAML — when only one or two variables in that block differ between workflows. GitHub should add a way to include YAML files into other YAML files, and to pass variables between the two, so that you can reuse modules across workflows. Yes, you could create other GitHub Actions to include in your workflows, but that’s kind of overkill, especially if the workflow is very specific to your development operations. Why not just…</p><p>A module:</p><pre>name: My module<br>id: my_module<br>type: module<br>inputs: <br>  - myVariable1<br>  - myVariable2</pre><pre>jobs:<br>  etc.</pre><p>An include:</p><pre>name: My workflow<br>jobs:<br>  my_job:<br>    runs-on: ubuntu-latest<br>    steps:<br>      - module: my_module<br>        inputs:<br>          - myVariable1: &#39;my input&#39;<br>          - myVariable2: &#39;my other input&#39;</pre><p>This would save so much hassle.</p><p><strong>UPDATE: </strong>As of November 2021, this exists. It’s called a <a href="https://docs.github.com/en/actions/using-workflows/reusing-workflows">Workflow Call</a>.</p><h3>4. Workflows that trigger other workflows and stay grouped to your P.R.</h3><p>Let’s say you have a monorepo and you run separate workflows specific to each package within your monorepo on every pull request.</p><p>Each workflow needs to run the same yarn install from the root when it first starts up. But you&#39;ve just updated your packages so there&#39;s a new yarn.lock and no cache available for your build. So now, each one of your workflows is going to start from scratch downloading and installing everything, adding at least five minutes to each run, unnecessarily eating up billable runtime.</p><p>But what if you could have a workflow that runs before your other workflows that detects changes in yarn.lock and pre-caches your node_modules first? You <em>can</em> configure a workflow to trigger other workflows using <a href="https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_run">workflow_run</a> or even Peter Evans&#39; <a href="https://github.com/marketplace/actions/repository-dispatch">Repository Dispatch</a> action (in which case use a personal access token, which is not ideal for organizations where it&#39;s preferable to not tie access keys to individual users&#39; accounts).</p><p>However, the problem is that subsequent workflows will get buried under the Actions tab and won’t be connected back to their trigger, specifically the P.R. that initiated the first workflow. Therefore, any checks in those workflows won’t be applied to the P.R., rendering them essentially useless if you use them for quality control.</p><p>Again, there’s gotta be a better way, and it could be as simple as modifying the workflow_run trigger to keep triggered workflows connected back to their initiator.</p><h3>5. Custom check results that go where they belong</h3><p>GitHub Actions allows you to add <a href="https://docs.github.com/en/developers/apps/guides/creating-ci-tests-with-the-checks-api">custom checks</a> to your workflows — validators that can block the merging of pull requests or the deployment of new builds. But for some bizarre reason, it doesn’t attach those custom checks to the workflows that triggered them. It will add them to any workflow triggered by the same P.R.</p><p>Per Michael Dorner, author of the <a href="https://github.com/marketplace/actions/test-reporter">Test Reporter</a> Action:</p><blockquote>Check Runs are created for specific commit SHA. It’s not possible to specify under which workflow test report should belong if more workflows are running for the same SHA. Thanks to this GitHub “feature” it’s possible your test report will appear in an unexpected place in GitHub UI.</blockquote><p>It’s true! And extremely confusing! And annoying! And GitHub should fix it!</p><h3>6. Automatically capture stdout/stderr from any step as an output and add more metadata as outputs</h3><p>In GitHub Actions, if you want to return the output of a command as a block of text to use in another job or step, you have to do some crazy BASH wizardry like:</p><pre>- name: Prettier<br>  id: prettier<br>  run: |<br>    ./node_modules/.bin/prettier — check 2&gt;&amp;1 | tee prettier-report.txt<br>    echo &quot;RESULTS&lt;&lt;EOF&quot; &gt;&gt; $GITHUB_ENV<br>    echo -e &quot;$(cat prettier-report.txt)&quot; &gt;&gt; $GITHUB_ENV<br>    echo &quot;EOF&quot; &gt;&gt; $GITHUB_ENV</pre><p>Each job step emits an object that contains user-designated outputs (which have their own issues, see #7), the outcome of the commands that were run — whether they were successful or not, and the conclusion of the step — whether it was successful or not. And…that’s it.</p><p>Why not include the actual output of what was run on the step object, too, instead of making me go through all that boilerplate each time I need to capture it?</p><p>GitHub could also add other useful metadata to the step object, such as the duration and time started and finished. These data are available from the GitHub API and gh CLI, so why not in the workflows themselves?</p><h3>7. Create an easier way of exporting multiline strings</h3><p>This jumble right here is how you export a multiline string in GitHub Actions:</p><pre>echo &quot;RESULTS&lt;&lt;EOF&quot; &gt;&gt; $GITHUB_ENV<br>echo -e &quot;$(cat my_file.txt)&quot; &gt;&gt; $GITHUB_ENV<br>echo &quot;EOF&quot; &gt;&gt; $GITHUB_ENV</pre><p>You can’t use <a href="https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions">outputs</a> because for some inexplicable reason they’re single-line only. (You don’t want to know how many failed runs I went through before I figured that out.)</p><p>You have to use a <em>global</em> environment variable that gets passed to every job in the workflow. Oh, and be careful that what you’ve echoed to $GITHUB_ENV isn’t too many lines, because it may crash your other jobs with an environment variable is too long error. Super-helpful, right?</p><p>Say it with me one more time: There has to be a better way. Maybe it’s…</p><h3>8. Add another variable layer that is neither secrets nor environment variables</h3><p>Not everything is a secret that needs to be concealed in the logs. And not everything is an environment variable that needs to be exposed to the whole job container. Sometimes you just need a place to jam some text and a way to get it back later. And that text isn’t always gonna be one short, convenient string. There needs to be somewhere other than outputs and environment variables that developers can temporarily stick stuff for our workflows. So how about adding some other kind of object that can actually handle things like multiline strings and, <em>gasp</em>, JSON objects gracefully? (And don’t you dare say “Use Upload Artifacts.”)</p><h3>9. Change the status indicator to a warning symbol when continue_on_error is enabled and a step fails</h3><p>As mentioned previously, each job step emits an object that contains the outcome of the commands that were run — whether they were successful or not, and the conclusion of the step — whether <em>it</em> was successful or not. The distinction is important.</p><p>You can continue a job where the outcome of a step is failure by adding a continue_on_error flag to the step. The step will then succeed even if the command it ran failed.</p><p>Sometimes this is useful if you want to, for example, upload test reports before terminating a job. To make the job fail after you complete your final steps, you have to create a validation step at the very end that checks whether the outcome on the actual test was success or failure and then emits an exit code of 0 or 1.</p><p>This is fine if you’re only validating one test. But if you’re validating multiple tests, you need to evaluate multiple steps’ outcome to determine the status of the job. Suddenly it becomes more difficult to quickly identify which test failed because there’s a big green check next to all the tests, but only one red <em>X</em> at the very end.</p><p>What GitHub can do here is change it so that if the conclusion is success but the outcome of a step is failure, the symbol is a yellow warning sign (⚠️) rather than a green checkmark. That way, you’ll quickly know which test in the group failed.</p><h3>10. Better log management</h3><p>One of the most painful aspects of working with GitHub Actions is reviewing the logs of jobs with a ton of output. Sometimes it’s not even worth trying on the website and I go right to the gh CLI. It’s just arduously slow and buggy. Sometimes you’ll just see thousands of blank lines and have to refresh the page several times before you see anything.</p><p>GitHub can address this in a number of ways. One is by sticking the logs in a scrollable window, truncating them, and tailing only the most recent output, making the previous lines available if you scroll up in the log window. They could also offer the option of showing stdout, stderr, or both for each step, so that you can control what gets output to the screen.</p><h3>Bonus: Notify <em>users</em> on Slack</h3><p>There are several GitHub Actions you can add to your workflows to send notifications to a Slack channel. But not everybody on your team needs to know about every workflow run and there’s presently no way to directly notify individual users of the outcomes of the checks on their own P.R.s. Part of this is simply the limitations of Slack’s webhooks integration which is channel restricted. But GitHub itself could partner with Slack to develop an integration that allows organizations to connect their Slack workspaces to GitHub and that ties users’ identities on GitHub to their identities on Slack. This way, you could create notifications that target individual users on Slack, instead of whole channels.</p><p>As you can see, GitHub Actions offers a great deal of functionality and flexibility to developers. But there’s always room for improvement, and in the areas I note, those improvements are sorely needed.</p><p>If you have any ideas for ways GitHub Actions could be better, please suggest them in the comments. And if you know anyone on the product team at GitHub whose eyes you can get this article in front of, please do!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a376bb0d624e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Twitter reaches for the sky from shaky ground]]></title>
            <link>https://sieradski.medium.com/twitter-reaches-for-the-sky-from-shaky-ground-ed9fe12688aa?source=rss-eae7d2c9dcc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed9fe12688aa</guid>
            <category><![CDATA[twitter]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[open-standards]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[mastodon]]></category>
            <dc:creator><![CDATA[Daniel Sieradski]]></dc:creator>
            <pubDate>Fri, 08 Oct 2021 08:12:58 GMT</pubDate>
            <atom:updated>2021-10-08T18:09:43.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GrqHJg8c_4U-xU4QfQpqeA.jpeg" /><figcaption>Mandela’s garden in the Robben Island courtyard (Photo by me)</figcaption></figure><p>About eight years ago, I visited South Africa and toured Robben Island, where the apartheid regime had imprisoned the great human rights activist and statesman Nelson Mandela. In the defunct yet preserved facility’s courtyard, there is a garden that Madiba had tended to during his incarceration. Each day he would go out into this garden, surrounded by the prison walls, and gaze into the sky while envisioning himself free, and for that moment, he’d forget where he was and experience contentment.</p><p>It’s absurd to analogize Mandela’s experience to the plight of today’s Internet users. But I’d be lying if I said the story hadn’t informed my perspective on what constitutes a “walled garden,” the users’ place within it, and most of all, how one should relate to the watchers on the wall.</p><p>In 2019, Twitter announced it would be embarking upon a new initiative to “decentralize social media.” Dubbed Bluesky, the project aims to create an open standard for the syndication of social media content that attaches proof of the author’s identity using the blockchain in currently unspecified ways. After sitting on it for a year-and-a-half, the company finally announced a project lead <a href="https://hypebeast.com/2021/8/twitter-bluesky-jay-graber-developer-crypto-decentralized-social-network">this past August</a> and recently launched a <a href="https://blueskyweb.org/">website</a> describing the project’s goals:</p><blockquote>The web. Email. RSS feeds. XMPP chats. What all these technologies had in common is they allowed people to freely interact and create content, without intermediaries.</blockquote><blockquote>We’re focusing on re-building the social web by connecting disconnected silos and returning control of the social experience to users. Our mission is to develop and drive the adoption of technologies for open and decentralized public conversation.</blockquote><p>Pardon me while I roll my eyes. Twitter already has the power to decentralize social media and has consistently worked instead to ensure that they remain in <a href="https://medium.com/@friske/this-isnt-about-social-media-this-is-about-control-112dea8a21fd">control of the public conversation</a> and that users remain firmly ensconced within their walled garden.</p><p>“The web. Email. RSS feeds.”</p><p>Yeah, okay, let’s talk about <a href="https://www.rssboard.org/rss-specification">RSS</a>. When introduced in 1999, RSS was a novel concept: A way to read content from all of your favorite websites without having to visit each one individually. Instead of maintaining an exhaustive list of bookmarks and visiting a dozen or more sites each day, you could stream all the content in which you were interested to one convenient application. This syndication format was especially well-suited to a new type of digital publishing that would soon come into vogue called web logging or “blogging” for short, one that would get a considerable boost from the introduction of a new platform called Blogger.com.</p><p>Blogger simplified the process of publishing content to, and sharing content from, your own website (it used FTP to upload static assets to <em>your</em> server) and took that sharing exponentially further by adding RSS feeds to the platform. The technologies both benefitted greatly from each other, increasing one another’s adoption. Every major news publisher had their journalists blogging, and RSS feeds on their homepages within a couple of years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*D0_9W0aLjDI0K4zpSMiHQg.png" /><figcaption>A typical early-2000’s RSS reader</figcaption></figure><p>With that mission accomplished and out of the way, Blogger soon started taking an interest in the concept of audio blogging recently introduced by one of the RSS specification’s authors, Dave Winer. They launched <a href="https://en.wikipedia.org/wiki/Odeo">Odeo</a>, which gave users a phone number to call and record a short audio message to post directly to their blog. These audio posts were then syndicated around the web via RSS using Winer’s new format. Others started using these so-called “RSS enclosures” to do long-form audio content, about which Apple, for some reason, got very excited. They just went ahead and added support for it in iTunes. And thus, a new medium was born: Podcasting.</p><p>In 2003, Blogger’s founder Ev Williams (who owns the godforsaken site you’re on right now) decided to focus on Odeo full-time and sold Blogger to Google, who summarily drove it into the ground. But within a short time, Odeo had dropped the audio idea. They decided to focus instead on SMS messages (which were becoming the new <em>it</em> thing) and relaunched as a “microblogging” platform called Twttr, where SMS would effectively replace RSS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ffD1Yk3LLOEzoK09BaRI8g.png" /><figcaption>Can you believe they made the designer who created this abomination their CEO?</figcaption></figure><p>It wasn’t tenable. After all, Twitter was ultimately an idea born from RSS. And everyone was now using RSS — it had total penetration. So within six months of launching, Twitter had no choice but to add <a href="https://blog.twitter.com/en_us/a/2006/twitter-has-permalinks-and-rss-feeds">RSS support</a>; otherwise, no one was going to be reading jack (pun intended). But there was one catch: Whereas many, if not most, blogs back then allowed users to leave comments without registering for an account, Twitter required registration to respond to tweets. Anyone following Twitterers via RSS who wanted to reply would have to create a Twitter account. This would ensure audience capture.</p><p>And so, one day, five years later, with a large segment of the audience sufficiently captured, the birdsite started singing a different tune. In 2011, the company quietly disappeared RSS feeds from users’ profile pages, and a few months later, <a href="https://webapps.stackexchange.com/questions/41499/any-alternatives-for-twitter-rss-after-native-service-is-shut-down">shut the feeds off</a> altogether. Now you had to go to Twitter to read tweets (and be bombarded with ads and the insistence that you create an account). The intent was obvious: To steer whatever audience that remained outside of Twitter into the walled garden. And frankly, <a href="https://www.cnet.com/how-to/how-twitter-replaced-my-rss-reader/">the strategy worked</a>. Within two years, Google pulled the plug on their beloved <a href="https://en.wikipedia.org/wiki/Google_Reader">Google Reader</a> RSS client. With it died the highly decentralized, community-built, open-protocol, and standards-driven blogosphere, atop whose ruins the closed-source, non-interoperable, toxically-managed, surveillance-capitalist Twittersphere was built. (And then Medium arrived to tap dance on its grave, stuffing blogging’s remains into its own walled garden. Thanks Ev!)</p><p>But it doesn’t end there! In addition to closing itself off from the rest of the web and closing its users in, Twitter has placed increasingly onerous restraints on developers using the Twitter API, which has resulted in third-party Twitter clients having to remove functions <a href="https://twitter.com/tweetbot/status/1263483486759006209?lang=en">as essential as notifications</a> because they <a href="https://developer.twitter.com/en/developer-terms/policy">“replicate Twitter’s core experience or features.”</a> You can’t even share<em> your own tweets</em> on <em>your own website</em> anymore without having to embed Twitter’s ridiculous widget (like the one below) with whatever tracking software accompanies it! It’s preposterous!</p><p>But here’s the kicker. The Twitter Developer Agreement explicitly states that you may not:</p><blockquote>Use Twitter Content or other data collected from people to create or maintain a separate conversational platform, social network, status update, private messaging or live broadcasting database or service</blockquote><p>In other words, you may not talk to anyone on Twitter except using Twitter’s apps, nor use Twitter to publish content to any other social platform. And we’re expected to believe they want interoperability across a decentralized social web? To that I say, L-O-fucking-L!</p><h3>Mastodon 🐘 on Twitter: &quot;Mastodon, your cryptocurrency-free decentralized social network. No blockchains, no NFTs, no attempting to turn every social interaction into a microtransaction / Twitter&quot;</h3><p>Mastodon, your cryptocurrency-free decentralized social network. No blockchains, no NFTs, no attempting to turn every social interaction into a microtransaction</p><p>Color me skeptical when Twitter says their goal is to promote a decentralized web and foster more open conversation. While it’s heartening to hear the folks behind Mastodon, Beaker Browser, ActivityPub, and IPFS are <a href="https://www.theverge.com/2021/1/21/22242718/twitter-bluesky-decentralized-social-media-team-project-update">involved</a> in the discussions taking place, I have zero illusions as to Twitter’s intentions. I could be convinced otherwise if they brought back user RSS feeds, reopened their developer API, and contributed to the already-existing <a href="https://www.w3.org/TR/micropub/">open</a> <a href="https://www.w3.org/TR/activitypub/">standards</a> for decentralized social media instead of trying to force a new one on us.* Until then, it just sounds like a new way to fleece crypto investors by using the development of open standards as a front, much like most other open-source “web3” initiatives with a blockchain attached.</p><p>The web is already decentralized — you just walled yourselves off from it.</p><p><em>*They could also restore my accounts which they permanently suspended for fighting back against the racists they refuse to keep off their platform and instead give ‘Verified’ status, but that’s a topic for a different post.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed9fe12688aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>