<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[Roidboard - Feedback & Support]]></title>
		<link>https://roidboard.to/</link>
		<description><![CDATA[Roidboard - https://roidboard.to]]></description>
		<pubDate>Mon, 19 Oct 2026 10:43:49 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Feature Requests]]></title>
			<link>https://roidboard.to/thread-9.html</link>
			<pubDate>Thu, 15 Oct 2026 13:31:24 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://roidboard.to/member.php?action=profile&uid=1">admin</a>]]></dc:creator>
			<guid isPermaLink="false">https://roidboard.to/thread-9.html</guid>
			<description><![CDATA[<div style="text-align: center;" class="mycode_align"><span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Feature Requests</span></span></div>
<br />
Got an idea for something the board should have? Post it here.<br />
<br />
Good feature requests share a few things. They describe a real problem you are running into, not just a feature you saw elsewhere. They are specific enough that someone could actually build what you are describing. And they acknowledge that not everything can ship at once.<br />
<br />
We read every suggestion. Some we act on quickly, some go on a list for later, and some we decide against. When we pass on an idea, it is usually because it conflicts with something else we are building or because the effort does not match the benefit for the number of people it would help.<br />
<br />
If your idea gets picked up, we will mention it in the <a href="https://roidboard.to/forumdisplay.php?fid=24" target="_blank" rel="noopener" class="mycode_url">Changelog</a> when it ships.<br />
<br />
A few things that are <span style="font-weight: bold;" class="mycode_b">not</span> feature requests:<ul class="mycode_list"><li>Bug reports (those go in <a href="https://roidboard.to/forumdisplay.php?fid=65" target="_blank" rel="noopener" class="mycode_url">Bug Reports</a>)<br />
</li>
<li>Complaints about moderation decisions (PM a moderator)<br />
</li>
<li>Requests to change the rules (PM staff)<br />
</li>
</ul>
<br />
Post your idea as a new thread in this forum with a descriptive title. Keep it to one idea per thread so discussion stays focused.]]></description>
			<content:encoded><![CDATA[<div style="text-align: center;" class="mycode_align"><span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Feature Requests</span></span></div>
<br />
Got an idea for something the board should have? Post it here.<br />
<br />
Good feature requests share a few things. They describe a real problem you are running into, not just a feature you saw elsewhere. They are specific enough that someone could actually build what you are describing. And they acknowledge that not everything can ship at once.<br />
<br />
We read every suggestion. Some we act on quickly, some go on a list for later, and some we decide against. When we pass on an idea, it is usually because it conflicts with something else we are building or because the effort does not match the benefit for the number of people it would help.<br />
<br />
If your idea gets picked up, we will mention it in the <a href="https://roidboard.to/forumdisplay.php?fid=24" target="_blank" rel="noopener" class="mycode_url">Changelog</a> when it ships.<br />
<br />
A few things that are <span style="font-weight: bold;" class="mycode_b">not</span> feature requests:<ul class="mycode_list"><li>Bug reports (those go in <a href="https://roidboard.to/forumdisplay.php?fid=65" target="_blank" rel="noopener" class="mycode_url">Bug Reports</a>)<br />
</li>
<li>Complaints about moderation decisions (PM a moderator)<br />
</li>
<li>Requests to change the rules (PM staff)<br />
</li>
</ul>
<br />
Post your idea as a new thread in this forum with a descriptive title. Keep it to one idea per thread so discussion stays focused.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[How to Get Help]]></title>
			<link>https://roidboard.to/thread-8.html</link>
			<pubDate>Thu, 15 Oct 2026 13:31:22 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://roidboard.to/member.php?action=profile&uid=1">admin</a>]]></dc:creator>
			<guid isPermaLink="false">https://roidboard.to/thread-8.html</guid>
			<description><![CDATA[<div style="text-align: center;" class="mycode_align"><span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">How to Get Help</span></span></div>
<br />
If something is not working the way you expect, this is how to get a fast answer.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Before posting</span><br />
<ol type="1" class="mycode_list"><li>Check if someone already reported the same thing. A quick search saves everyone time.<br />
</li>
<li>Figure out if it is a bug or a question. A bug is something broken (page error, feature not working, display glitch). A question is "how do I do X."<br />
</li>
</ol>
<br />
<span style="font-weight: bold;" class="mycode_b">If it is a bug</span><br />
Post it in <a href="https://roidboard.to/forumdisplay.php?fid=65" target="_blank" rel="noopener" class="mycode_url">Bug Reports</a> with steps to reproduce, what you expected and what actually happened. Include your browser and device if relevant.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">If it is a question or suggestion</span><br />
Post it right here in Feedback and Support. Be specific about what you need. "The forum is confusing" does not help us help you. "I cannot find where to leave a vendor review" does.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">What to include</span><ul class="mycode_list"><li>A clear subject line that describes the issue<br />
</li>
<li>The URL of the page where you saw the problem, if applicable<br />
</li>
<li>A screenshot if the issue is visual<br />
</li>
<li>Your browser and whether you are on mobile or desktop<br />
</li>
</ul>
<br />
Staff check this section daily. We will respond, usually within a day.]]></description>
			<content:encoded><![CDATA[<div style="text-align: center;" class="mycode_align"><span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">How to Get Help</span></span></div>
<br />
If something is not working the way you expect, this is how to get a fast answer.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Before posting</span><br />
<ol type="1" class="mycode_list"><li>Check if someone already reported the same thing. A quick search saves everyone time.<br />
</li>
<li>Figure out if it is a bug or a question. A bug is something broken (page error, feature not working, display glitch). A question is "how do I do X."<br />
</li>
</ol>
<br />
<span style="font-weight: bold;" class="mycode_b">If it is a bug</span><br />
Post it in <a href="https://roidboard.to/forumdisplay.php?fid=65" target="_blank" rel="noopener" class="mycode_url">Bug Reports</a> with steps to reproduce, what you expected and what actually happened. Include your browser and device if relevant.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">If it is a question or suggestion</span><br />
Post it right here in Feedback and Support. Be specific about what you need. "The forum is confusing" does not help us help you. "I cannot find where to leave a vendor review" does.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">What to include</span><ul class="mycode_list"><li>A clear subject line that describes the issue<br />
</li>
<li>The URL of the page where you saw the problem, if applicable<br />
</li>
<li>A screenshot if the issue is visual<br />
</li>
<li>Your browser and whether you are on mobile or desktop<br />
</li>
</ul>
<br />
Staff check this section daily. We will respond, usually within a day.]]></content:encoded>
		</item>
	</channel>
</rss>