tag:github.com,2008:https://github.com/someodd/phorum/releasesRelease notes from phorum2025-03-21T03:23:26Ztag:github.com,2008:Repository/767286729/v0.7.0.02025-03-21T03:26:16Zv0.7.0.0<p>Phorum can now be served from a selector prefix, as if it's all within some subdirectory. See the <code>selectorPrefix</code> in config.</p>someoddtag:github.com,2008:Repository/767286729/v0.6.0.02024-06-25T09:08:50Z[v0.6.0.0] - 2024-06-25: Renamed to Phorum + Packaging<p>Project renamed to Phorum!</p>
<p>This release is based off a move to start packaging the software so it's more easily used<br>
and installed on servers. Namely, automation has begun to create a Debian package, but<br>
probably more options to come!</p>
<p>Part of the switch is I've stopped using Nix for packaging and a dev environment.</p>
<p>I won't mention changes to this repo that are outside the actual software itself in the<br>
changes below.</p>
<h3>Added</h3>
<ul>
<li>Config option for running as a specific user, if <code>phorum</code> is ran as root it will<br>
switch to the specified user.</li>
</ul>
<h3>Changed</h3>
<ul>
<li>Command line interface so you always specify a path to the config file with<br>
<code>--config</code></li>
<li>The "space cookie" config section is now the "daemon" config section</li>
</ul>someoddtag:github.com,2008:Repository/767286729/v0.5.0.02024-03-31T04:53:49Zv0.4.0.0: Reposting<h1>Added</h1>
<ul>
<li>Make gopher links out of posted URIs!</li>
<li>Special codes: you can define keys associated with strings in your <code>config.toml</code>, if a<br>
post's entire message is <code><somekey></code> where <code>somekey</code> belongs to an entry in the<br>
<code>specialCodes</code> table, then the post will be presented as the corresponding value.</li>
<li>Prevent the creation of threads with a message that already exists as a thread OP</li>
<li>Prevent accidental reposting + some spam by disallowing posting a reply which has the<br>
same IP and message as the last reply in the same thread. This is nice for preventing<br>
an index search result from being refreshed, when the user intends to simply refresh<br>
the thread, and it resulting in an accidental repost.</li>
</ul>
<h1>Changed</h1>
<ul>
<li>Rate-limit messages broken down into two separate messages for reply rate limit and<br>
new thread rate limit</li>
</ul>someoddtag:github.com,2008:Repository/767286729/v0.4.0.02024-03-14T07:50:07Zv0.4.0.0: Blank selector<p>Handle blank selector.</p>someoddtag:github.com,2008:Repository/767286729/v0.3.0.02024-03-14T02:24:01Zv0.3.0.0<h2>Added</h2>
<ul>
<li>Configurable maximum post length</li>
<li>Configuration for client sent an empty query language</li>
<li>Config options for spacecookie server</li>
<li>(Hopefully) more accessible reply + new thread links</li>
</ul>
<h2>Fixed</h2>
<ul>
<li>Give an error for when a post is too long</li>
</ul>someoddtag:github.com,2008:Repository/767286729/v0.2.0.02024-03-08T11:37:02Zv0.2.0.0: TOML + Rate-limiting!No content.someoddtag:github.com,2008:Repository/767286729/v0.1.0.02024-03-05T02:44:22Zv0.1.0.0: Initial Release/Proof of ConceptNo content.someodd