<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Screenly 26.11.3 | Screenly</title><description>What has shipped across Screenly, newest first.</description><link>https://www.screenly.io/releases/screenly/26.11.3/</link><language>en</language><atom:link href="https://www.screenly.io/releases/screenly/26.11.3/rss.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Tue, 03 Nov 2026 00:00:00 +0000</lastBuildDate><item><title>Screenly 26.11.3: Improvements to adding a passkey</title><link>https://www.screenly.io/releases/screenly/26.11.3/adding-a-passkey/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.11.3/adding-a-passkey/</guid><pubDate>Tue, 03 Nov 2026 00:00:00 +0000</pubDate><category>improvement</category><category>security</category><description>&lt;p&gt;Adding a passkey on the Security tab of your account settings is clearer now. It takes you from
naming the passkey to confirming on your device and tells you when it&amp;rsquo;s done, the same way creating
an API token does.&lt;/p&gt;
&lt;p&gt;When something goes wrong, the error message says what happened, so you know how to fix it.&lt;/p&gt;</description></item><item><title>Screenly 26.11.3: Players report whether each command ran, and other behind-the-scenes work</title><link>https://www.screenly.io/releases/screenly/26.11.3/fixes-and-improvements/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.11.3/fixes-and-improvements/</guid><pubDate>Tue, 03 Nov 2026 00:00:00 +0000</pubDate><category>roundup</category><description>&lt;p&gt;Behind the scenes, the work in this release went into these areas:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Players now report back whether each command they get, such as reboot or take screenshot, ran.
It&amp;rsquo;s groundwork for &lt;a href="https://www.screenly.io/features/device-management/"&gt;device management&lt;/a&gt;: we&amp;rsquo;re working toward
showing in the dashboard which commands were sent to a screen, who sent them, and how each one
turned out.&lt;/li&gt;
&lt;li&gt;How content files are delivered.&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>