Skip to content

v0.7.0

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 15 Nov 01:10
· 4 commits to main since this release
Immutable release. Only release title and notes can be modified.
12178fc

Pre-release: this is a 0.x version and may change without notice.

Added

  • Desktop app: an optional local browser interface, opened by default (tui and the command-line actions stay). It has Play, Host and Both views and keeps the remote play target apart from local hosting: services start only when asked. It wires catalog approval, game grants for the trophy SDK, encrypted profile backup and restore, and the friend actions to its screens. The browser launch is private and one-use, reopening is authenticated, and a per-settings controller lock allows one controller per settings directory. Stopping the app stops only the host it started; a separately started server keeps running. This is a large change: the embedded screens, the authenticated controller, process ownership on Linux and Windows, the paired packaging and the regression tests belong to one workflow. See docs/client-ui.md. Not checked: hosting and the default-browser launch on native Windows, ARM hardware and a live game.
  • Desktop app: profiles, trophies and friends in the desktop: Profile, Trophies and Friends panes, explicit profile, trophy and friend command-line actions, and host-local companion administration. One desktop session owns its profile store, renews the game grant for its title and cancels social operations when it closes; an expired grant says it needs reissuing. The new native SDK and two-host tests are required in Linux CI and a Windows compile and link check of the SDK is added. See docs/app-framework.md.
  • Desktop app: an app framework (app/framework): a bounded, atomically written local profile and trophy store, a portable identity with encrypted backup and restore (AES-GCM, key from a passphrase of at least 12 characters), a loopback broker that gives each game title a scoped, revocable grant, and an opt-in TLS 1.3 social service and client with explicit host admission, per-host registration, consent-based friendships, blocking and host revocation. The C and C++ SDK is client/psnr_app.h and client/psnr_app.c with an example (client/examples/app_trophy.c). The game protocol and the server do not change: game names stay unauthenticated, a trophy report records only when it was received and proves neither an earned achievement nor a PSN account, and live presence, invitations, remote trophy sync and provider verification are not there. ROADMAP.md and SECURITY.md state the changed scope; see docs/app-framework-api.md.
  • Server: the read-only status page has Play, Host and Both views (a preference kept in the browser; Host grants no permission). Host shows the existing counters and limits, and Both adds the player tables. Appearance controls, keyboard use, narrow layouts and the tables without JavaScript are kept.
  • Docs and tooling: CITATION.cff: citation metadata that GitHub shows as "Cite this repository" (title, maintainer, repository and website, MIT licence, and the upstream psnr project as a reference); the repository layout check allows the file in the root.
  • Docs and tooling: BUILDING.md: a short page that points to where each part is built and tested (the server, the desktop app, the C client, the container image, release archives and the AppImage); the README's document list links it, and the repository layout check allows the file in the root.
  • Docs and tooling: KNOWN_ISSUES.md: what is known not to work or not to have been checked (early software, binaries and scripts not run on every platform, the experimental admin API, the relay off by default and other limits), each with a link to the page that says it in full; the README's document list links it, and the repository layout check allows the file in the root.

