10 releases 10 tags

RSS feed

• v1.2.7 db14d0e444

  Compare

  v1.2.7 Stable

  k4wit0 released this 2026-10-18 16:27:03 +02:00 | 9 commits to main since this release

  Added

  • The team is told when a comment is waiting for review. A visitor's comment, or a follow-up from whoever reported, now reaches the repository's channel, so it no longer sits in the queue unseen.
  • Whoever reported something and left an address is written to when the team replies, and when the issue on the forge is closed or changes state, as they already were when the team changed a status in the panel.

  Downloads

  • SHA256SUMS
    6 downloads · 2026-10-18 16:27:03 +02:00 · 257 B
  • SHA256SUMS.sig
    3 downloads · 2026-10-18 16:27:03 +02:00 · 89 B
  • lasthelp-linux-amd64
    3 downloads · 2026-10-18 16:27:04 +02:00 · 15 MiB
  • lasthelp-linux-arm64
    3 downloads · 2026-10-18 16:27:05 +02:00 · 14 MiB
  • lasthelp.service
    3 downloads · 2026-10-18 16:27:06 +02:00 · 2.7 KiB
• v1.2.6 4ddfb4dded

  Compare

  v1.2.6 Stable

  k4wit0 released this 2026-10-12 16:41:11 +02:00 | 18 commits to main since this release

  A clearer third point on the front page

  Changed

  • The third point of the front page says what a visitor gets: every report shows where it stands, from new to shipped, in the twenty languages. It used to say that reports can become forge issues, which an installation without a forge never has.

  Downloads

  • SHA256SUMS
    19 downloads · 2026-10-12 16:41:11 +02:00 · 257 B
  • SHA256SUMS.sig
    16 downloads · 2026-10-12 16:41:11 +02:00 · 89 B
  • lasthelp-linux-amd64
    19 downloads · 2026-10-12 16:41:16 +02:00 · 15 MiB
  • lasthelp-linux-arm64
    5 downloads · 2026-10-12 16:41:18 +02:00 · 14 MiB
  • lasthelp.service
    17 downloads · 2026-10-12 16:41:18 +02:00 · 2.7 KiB
• v1.2.5 89675b8925

  Compare

  v1.2.5 Stable

  k4wit0 released this 2026-10-12 15:33:24 +02:00 | 23 commits to main since this release

  A picture beside every name, and a safer text for the forge

  Added

  • Replies and comments no longer draw initials. Everybody gets a picture beside their name: one figure in a light grey for whoever reported or commented, and the same figure with its colours turned round and a stronger grey for the team.
  • A team member's own picture shows beside their replies on public pages, and in the panel's lists and menu. It is public, like their name already was; somebody who has chosen none keeps the default.

  Fixed

  • What a stranger wrote is made inert before it reaches the forge. An issue body is read there as Markdown, so a mention notified people, an image loaded from a host the writer chose, a link hid its destination and, on one forge, a line starting with a slash could run a command. The report text and every answer now have those characters escaped, with code left exactly as written.
• v1.2.4 081edf38bd

  Compare

  v1.2.4 Stable

  k4wit0 released this 2026-10-11 20:29:55 +02:00 | 28 commits to main since this release

  Replies follow renamed accounts, History with open and closed, and the house colours

  Added

  • The archive tab, now called History, splits the published reports into All, Open and Closed, each with the number it shows. Under Closed, Done and Not done tell a delivery from a report the team turned down.
  • In History, a repository's heading folds its reports away and opens them again, and the choice is kept in your browser.

  Changed

  • The panel is laid on the page's own ground, with its menu and cards one step above it, in both themes, and the light background, the two text greys, the light border and the dark text are the values the rest of the family uses.
  • Go 1.27.2 and x/net 0.60.0, which fix the standard-library and HTTP/2 advisories the vulnerability scan reports. The scan now runs before a release is tagged, so a release that reaches an advisory cannot be cut.
  • The toolchain and dependencies are up to date: Bun 1.4.3, Docker CLI 29.9.0, buildx 0.38.0, and the Go modules crypto, image, net and SQLite.

  Fixed

  • A team reply is signed with the name the account has now: renaming an account used to leave its earlier replies under the old name. Replies written before this version are matched to the account that holds their name today, and a rename claims the ones still signed with the name it leaves.
