<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Welkyn Devlog on WickNet</title>
    <link>https://wicknet.dev/devlog/welkyn/</link>
    <description>Recent content in Welkyn Devlog on WickNet</description>
    <image>
      <title>WickNet</title>
      <url>https://wicknet.dev/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://wicknet.dev/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.143.1</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 23 Jan 2025 23:18:47 -0500</lastBuildDate>
    <atom:link href="https://wicknet.dev/devlog/welkyn/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Welkyn Devlog 2025-01-23</title>
      <link>https://wicknet.dev/devlog/welkyn/2025-01-23/</link>
      <pubDate>Thu, 23 Jan 2025 23:18:47 -0500</pubDate>
      <guid>https://wicknet.dev/devlog/welkyn/2025-01-23/</guid>
      <description>&lt;p&gt;The philosophical drive for Welkyn is to create a window to the AP network. That is, persistence of data is not an anticipated feature. Welkyn will preserve local data, but will be, effectively, a sliding window into the fediverse. Historic data from remote instances will not be kept. The experimental motivation is to address the infinite database creep of existing fediverse implementations. This ought to allow the software to run on less powerful hardware, and require fewer resources, compute, storage, or otherwise. While this may sound drastic, with a long enough window (90 days or so), and combining this with persistent local data, some rules about keeping conversations in which the user participated, or bookmarked a post, I anticipate that there will be minimal impact on the user who merely wishes to communicate with other fediverse users while significantly reducing hard-disk and compute requirements with regards especially to databases.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