Changed

  • Desktop app: the app archives now contain the matching re-psn-host (the server, under that name) next to re-psn-app, and install.sh and install.ps1 install both with --app / -App. The pair is staged and rolled back if a move fails, but two files are not replaced atomically across a crash: stop the app and its host before updating. An older app archive without re-psn-host is refused, and an installed standalone re-psn is not touched. The Windows app is built as a windowed program (-H=windowsgui).
  • Docs and tooling: the issue chooser's link to the upstream issues says re-psn began as a fork of psnr, instead of "This is a fork." (.github/ISSUE_TEMPLATE/config.yml; the link and its target are unchanged).
  • Docs and tooling: the README's longest sentences are split (the fork history, the overview, the session steps, the desktop app and build paragraphs, the security list, the roadmap line and the closing paragraph); no fact, link or command changed.
  • Docs and tooling: docs/installing.md starts with "Install, step by step": numbered steps for Linux and for Windows, each with what the script prints, what to do when the folder is not on PATH, and how a failure shows. A few of the longest sentences in that page are split; no command, flag or behaviour changed.
  • Docs and tooling: the wording that called re-psn "a fork" in CONTRIBUTING.md, AGENTS.md, NOTICE.md, SECURITY.md and the website now says it began as a fork of psnr and is a repository of its own; the credit to upstream and the licence lines are unchanged. The security page heading "What this fork changes" is now "What re-psn changes".
  • Docs and tooling: the README's first screen is centred (banner, one-line description, badges) with a links line (Download, Quick start, Features, Install, Configuration, Documentation, Website, Report an issue), and its main sections are separated by horizontal rules. The "About this fork" section is now "About this project": it says re-psn began as a fork of psnr and is now a repository of its own, and the credits keep the upstream work and licence line as before.
  • Docs and tooling: the README and docker/README.md name v0.6.0 and its container image as the newest, and the features list says since 0.6.0, not main, for four rows that shipped in it (-no-peer-titles, the capability report, the C client's connect policy and the experimental admin API).

Fixed

  • Desktop app: a protocol request now honors its context while it waits for and uses the connection: acquiring the writer respects cancellation, cancellation is checked before a socket write, and a blocked write is interrupted. A frame interrupted half way closes the connection; cancelling a request that is only queued keeps it open. A request that already completed is not undone.
  • Client: the whole setup of psnr_stream_connect and psnr_stream_accept now runs under one monotonic deadline: an interrupted wait is retried with the time left (also for psnr_connect_timeout), partial reads and writes during setup are handled, a negative relay timeout still means no limit, and a successful call returns a blocking stream. The setup-deadline, interrupted-connect and native relay-pair tests are required in Linux CI.
  • Server: replies and pushes to a connection now leave in the order the room changed. Each control connection has one output queue, written outside the room lock, so a join, a leave, a disconnect clean-up and a relay offer can no longer overtake each other. A queue holds at most 2048 frames and 128 KiB; a connection that overflows it or fails to write is closed. The wire format and settings are unchanged.

Files

Each archive holds one self-contained server binary (no installer, no runtime needed), LICENSE, NOTICE.md and an examples folder (settings file, systemd unit, proxy configs).
The re-psn-app archives hold the desktop app (one static binary, LICENSE, NOTICE.md and its README) for the same three platforms. install.sh --app and install.ps1 -App install the app from a release instead of the server; or unpack one by hand.
The x86_64 AppImage holds the same Linux binary and examples as one runnable file; it needs FUSE to mount, or run it with --appimage-extract-and-run. It is not signed.
install.sh (Linux) and install.ps1 (Windows) are the install scripts from this tag, listed in SHA256SUMS too: download one with SHA256SUMS, check it, read it, then run it (see docs/installing.md).
Check a download with sha256sum -c SHA256SUMS --ignore-missing.

a2cb2925332e6ef80a9941c1f7ce1ea968bc6f30c8e4cd1c2c820aa3be1a205c  re-psn-app-v0.7.0-windows-amd64.zip
763d01d6855a4ad020db04f32c95639ce68f6eaf05d83f5c803d1340d50db366  re-psn-v0.7.0-windows-amd64.zip
352f3d2dc471f9f7c2eadc9472e64628cc77e57461c3e18d0e467ec6cf135a07  re-psn-app-v0.7.0-linux-amd64.tar.gz
7194b6a57e22bb2712566477dff1809932bd80f50e7595a5bbc301320b40214c  re-psn-app-v0.7.0-linux-arm64.tar.gz
a28e889621bff809a48aa2d40ee7995ad40ed58791e75fe3eb46f181ee98bf1d  re-psn-v0.7.0-linux-amd64.tar.gz
534435bea4d35c46df6372efc544549673cd538d4cfa224341699a9485aa8233  re-psn-v0.7.0-linux-arm64.tar.gz
3c1b9131819fa1be89acc413d8e0c9fe6efaa2b34761c6e1b2ba088f5b9b5687  install.sh
5a032a7c51990713491da3561b587d40d8e94bc4a1ba909d19d51e0aad7a0760  install.ps1
263c45975df4a7eacf4e0e7b4931c9892f87e7f658dd73e2a21e0fa3c6b0c0bd  re-psn-v0.7.0-x86_64.AppImage

Developed with AI agent assistance.

Next release: when ready