<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SocialMedia on L0G.is</title>
    <link>https://L0g.is/tags/socialmedia/</link>
    <description>Recent content in SocialMedia on L0G.is</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 16 Nov 2022 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://L0g.is/tags/socialmedia/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Leaving Birdland</title>
      <link>https://L0g.is/posts/leaving-birdland/</link>
      <pubDate>Wed, 16 Nov 2022 00:00:00 +0000</pubDate>
      <guid>https://L0g.is/posts/leaving-birdland/</guid>
      <description>&lt;!-- raw HTML omitted --&gt;&#xA;&lt;p&gt;This week, I deleted all my tweets on Twitter and posted a signpost to my new Mastodon account at &lt;a href=&#34;https://infosec.exchange/@L0G1S&#34;&gt;https://infosec.exchange/@L0G1S&lt;/a&gt;, might delete the whole thing next week, we&amp;rsquo;ll see.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve noticed from others within the infosec.exchange instance that there are some various growing pains for some when moving from Twitter to a federated community and I wanted to speak about why that is. Moving from a centralized community to a federated instance of something requires a shift into a new mindset of how you approach online communities in general. Even if the operation of the social media is similar. It doesn&amp;rsquo;t matter if tweets and toots are very similar, the underlying model is drastically different.  If someone isn&amp;rsquo;t aware of those differences with the federated model, they might be disappointed when this community doesn’t operate the same (meaning: offer the same features) as the old, centralized service.  Also moving from a billion dollar app to an open source one will also differ in quality and features.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