• v1.2.3 3dc615e8cb

  Compare

  v1.2.3 Stable

  k4wit0 released this 2026-10-07 20:17:52 +02:00 | 48 commits to main since this release

  A declined idea reads as the rest do

  Fixed

  • In Spanish, the status of a declined idea is "Descartado", agreeing with "Nuevo", "Planificado", "En curso" and "Entregado" instead of standing out as the only feminine one on the Closed tab.
• v1.2.2 955d016f10

  Compare

  v1.2.2 Stable

  k4wit0 released this 2026-10-07 20:00:48 +02:00 | 52 commits to main since this release

  Closed reports say what the team decided

  Added

  • On the Closed tab, two switches — Done and Not done — narrow the list to what was shipped or fixed, or to what the team declined or could not reproduce, each with its count. Pressing the one that is on shows both again, and the choice is kept in the address.
  • The similar reports offered while somebody types a title now show what the team decided about a closed one, with a line saying a closed report takes no more votes, so it can be read before asking for the same thing again.

  Changed

  • An idea the team does not take on is Declined and a bug it could not reproduce is Couldn't reproduce, translated by hand in all 20 languages. They were "Not planned" and "Can't reproduce".
  • A closed "no" no longer looks like a delivery: a shipped or fixed report is green and solid, a declined one has a dashed edge and a hollow dot. A fixed bug used to be the same grey as a declined idea.
• v1.2.1 7fff97c28f

  Compare

  v1.2.1 Stable

  k4wit0 released this 2026-10-05 16:21:51 +02:00 | 57 commits to main since this release

  Stored secrets show as dots

  Changed

  • A saved token or secret — a notification channel's token, an organisation's forge token and its webhook secret — is shown as dots: it is there, and which one it is cannot be seen, and there is no eye to reveal it. Write over the dots to replace it, empty the field to remove it, or leave the dots to keep it. The checkbox that removed a channel's token is gone.
  • An organisation's forge token and webhook secret are changed one at a time: replacing one leaves the other, and an empty field keeps what is stored. Removing the token disconnects the organisation from its forge.

  Fixed

  • Saving only the forge token, as the setup wizard does, no longer empties a webhook secret that was already stored.
• v1.2.0 1944bb76cd

  Compare

  v1.2.0 Stable

  k4wit0 released this 2026-10-05 07:56:44 +02:00 | 62 commits to main since this release

  Anti-abuse, notifications and a grace window

  Added

  • An Anti-abuse screen under This server: the word list as a form and a list, with edit and remove in each row, a search and pages of ten, how many reports each word has refused, and how many submissions each check turned away, by repository.
  • When an administrator rejects a report from the queue, the word that gave it away can be added to the list in the same step.
  • A notification channel for the whole server, set once under Notifications and chosen by each repository in its own list. A repository that does not choose it is not affected.
  • A Send a test button on notification channels, which says why a message did not arrive: a refused token, an address that does not exist, a service that cannot be reached, no mail relay, or an installation working offline.
  • Ctrl+K (⌘K on a Mac) goes to the search box on every screen.

  Changed

  • The word list matches whole words, so "ass" no longer refuses "class", and finds a word anywhere in a sentence in Chinese, Japanese, Korean and Thai, which have no spaces. Capitals and accents do not matter. A list written for the old matching may need a word or two added.
  • A repository's notification form shows the saved address and recipient after saving. The token is never shown; leave it empty to keep the stored one, or tick the box to remove it.
  • An answered report stays open to its reporter and to the team for 48 hours after the answer, and the page says until when. Visitors still cannot comment as soon as it is answered.
  • A board's card on the front page counts every report it has had, answered or not, instead of only the open ones.
  • The reports screen's search shortcut is Ctrl+K instead of "/", and the board page's search uses the same box as the rest of the product.

  Fixed

  • Usernames can no longer contain <, >, ", ', & or control characters. Accounts that already have them keep their names.
  • The address a reporter leaves must be one plain mailbox.
  • In a narrow reports pane, the sentence beside the approve, reject and spam buttons was squeezed into a column of a few letters.
