<?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[Starwolves | Space Frontiers - Rules and Policy]]></title>
		<link>https://starwolves.io/</link>
		<description><![CDATA[Starwolves | Space Frontiers - https://starwolves.io]]></description>
		<pubDate>Wed, 27 May 2026 19:43:25 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Security policy]]></title>
			<link>https://starwolves.io/thread-3.html</link>
			<pubDate>Thu, 24 Nov 2022 17:53:26 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://starwolves.io/member.php?action=profile&uid=1">starwolf</a>]]></dc:creator>
			<guid isPermaLink="false">https://starwolves.io/thread-3.html</guid>
			<description><![CDATA[<span style="font-size: x-large;" class="mycode_size">Security Policy</span><br />
Security related information regarding Star Wolves product development and self-managed services.<br />
<br />
<span style="font-size: large;" class="mycode_size">Domain names</span><br />
The domain names make use of <a href="https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en" target="_blank" rel="noopener" class="mycode_url">DNSSEC</a>.<br />
<br />
<span style="font-size: large;" class="mycode_size">Email postmaster</span><br />
The email postmaster that sends emails to users for verification and recovery options only sends SSL-encrypted emails.<br />
<br />
<span style="font-size: large;" class="mycode_size">Server security</span><br />
Server installations are deployed on Linux and have undergone routine security measurements. From intrusion prevention software, to whitelisting only specific static IP addresses with firewalls and by making proper use of Linux users, permissions systems and administrators use password vaults with randomly generated passwords and two factor authentication.<br />
Services run on secure servers inside data-centers with optimal geographic positions. These data-centers are secured and only physically and remotely accessible by trusted people.<br />
<br />
<span style="font-size: large;" class="mycode_size">Service security</span><br />
Web services are offered as HTTPS-only.<br />
User and admins ervices that provide login portals have sets of minimum password requirements. Login functionality of our services comes either as rate limited or with captchas to protect against bots. Or both!<br />
Backups are performed every month and are only accessible by persons of high authorization.<br />
<br />
<span style="font-size: medium;" class="mycode_size">1. MyBB (starwolves.io forum)</span><br />
<a href="https://mybb.com/" target="_blank" rel="noopener" class="mycode_url">MyBB</a> is a free open source BulletinBoard project that has existed and matured for many years. It has undergone a lot of security analyses and updates. For this instance <a href="https://docs.mybb.com/1.8/administration/security/protection/" target="_blank" rel="noopener" class="mycode_url">the security advises</a> have been heard and many security related settings have been tweaked. The MySQL database has been secured.<br />
<br />
<span style="font-size: medium;" class="mycode_size">2. Gitlab (gitlab.starwolves.io)</span><br />
<a href="https://gitlab.com/rluna-gitlab/gitlab-ce" target="_blank" rel="noopener" class="mycode_url">Gitlab community edition</a> is an open source end-to-end software development platform with built-in version control, issue tracking, code review, CI/CD, and more. The <a href="https://docs.gitlab.com/ee/security/" target="_blank" rel="noopener" class="mycode_url">security advises</a> have been heard and security tweaks have been made to it as well. Gitlab is mature and backed by big business.<br />
<br />
<span style="font-size: medium;" class="mycode_size">3. Matrix (comms.starwolves.io)</span><br />
<a href="https://github.com/matrix-org/dendrite" target="_blank" rel="noopener" class="mycode_url">Dendrite</a> is a new Matrix homeserver written in Go. It is free open source and currently still in an early development state. Matrix is a very secure messaging system and messages are only stored in encrypted forms inside the databases.<br />
<br />
<span style="font-size: medium;" class="mycode_size">4. Store (store.starwolves.io)</span><br />
<a href="https://store.starwolves.io/" target="_blank" rel="noopener" class="mycode_url">The store</a> is a custom Node.js solution that accepts credit card payments with Stripe. We do not store any sensitive payment or personal information on our servers, instead these are stored on the servers of Stripe. The store has rate limiters installed and user passwords are hashed using Argon2. Input on all POST and GET methods are validated server-side. SQL queries that involve input are escaped. Sensitive endpoints are whitelisted by IP address. The store is exclusively served over a secure <span style="font-weight: bold;" class="mycode_b">https</span> connection. Server-side API keys have been stripped of as much permissions as possible.<br />
<br />
<span style="font-size: large;" class="mycode_size">Security of high authorization persons</span><br />
Persons with high levels of access are expected to practice digital hygiene. This is reserved for server maintainers, administrators, DevOps and the like.<br />
Required digital hygiene points:<br />
<ol type="1" class="mycode_list"><li>Manage your device(s) accounts with access to high authorization accounts(<a href="http://#fn-1-536" target="_blank" rel="noopener" class="mycode_url">1</a>) responsibly, professionally and maturely and only entrust it to people that you explicitly entrust with all this data (people whose full identity you know) and people that have to your estimations a low chance of maliciously making use of your device(s).<br />
</li>
<li>Usage of two-factor authentication for all relevant accounts(<a href="http://#fn-1" target="_blank" rel="noopener" class="mycode_url">1</a>). Two factor authentication secrets must be stored inside a password protected ENCRYPTED application (like Android app <a href="https://github.com/beemdevelopment/Aegis" target="_blank" rel="noopener" class="mycode_url">Aegis</a>) or other secure password vaults with TOTP features.<br />
</li>
<li>Usage of a password vault with randomly generated strings as passwords for the relevant authorized accounts(<a href="http://#fn-1" target="_blank" rel="noopener" class="mycode_url">1</a>).<br />
</li>
<li>Usage of device and disk encryption supplied as features with operating systems for devices that have access to relevant authorized accounts<a href="http://#fn-1" target="_blank" rel="noopener" class="mycode_url">(1)</a>. For Windows users, this includes BitLocker + character PIN on boot.<br />
</li>
</ol>
<br />
For persons with such access: A full identity exchange including verification of legal personal identification documents through trusted services (ie <a href="https://www.electronicid.eu/" target="_blank" rel="noopener" class="mycode_url">electronicid.eu</a>) are required. <br />
<br />
<br />
Footnotes:<br />
<ol type="1" class="mycode_list"><li>Accounts that have high levels of authorization to one or more of our servers, services or products. <a href="http://#fnref-1-536" target="_blank" rel="noopener" class="mycode_url">↩</a> <a href="http://#fnref-1-2" target="_blank" rel="noopener" class="mycode_url">↩2</a> <a href="http://#fnref-1-3" target="_blank" rel="noopener" class="mycode_url">↩3</a> <a href="http://#fnref-1-4" target="_blank" rel="noopener" class="mycode_url">↩4</a><br />
</li>
</ol>
]]></description>
			<content:encoded><![CDATA[<span style="font-size: x-large;" class="mycode_size">Security Policy</span><br />
Security related information regarding Star Wolves product development and self-managed services.<br />
<br />
<span style="font-size: large;" class="mycode_size">Domain names</span><br />
The domain names make use of <a href="https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en" target="_blank" rel="noopener" class="mycode_url">DNSSEC</a>.<br />
<br />
<span style="font-size: large;" class="mycode_size">Email postmaster</span><br />
The email postmaster that sends emails to users for verification and recovery options only sends SSL-encrypted emails.<br />
<br />
<span style="font-size: large;" class="mycode_size">Server security</span><br />
Server installations are deployed on Linux and have undergone routine security measurements. From intrusion prevention software, to whitelisting only specific static IP addresses with firewalls and by making proper use of Linux users, permissions systems and administrators use password vaults with randomly generated passwords and two factor authentication.<br />
Services run on secure servers inside data-centers with optimal geographic positions. These data-centers are secured and only physically and remotely accessible by trusted people.<br />
<br />
<span style="font-size: large;" class="mycode_size">Service security</span><br />
Web services are offered as HTTPS-only.<br />
User and admins ervices that provide login portals have sets of minimum password requirements. Login functionality of our services comes either as rate limited or with captchas to protect against bots. Or both!<br />
Backups are performed every month and are only accessible by persons of high authorization.<br />
<br />
<span style="font-size: medium;" class="mycode_size">1. MyBB (starwolves.io forum)</span><br />
<a href="https://mybb.com/" target="_blank" rel="noopener" class="mycode_url">MyBB</a> is a free open source BulletinBoard project that has existed and matured for many years. It has undergone a lot of security analyses and updates. For this instance <a href="https://docs.mybb.com/1.8/administration/security/protection/" target="_blank" rel="noopener" class="mycode_url">the security advises</a> have been heard and many security related settings have been tweaked. The MySQL database has been secured.<br />
<br />
<span style="font-size: medium;" class="mycode_size">2. Gitlab (gitlab.starwolves.io)</span><br />
<a href="https://gitlab.com/rluna-gitlab/gitlab-ce" target="_blank" rel="noopener" class="mycode_url">Gitlab community edition</a> is an open source end-to-end software development platform with built-in version control, issue tracking, code review, CI/CD, and more. The <a href="https://docs.gitlab.com/ee/security/" target="_blank" rel="noopener" class="mycode_url">security advises</a> have been heard and security tweaks have been made to it as well. Gitlab is mature and backed by big business.<br />
<br />
<span style="font-size: medium;" class="mycode_size">3. Matrix (comms.starwolves.io)</span><br />
<a href="https://github.com/matrix-org/dendrite" target="_blank" rel="noopener" class="mycode_url">Dendrite</a> is a new Matrix homeserver written in Go. It is free open source and currently still in an early development state. Matrix is a very secure messaging system and messages are only stored in encrypted forms inside the databases.<br />
<br />
<span style="font-size: medium;" class="mycode_size">4. Store (store.starwolves.io)</span><br />
<a href="https://store.starwolves.io/" target="_blank" rel="noopener" class="mycode_url">The store</a> is a custom Node.js solution that accepts credit card payments with Stripe. We do not store any sensitive payment or personal information on our servers, instead these are stored on the servers of Stripe. The store has rate limiters installed and user passwords are hashed using Argon2. Input on all POST and GET methods are validated server-side. SQL queries that involve input are escaped. Sensitive endpoints are whitelisted by IP address. The store is exclusively served over a secure <span style="font-weight: bold;" class="mycode_b">https</span> connection. Server-side API keys have been stripped of as much permissions as possible.<br />
<br />
<span style="font-size: large;" class="mycode_size">Security of high authorization persons</span><br />
Persons with high levels of access are expected to practice digital hygiene. This is reserved for server maintainers, administrators, DevOps and the like.<br />
Required digital hygiene points:<br />
<ol type="1" class="mycode_list"><li>Manage your device(s) accounts with access to high authorization accounts(<a href="http://#fn-1-536" target="_blank" rel="noopener" class="mycode_url">1</a>) responsibly, professionally and maturely and only entrust it to people that you explicitly entrust with all this data (people whose full identity you know) and people that have to your estimations a low chance of maliciously making use of your device(s).<br />
</li>
<li>Usage of two-factor authentication for all relevant accounts(<a href="http://#fn-1" target="_blank" rel="noopener" class="mycode_url">1</a>). Two factor authentication secrets must be stored inside a password protected ENCRYPTED application (like Android app <a href="https://github.com/beemdevelopment/Aegis" target="_blank" rel="noopener" class="mycode_url">Aegis</a>) or other secure password vaults with TOTP features.<br />
</li>
<li>Usage of a password vault with randomly generated strings as passwords for the relevant authorized accounts(<a href="http://#fn-1" target="_blank" rel="noopener" class="mycode_url">1</a>).<br />
</li>
<li>Usage of device and disk encryption supplied as features with operating systems for devices that have access to relevant authorized accounts<a href="http://#fn-1" target="_blank" rel="noopener" class="mycode_url">(1)</a>. For Windows users, this includes BitLocker + character PIN on boot.<br />
</li>
</ol>
<br />
For persons with such access: A full identity exchange including verification of legal personal identification documents through trusted services (ie <a href="https://www.electronicid.eu/" target="_blank" rel="noopener" class="mycode_url">electronicid.eu</a>) are required. <br />
<br />
<br />
Footnotes:<br />
<ol type="1" class="mycode_list"><li>Accounts that have high levels of authorization to one or more of our servers, services or products. <a href="http://#fnref-1-536" target="_blank" rel="noopener" class="mycode_url">↩</a> <a href="http://#fnref-1-2" target="_blank" rel="noopener" class="mycode_url">↩2</a> <a href="http://#fnref-1-3" target="_blank" rel="noopener" class="mycode_url">↩3</a> <a href="http://#fnref-1-4" target="_blank" rel="noopener" class="mycode_url">↩4</a><br />
</li>
</ol>
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[General rules]]></title>
			<link>https://starwolves.io/thread-2.html</link>
			<pubDate>Thu, 24 Nov 2022 17:48:20 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://starwolves.io/member.php?action=profile&uid=1">starwolf</a>]]></dc:creator>
			<guid isPermaLink="false">https://starwolves.io/thread-2.html</guid>
			<description><![CDATA[<span style="font-size: large;" class="mycode_size">The following rules apply to Star Wolves platforms and services such as the SS14 server and the official Space Frontiers Discord server.</span><br />
<br />
<br />
<span style="font-weight: bold;" class="mycode_b">0. Regarding minors.  </span><br />
(I) <span style="font-weight: bold;" class="mycode_b">NO minors below the age of 16 are allowed to be present or to partake in our server or services unless they are accompanied by parental consent AND by parental supervision.</span><br />
(II) Orderly and respectful conduct from adults around or towards minors is a standard that you must do your best to uphold at all times.<br />
(III) In and around the SS14 server and the default 16+ Discord channels you must always assume minors are watching and present, which means you must moderate your own behavior accordingly. Do not be overtly rude, vulgar or mean to other users; instead resort to pinging or messaging staff members to resolve issues.<br />
(IV) The SS14 server and the default 16+ Discord channels prioritize light-hearted, playful &amp; mutually courteous and respectful behavior. <br />
<span style="font-weight: bold;" class="mycode_b">1. No NSFW conversations or content.</span><br />
(I) No extreme vulgar, overly violent, disgusting, brutal or sexually explicit conversations or content.<br />
<span style="font-weight: bold;" class="mycode_b">2. With respect to freedom of speech.</span><br />
(I) We offer everyone the freedom of speech and freedom to offend inside our designated 18+ Discord channels. However, this freedom is not a given in our Space Station 14 game server or in the default Discord 16+ server channels.<br />
(II) But to a reasonable extend that doesn't result in the degeneracy of our chat. Please, dependent on the severity of the offending speech you may have outed, consider how often and when you would like to repeat it in this server.<br />
(III) We also offer a place to discuss controversial topics, but when you discuss or mention such topics ensure you do so with the right motives. It is easy to provoke a lot of emotions and chaos in the chat by being careless with what you write.<br />
(IV) Jokes about sensitive topics are okay but refer to Rules 2.II and 3 . We will do our best to allow for genuine jokes, but we keep our eyes out on controversial jokes a bit more. Just because sometimes the motivations aren't always to truly try and make people laugh.<br />
<span style="font-weight: bold;" class="mycode_b">3. No bad trolls.</span><br />
(I) Please ensure that the persona you represent in our server is "real enough". Ie not just some shady impersonal account that constantly attempts to disrupt and only acts in non-contributive and disrupting patterns (no bad trolls basically).<br />
(II) If your account shows similarities with that of a bad troll you always invoke the chance of a potential misjudgment from our moderation team due to the unchangeable nature of the internet.<br />
<span style="font-weight: bold;" class="mycode_b">4. No unnecessary toxicity.</span><br />
(I) Do not start malevolent flame wars with other toxic members, if people join this community with the sole intention to troll or be non-constructively mean, they should be removed from the group.<br />
(II) Creating flame wars with all kinds of insults and toxic/nasty behaviour towards one another is a bad display for public channels. If you want to fight someone and they hate you too, start the fight in DMs.<br />
<span style="font-weight: bold;" class="mycode_b">5. Do not break the relevant Terms Of Service on the platforms we use.</span><br />
(I) Corporate and/or public community platforms like Discord have great reach and advantages. We do not want our community banned on those places. For the importance of freedom of speech freely access our self-hosted discourse platforms such as our <a href="https://matrix.to/#/#space-frontiers:comms.starwolves.io" target="_blank" rel="noopener" class="mycode_url">Matrix server</a> (currently offline).<br />
<span style="font-weight: bold;" class="mycode_b">Staff Rules</span>:<br />
<span style="font-weight: bold;" class="mycode_b">1. Punish users with an escalation method.</span><br />
(I) Severity of punishments are decided by the severity of the violation and depending on if the violator has previously been warned or punished before for (similar) violations.<br />
(II) The stair-case to punishment escalation involves several timeouts before more severe punishments are made.<br />
(III) If the violator is suspected to violate Rule 3.I the escalation staircase could be bypassed when there is a shortage of time/staff-manpower or if a wave of trolls is active.<br />
<span style="font-weight: bold;" class="mycode_b">2. Punishment code of conduct.</span><br />
(I) Incorrect punishments deem to be corrected and apologized for.<br />
<span style="font-weight: bold;" class="mycode_b">3. Staff code of conduct.</span><br />
(I) Staff members are not expected to aggravate members or situations for the sole sake of causing chaos.<br />
<span style="font-weight: bold;" class="mycode_b">Report disruptors and rule breakers by tagging or DMing staff members.</span>]]></description>
			<content:encoded><![CDATA[<span style="font-size: large;" class="mycode_size">The following rules apply to Star Wolves platforms and services such as the SS14 server and the official Space Frontiers Discord server.</span><br />
<br />
<br />
<span style="font-weight: bold;" class="mycode_b">0. Regarding minors.  </span><br />
(I) <span style="font-weight: bold;" class="mycode_b">NO minors below the age of 16 are allowed to be present or to partake in our server or services unless they are accompanied by parental consent AND by parental supervision.</span><br />
(II) Orderly and respectful conduct from adults around or towards minors is a standard that you must do your best to uphold at all times.<br />
(III) In and around the SS14 server and the default 16+ Discord channels you must always assume minors are watching and present, which means you must moderate your own behavior accordingly. Do not be overtly rude, vulgar or mean to other users; instead resort to pinging or messaging staff members to resolve issues.<br />
(IV) The SS14 server and the default 16+ Discord channels prioritize light-hearted, playful &amp; mutually courteous and respectful behavior. <br />
<span style="font-weight: bold;" class="mycode_b">1. No NSFW conversations or content.</span><br />
(I) No extreme vulgar, overly violent, disgusting, brutal or sexually explicit conversations or content.<br />
<span style="font-weight: bold;" class="mycode_b">2. With respect to freedom of speech.</span><br />
(I) We offer everyone the freedom of speech and freedom to offend inside our designated 18+ Discord channels. However, this freedom is not a given in our Space Station 14 game server or in the default Discord 16+ server channels.<br />
(II) But to a reasonable extend that doesn't result in the degeneracy of our chat. Please, dependent on the severity of the offending speech you may have outed, consider how often and when you would like to repeat it in this server.<br />
(III) We also offer a place to discuss controversial topics, but when you discuss or mention such topics ensure you do so with the right motives. It is easy to provoke a lot of emotions and chaos in the chat by being careless with what you write.<br />
(IV) Jokes about sensitive topics are okay but refer to Rules 2.II and 3 . We will do our best to allow for genuine jokes, but we keep our eyes out on controversial jokes a bit more. Just because sometimes the motivations aren't always to truly try and make people laugh.<br />
<span style="font-weight: bold;" class="mycode_b">3. No bad trolls.</span><br />
(I) Please ensure that the persona you represent in our server is "real enough". Ie not just some shady impersonal account that constantly attempts to disrupt and only acts in non-contributive and disrupting patterns (no bad trolls basically).<br />
(II) If your account shows similarities with that of a bad troll you always invoke the chance of a potential misjudgment from our moderation team due to the unchangeable nature of the internet.<br />
<span style="font-weight: bold;" class="mycode_b">4. No unnecessary toxicity.</span><br />
(I) Do not start malevolent flame wars with other toxic members, if people join this community with the sole intention to troll or be non-constructively mean, they should be removed from the group.<br />
(II) Creating flame wars with all kinds of insults and toxic/nasty behaviour towards one another is a bad display for public channels. If you want to fight someone and they hate you too, start the fight in DMs.<br />
<span style="font-weight: bold;" class="mycode_b">5. Do not break the relevant Terms Of Service on the platforms we use.</span><br />
(I) Corporate and/or public community platforms like Discord have great reach and advantages. We do not want our community banned on those places. For the importance of freedom of speech freely access our self-hosted discourse platforms such as our <a href="https://matrix.to/#/#space-frontiers:comms.starwolves.io" target="_blank" rel="noopener" class="mycode_url">Matrix server</a> (currently offline).<br />
<span style="font-weight: bold;" class="mycode_b">Staff Rules</span>:<br />
<span style="font-weight: bold;" class="mycode_b">1. Punish users with an escalation method.</span><br />
(I) Severity of punishments are decided by the severity of the violation and depending on if the violator has previously been warned or punished before for (similar) violations.<br />
(II) The stair-case to punishment escalation involves several timeouts before more severe punishments are made.<br />
(III) If the violator is suspected to violate Rule 3.I the escalation staircase could be bypassed when there is a shortage of time/staff-manpower or if a wave of trolls is active.<br />
<span style="font-weight: bold;" class="mycode_b">2. Punishment code of conduct.</span><br />
(I) Incorrect punishments deem to be corrected and apologized for.<br />
<span style="font-weight: bold;" class="mycode_b">3. Staff code of conduct.</span><br />
(I) Staff members are not expected to aggravate members or situations for the sole sake of causing chaos.<br />
<span style="font-weight: bold;" class="mycode_b">Report disruptors and rule breakers by tagging or DMing staff members.</span>]]></content:encoded>
		</item>
	</channel>
</rss>