v2.0.0

It's been exactly one month since I released Needle v1.0.0, and you gave me lots of good feedback! A total of 75 servers currently have Needle in their server. This update addresses the most common feature requests and bug reports. I have categorized the updates so it is easier for you to find what you're looking for. These release notes do not list every single change, only the most important ones. If you wnat to see every single change, see the full changelog: v1.0...v2.0.0.

General

• We changed the license from GPL-3.0 to AGPL-3.0-or-later (#38)
  Please take a moment to read through the LICENSE again to see the updated terms and conditions for using and interacting with this bot and its source code.
• We've added a privacy policy (#40)
  The privacy policy explains what data we collect. Take a moment to read through it (it's not very long). This is done in preparation for requesting bot verification from Discord.

The bot

• Threads will now archive immediately (#25)
  When users press the archive button or invoke the /close command, the threads will archive immediately by default (instead of setting the auto-archive duration to 1 hour).

  This behavior is customizable with the new archive-behavior option under /configure auto-threading. Set this to ⌛ Archive after 1 hour of inactivity to revert the behavior to how it was before v2.0.0.

• Better default look of archive-button (#31)
  We want people to archive their threads when they are done! This makes the side-bar less cluttered and gives less work for moderators. In version 1.0.0, the archive button looked very scary. We made it friendlier!

  v1.0.0	v2.0.0

• Less verbose messages
  As many of you noted, Needle was very noisy by default. This update addresses that, and has much better default messages. I'm planning on making the verbosity configurable in a later release, but make it less verbose by default is definitely the way to go.

  v1.0.0	v2.0.0
  	OR

• You can now have new-lines in custom auto-thread messages (#37)
  When writing the value for custom-message under /configure auto-threading, you can now write \n to make new lines.

• 🆕emoji that indicate threads without replies (#8)
  Threads that have not received a reply from another user is prepended with 🆕 so that they can be easily identifiable in the channel list. It will remain even if users change the thread name with /title. The emoji is removed as soon as another user replies in the thread, or when the thread is archived.

  This feature is enabled by default, but can be turned off with /configure emojis enabled: False.

• Configuration is removed when the bot is kicked (#36)
  In order to not waste disk space and also lower our data retention, guild configurations will be removed once Needle is kicked. You can read more about this in the issue and the privacy policy.

• Improved detection of thread owners (#49)
  Previously, if users removed the message that started a thread, we could no longer determine who created the thead, which meant that those users could not archive that thread anymore or change the title. It was also unclear for other people who owned the thread. This is no longer a problem, see more details in the issue.

• Fix bug with server boost downgrade (#23)
  See issue for more details

• Fix bug with custom message variables (#51)
  See issue for more details

• Renamed /configure autothreading to /configure auto-threading
  Consistency!

• Activity now says Listening to /help
  This helps new users understand how to interact with the bot.

• Removed unused message keys

Developers

• Minimum node version is changed from 16.6.0 -> 16.9.0
  This is imposed by Discord.js

• Added dependabot
  Dependabot will now create pull requests for package upgrades.

• See license changes noted above
  If you are going to self-host the bot without changing the source code, you do not have to disclose the source. However, if you are going to make modifications to the bot's code and plan on self-hosting it, you do need to disclose your source.

Thank you 💜

Thank you to everyone who has created issues and joined the discussion in the Discord server! It's really fun to get such good feedback and suggestions on improvements.

Special thanks to @nchristopher and @c43721 that have contributed massively to this project by reviewing and submitting PRs and keeping me in check when I try to do wonky things!