• v1.1.0 fd1899d670

  Compare

  v1.1.0 Stable

  k4wit0 released this 2026-10-03 03:26:33 +02:00 | 76 commits to main since this release

  Pictures on a report

  A screenshot is often the quickest way to show a bug, so reports can now carry them. Installations update in place — from the panel, the installer or a new image — and keep everything they hold; the update adds the table the pictures live in.

  Added

  • Pictures on reports. The person reporting can attach up to five screenshots to a report and three to each follow-up, and the team can add three to each reply. Nothing is shown until the team has looked, and it can take out a single picture and approve the rest. The server draws every picture again, so the place and the camera a photo carries are not kept.
  • A picture opens large over the page, with the arrows to move between them and Escape to go back.
  • A switch per repository for pictures, in its settings.
  • Each repository card on the front page shows how many bugs and ideas are open, and the two kinds wear their colours wherever they appear.

  Changed

  • An answered idea or bug takes no more votes, comments or replies. The thread stays, and reopening the report opens it again.
  • Pictures are erased 30 days after their report closes, and at once when a report or a message is rejected, marked as spam or deleted.
  • The limits on the words of a report count characters, not bytes: a report in Japanese or Chinese was refused at about a third of what English was allowed.
  • After updating, every repository takes pictures. Turn them off in its settings if you prefer.

  Fixed

  • Pictures can be added to the front page from Safari on a Mac or an iPhone.
  • Long words with no spaces, like a pasted address or a log, stay inside the report's card instead of running off it, most of all on a phone.
  • A vote or a comment on a report that was folded into another or turned down is refused instead of being accepted and lost.
  • A build made between two releases is no longer offered the release before it as an update.
• v1.0.0 9f09ac33f6

  Compare

  v1.0.0 Stable

  k4wit0 released this 2026-09-29 17:22:13 +02:00 | 101 commits to main since this release

  The first stable release

  The first stable release of LastHelp, a self-hosted feedback portal that speaks to your forge. There is no earlier stable to compare it with, so these notes describe what LastHelp is rather than what changed. Installations that followed the betas update in place — from the panel, the installer or a new image — and keep everything they hold. Two things are not there yet: a bridge to Bitbucket, and a screen in the panel for the anti-abuse word list and the refusal counts, which work and are set and read as the documentation describes.

  Added

  • Reporting without an account. Anybody can send a bug or an idea from one form. What they get back is a secret link to their own report, which is why no sign-up is needed.
  • Bugs and ideas as two journeys. A bug is asked which version and how to see it happen, and is not voted. An idea is one sentence, gathers votes and ranks by them.
  • Similar reports while typing, so the same problem gathers votes and comments instead of duplicates.
  • A public board per repository, with open and closed reports apart, filters and search kept in the address, and a page at a time.
  • A roadmap nobody maintains. Three columns built from the state of each report, so it cannot go out of date.
  • Reports, the team's one screen. Every repository you work on in one list, with the report beside it: publish, reject or spam with a key each, edit its words, change its status, reply, edit or delete any comment, merge a duplicate, or open or link a forge issue. The same screen is the archive of every report ever sent.
  • An overview of the last thirty days, the most wanted ideas, the newest reports and the work per repository, each number leading to the list it counts.
  • Organisations and repositories with two levels of trust. A lead runs an organisation, its forge token and its repositories. A collaborator triages the repositories they are given and never sees the token. Both can carry an icon.
  • A front page you compose from bands of modules — the repositories, the most voted ideas, what was resolved, statistics, links, and your own words and images — arranged on a grid in the page itself.
  • A bridge to GitHub, GitLab, Gitea and Forgejo, including forges on your own network. A report becomes an issue or is attached to an existing one, and follows it when it closes or reopens. Work goes through a queue with backoff, so a forge that is down delays an issue instead of losing a report. Running without a forge is supported.
  • Notifications for the team through ntfy, Gotify, a webhook or mail, per repository. Reporters can follow an Atom feed that needs no account, or leave an email when a mail relay is configured; the address is deleted when the report closes.
  • Anti-abuse without a third party. A signed single-use form token, a timing window, a honeypot, rate limits by address and network block, duplicate and link heuristics, an operator word list, and a breaker that closes a repository for a while. Nothing is published without a person, and every refusal is counted by layer.
  • Signed releases and a verified updater. Checksums are signed with Ed25519. The updater in the panel checks the signature and the checksum, makes the new binary prove it runs, refuses one older than the database and takes a backup before it swaps, showing each step.
  • One binary, one SQLite file. A one-line installer with a hardened systemd service, --uninstall and --purge, and Docker images for linux/amd64 and linux/arm64.
  • Twenty languages, translated by hand, with right-to-left layout for Arabic, Persian and Urdu.
  • Installable as an app from the browser when served over HTTPS.