0.4
π Old Release
This is an old release, kept here for archival purposes. Unless you absolutely need it, see latest.
β¨ What's New?
- Support for Videos
- yt-dlp must be installed to do the processing
- File caching
- Images/videos from Bluesky will now be cached locally to improve performance when pushing files to other services
- This cache is automatically cleaned up periodically, but you can manually manage these files by deleting them from
<config-dir>/file-cache/
- Daemon/service mode
- Using
start
,stop
, andstatus
verbs, the relay service can run in the background as a daemon - Use
start --no-daemon
(orrun
) to run in the foreground, like previous versions - While running as a daemon, verbs such as
usernames
can be used alongside
- Using
- Changed default host (from
public.api.bsky.app
tobsky.social
) - Handle Mastodon-compatible services that don't allow markdown
- If posts including usernames that aren't mapped (via
usernames
), an attempt is made to fetch them via Bridgy Fed before falling back to posting the profile URL (similar to X)
- If posts including usernames that aren't mapped (via
- Fixed update checker picking up on pre-release versions
- Fixed failed service connections being unhandled
- Framework-dependent version
- .NET Runtime must be installed first, then ran with
dotnet Booski.dll
- .NET Runtime must be installed first, then ran with
π₯ Breaking Changes
- yt-dlp must be installed
- Threads support has been abandoned
- Although this feature never saw the light of day, references to it were visible in the UI: these have been removed. It may come again in the future, but don't hold your breath
βοΈ Development
These changes are important to note if you plan on building and/or contributing to Booski
- Moved
./publish.sh
to./tools/bash/publish.sh
- Added new lexicons to
Booski.Lib
Com.Atproto.Identity.ResolveHandle()
βcom.atproto.identity.resolveHandle
- Updated .NET packages (
Microsoft.*
) to .NET 9.0-rc1 - Due to dotnet/runtime#72604, only .NET 9.0 (currently in RC) is supported. There are no plans to support .NET 8.0 (or below) as Microsoft seem entirely unwilling to fix this issue for those versions