<?xml version="1.0" encoding="UTF-8"?>
<rss  xmlns:atom="http://www.w3.org/2005/Atom" 
      xmlns:media="http://search.yahoo.com/mrss/" 
      xmlns:content="http://purl.org/rss/1.0/modules/content/" 
      xmlns:dc="http://purl.org/dc/elements/1.1/" 
      version="2.0">
<channel>
<title>Lamtei Wahlang</title>
<link>https://lamtei.me/</link>
<atom:link href="https://lamtei.me/index.xml" rel="self" type="application/rss+xml"/>
<description>Software development, music, technology and other topics.</description>
<generator>quarto-1.9.38</generator>
<lastBuildDate>Thu, 13 Aug 2026 19:00:00 GMT</lastBuildDate>
<item>
  <title>Revamping a Chat App: Evolving an Open Standard into a Modern Messaging Platform</title>
  <link>https://lamtei.me/published/ejabberd-revamp/revamping-ejabberd-for-modern-chat.html</link>
  <description><![CDATA[ Some years back I worked on a messaging platform and learned a lot about these systems, so I thought why not write about it. A story, more historical than recent, of four places where the XMPP core design meets a modern mobile messenger and does not quite fit, and what we did about each of them. ]]></description>
  <guid>https://lamtei.me/published/ejabberd-revamp/revamping-ejabberd-for-modern-chat.html</guid>
  <pubDate>Thu, 13 Aug 2026 19:00:00 GMT</pubDate>
</item>
</channel>
</rss>
