<?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"><channel><title><![CDATA[PyLova v0.3.1 Released! - Multi-Image Post Support]]></title><description><![CDATA[<p dir="auto"><img src="https://quokk.au/static/media/posts/iW/Eu/iWEu0jm8AFQvHZE.png" alt="image" class=" img-fluid img-markdown" /></p>
<p dir="auto"><a href="https://codeberg.org/quokkau/PyLova" rel="nofollow ugc">PyLova</a> (Python+<a href="https://en.wikipedia.org/wiki/Pavlova" rel="nofollow ugc">Pavlova</a>) is a soft fork of PieFed, aimed at improving the user experience through UI overhauls, empowering users and admins with agency, improved administration and moderation functions, and general bug fixing.</p>
<h1>New in V0.3.1</h1>
<p dir="auto">V0.3.1 is a smaller update. The main benefit of this update is the introduction of a new feature, multiple image posts.</p>
<p dir="auto">A special thanks to <a class="plugin-mentions-user plugin-mentions-a" href="/user/awesomelowlander%40quokk.au" aria-label="Profile: awesomelowlander@quokk.au">@<bdi>awesomelowlander@quokk.au</bdi></a> for their help bug-hunting</p>
<h2>Multi-Image Posts</h2>
<p dir="auto">These posts allows users on PyLova instances to share threads with more than one image, a feature I've personally much needed for my communities. You can drag and drop the order of images around on the upload page.</p>
<p dir="auto">For non-PyLova instances they will unfortunately only see the 'cover' image, that is the one ordered first in the list. With v0.3.2 I will aim at ensuring it is compatible with Mastodon and Sharkey instances which allow for multi-image posts. I will also look at potentially displaying these as images inside the post body for Lemmy/Mbin/PieFed.  Ideally in the future we can work to seeing this feature more readily supported across the Threadiverse, and I would love to work with devs on other projects to see this goal realised.</p>
<h2>For Admins</h2>
<ul>
<li>New Users would be subjected to a 7 day waiting period on PieFed, which severely limited their ability to post/comment/msg. There is now a toggle in the users profile that admins can set to 'verify' a user and remove this restriction from them - it can also be re-set on older accounts.</li>
</ul>
<h2>Bug-Fixes</h2>
<ul>
<li>If you went to the page of an undiscovered user, i.e. <a href="http://quokk.au/u/randomaccount@anarchist.nexus" rel="nofollow ugc">quokk.au/u/randomaccount@anarchist.nexus</a> it would return 'not found' on a blank page. Now it actually fetches the user (if they exist) and shows you their profile.</li>
<li>Visiting a community url ending with a / (i.e. <a href="http://quokk.au/c/news/" rel="nofollow ugc">quokk.au/c/news/</a> instead of <a href="http://quokk.au/c/news" rel="nofollow ugc">quokk.au/c/news</a>) would render a blank 'not found' page, the page is now correctly found.</li>
<li>If you discovered and joined a new community, all comment replies would be dated from the date of discovery (i.e. seconds ago). They now correctly match the actual date they were posted.</li>
<li>When choosing to share a new community via !newcommunities@lemmy.world, the post would default to having notifications turned off. This has now been changed and you will be informed when users comment in the thread about your new community.</li>
</ul>


<div class="row mt-3"><div class="col-12 mt-3"><div class="ratio ratio-16x9">
<video controls>
<source src="https://quokk.au/static/media/posts/AZ/Ts/AZTsyJs1dVBI5O9.mp4" type="video/mp4"></source>
</video>
</div></div></div>]]></description><link>https://forum.ieu.app/topic/c971c698-2351-4ef5-9eea-ace63e5aeab2/pylova-v0.3.1-released-multi-image-post-support</link><generator>RSS for Node</generator><lastBuildDate>Sat, 05 Sep 2026 22:28:21 GMT</lastBuildDate><atom:link href="https://forum.ieu.app/topic/c971c698-2351-4ef5-9eea-ace63e5aeab2.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 15 Aug 2026 09:00:13 GMT</pubDate><ttl>60</ttl></channel></rss>