<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Sean's Thoughts</title>
        <link>https://paragraph.com/@seanwince</link>
        <description>undefined</description>
        <lastBuildDate>Fri, 08 May 2026 16:16:54 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Welcome to Paragraph!]]></title>
            <link>https://paragraph.com/@seanwince/welcome-to-paragraph</link>
            <guid>hVRDvMpsynARNCHFXHgz</guid>
            <pubDate>Sun, 28 Jan 2024 03:53:07 GMT</pubDate>
            <description><![CDATA[This post teaches you everything you need to know about getting started with Paragraph.]]></description>
            <content:encoded><![CDATA[<p>Paragraph lets you create and share beautifully crafted posts - just like this one. </p><p>Write anything - from your smallest paragraph to your grandest masterpiece - and publish it online or send it as email newsletters directly to your readers.</p><p>Your Paragraph publication is blazing-fast, SEO optimized, and combines the best parts of both web2 and web3 to help you create content and grow your community better than ever. </p><h2>Getting started</h2><p>What you&apos;re looking at right now is the Paragraph editor. We support markdown, callouts, code, and rich media embeds like Twitter and YouTube.</p><div data-type="twitter" tweetid="1560419350976221185">   <div class="twitter-embed embed">    <div class="twitter-header">        <div style="display:flex">          <a target="_blank" href="https://twitter.com/paragraph_xyz">              <img alt="User Avatar" class="twitter-avatar" src="https://pbs.twimg.com/profile_images/1521582712527548416/VaZi_24t_normal.jpg">            </a>            <div style="margin-left:4px;margin-right:auto;line-height:1.2;">              <a target="_blank" href="https://twitter.com/paragraph_xyz" class="twitter-displayname">paragraph.xyz</a>              <p><a target="_blank" href="https://twitter.com/paragraph_xyz" class="twitter-username">@paragraph_xyz</a></p>                </div>            <a href="https://twitter.com/paragraph_xyz/status/1560419350976221185" target="_blank">              <img alt="Twitter Logo" class="twitter-logo" src="https://paragraph.xyz/editor/twitter/logo.png">            </a>          </div>        </div>          <div class="twitter-body">      On <a class="twitter-content-link" href="https://t.co/BbYULfPfbU" target="_blank">paragraph.xyz</a>, all posts are stored on <a class="twitter-content-link" href="https://twitter.com/ArweaveTeam" target="_blank">@ArweaveTeam</a>. This means they&apos;re immutable, uncensorable, permanent, and composable <img class="twitter-emoji" draggable="false" alt="✨" src="https://twemoji.maxcdn.com/v/14.0.2/72x72/2728.png">                    <a class="twitter-card-link" href="https://t.co/BbYULfPfbU" target="_blank">          <div class="twitter-media twitter-summary-large-image">            <img src="https://pbs.twimg.com/card_img/1747066277238108161/waMOL0FA?format=jpg&name=800x320_1">            <div class="twitter-summary-card-text">              <span>paragraph.xyz</span>              <h2>Paragraph | all-in-one publishing &amp; newsletter platform</h2>              <p>Create, publish and share web3-native blogs &amp; newsletters.</p>            </div>          </div>        </a>           </div>         <div class="twitter-footer">          <a target="_blank" href="https://twitter.com/paragraph_xyz/status/1560419350976221185" style="margin-right:16px; display:flex;">            <img alt="Like Icon" class="twitter-heart" src="https://paragraph.xyz/editor/twitter/heart.png">            16          </a>          <a target="_blank" href="https://twitter.com/paragraph_xyz/status/1560419350976221185"><p>7:12 PM • Aug 18, 2022</p></a>        </div>      </div>   </div><p>When you publish a post, you&apos;ll have the option of sending it as a newsletter or storing it in the permanent &amp; uncensorable Arweave. </p><h2>Helpful links</h2><p>Here&apos;s a few helpful pointers to customize your publication &amp; get the most out of Paragraph:</p><ul><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/settings/publication/theme">Theming &amp; customization</a>. Change your publication&apos;s font &amp; colors; truly make this space your own.</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/settings/publication/emails">Set up a welcome email</a>. This is the email your readers receive when they subscribe to your newsletter. </p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/settings/publication/blog">Configure your publication&apos;s settings</a>. Add links to your homepage, set up a custom domain, configure Google Analytics &amp; more. </p></li></ul><h2>Need help or have feedback?</h2><p>We&apos;ve put together some documentation <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://docs.paragraph.xyz">here</a>, but if you still have questions you&apos;d like answered we’d love to hear from you. </p><p>You can reach us via email at <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="mailto:hello@paragraph.xyz">hello@paragraph.xyz</a> or subscribe to our newsletter <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/@blog">here</a>. We&apos;re also pretty active on <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/discord">Discord</a>. </p>]]></content:encoded>
            <author>seanwince@newsletter.paragraph.com (Sean's Thoughts)</author>
            <category>tutorial</category>
            <enclosure url="https://paragraph.xyz/covers/welcome_to_paragraph_modern.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Web3 in 2022 and Beyond]]></title>
            <link>https://paragraph.com/@seanwince/web3-in-2022-and-beyond</link>
            <guid>fmu8mSnSqaklfSjXdKCE</guid>
            <pubDate>Wed, 08 Jun 2022 06:15:19 GMT</pubDate>
            <description><![CDATA[A popular analogy for explaining web3 vs. old web paradigms goes like this:Web1 = ReadWeb2 = Read & WriteWeb3 = Read, Write & OwnIn Web1, the average...]]></description>
            <content:encoded><![CDATA[<p>A popular analogy for explaining web3 vs. old web paradigms goes like this:</p><p>Web1 = Read</p><p>Web2 = Read &amp; Write</p><p>Web3 = Read, Write &amp; Own</p><p>In Web1, the average internet user could, for the most part, only read content online. It involved going to the AOL or Yahoo homepage and checking out the latest news, or some other activity that was simply just consuming content. Like radio or television, information was beamed down to the end-user by third parties (usually large companies) that could afford the resources to broadcast on this new medium.</p><p>Web2 represented a sea change in how the average person could interact with the internet. Starting with forums and eventually ending with mass social media, the user could now broadcast their own messages directly to other internet users, or the entire world if they wished. Social media such as MySpace, Facebook and others now allowed the average person to easily create their own content and curate a following.</p><p>The downside, though, is that those social media companies actually owned that content at the end of the day. Whether by a terms of service agreement (which nobody read) or by the practical matter of all the data being stored on a server, users did not actually own their content, posts, or following -- the company could ban them or remove content at any time.</p><p>The latest change now possible thanks to web3 is that users can now finally create content and actually own it themselves. Instead of content existing on a company’s server, it can now be hosted on a public, decentralized blockchain which is maintained by thousands of computers across the whole world. Instead of a list of followers being proprietary data controlled by a company, that list can be a set of tokens which are carried by the user from one service to another.</p><p>We are still just at the beginning of this paradigm shift -- think Facebook circa 2005. It’s impossible for us to know where such a huge change will lead in 10-15 years, just like it was impossible for early Facebook users to imagine the platform being influential in elections. How will internet users change their behavior now that they unequivocally own the digital goods they produce? Only time will tell.</p>]]></content:encoded>
            <author>seanwince@newsletter.paragraph.com (Sean's Thoughts)</author>
        </item>
    </channel>
</rss>