Releases: dimkr/tootik
Releases · dimkr/tootik
0.14.0
Added
- Support for multiple client certificates
- With list of certificates at
/users/certificates
, each with SHA-256 fingerprint and expiry date- Will show
2100-01-01
for certificates added before 0.14.0 - With ability to approve or deny a newly added certificate, or revoke access for a previously approved certificate
- Will show
- With list of certificates at
- Validation of client certificate expiry date when authenticating
- Forwarding of Update and Delete activities
- For replies in a thread started by a user with followers
- For posts and replies in a community
- Result graphs for polls without any votes yet
Removed
- Ability to select the username duration registration and override what's in the CN property of the client certificate
- Attempts to register with an existing username add the client certificate to the list of certificates waiting for the user's approval
Bug Fixes, Performance and Maintenance
- Poll results are updated to 0 when all votes are deleted
- Undo activities are sent to the recipients of the matching Create activities, plus current followers
0.13.0
Added
- Bookmarked posts
- Improved compatibility with Friendica and possibly other ActivityPub servers with Group actors
- More friendly error messages when profile changes are throttled
Removed
- Support for fetching public posts through the user's
outbox
endpoint: it seems unused
Bug Fixes, Performance and Maintenance
- The default configuration now makes sqlite run in
synchronous=NORMAL
mode - The special "nobody" user is now of type Application, clearly marking it as an "instance actor"; this may improve compatibility with other implementations of ActivityPub
- Dependency and Go updates
- Reduction of gopls warnings
0.12.6
Added
- More user-friendly error messages when posting or editing is throttled
Removed
- Graceful termination of the HTTP server during shutdown
Bug Fixes, Performance and Maintenance
- Fix for deadlock during shutdown when waiting for Gemini or Guppy requests to finish
- Fix for inability to delete a reply when the parent post is deleted
0.12.5
Added
- Logging of the user name when handling Gemini requests, including invalid ones
Removed
- The restriction that prevents users from voting on their own polls
Bug Fixes, Performance and Maintenance
- Dependency and Go updates
- Various README.md improvements
0.12.4
Added
- HTTP response sizes are now validated against the new
MaxResponseBodySize
configuration key, instead ofMaxRequestBodySize
Removed
- The
GuppyResponseChunkSize
configuration key
Bug Fixes, Performance and Maintenance
- Guppy responses are now line-buffered and streamed
- Cached responses are now sent in multiple chunks and not as a single chunk
- More resolver tests with coverage for edge cases like huge responses
0.12.3
Added
Nothing!
Removed
Nothing!
Bug Fixes, Performance and Maintenance
- Thread view is now streamed
- HTTP requests are now handled with 30s timeout
- More efficient handling of big HTTP responses
- Fix for breakage of search when using Guppy
- Encapsulation of function arguments and logging through the default logger
- Dependency and Go updates
0.12.2
Added
- The
Content-Length
header, in outgoing POST requests, to allow validation and memory pre-allocation in the receiving server - Validation of the
Content-Length
header againstMaxRequestBodySize
(if specified), instead of readingresponse[:MaxRequestBodySize]
, trying to parse it and failing if truncated
Removed
Nothing!
Bug Fixes, Performance and Maintenance
- Followed users list is now faster because it uses the new
feed
table to sort followed users by latest activity, and the page contents are streamed while reading result rows - Fix for harmless warnings about inability to send the response, when generating a cached response
0.12.1
Added
- Gemini and Gopher responses are now steamed in 16 line chunks
- Clients that stream page contents now allow the user to start reading the page before everything is received: for example, read the post before the replies section has been received
- The server continues to build the next response chunk while sending the previous one, instead of blocking on network every time a line is appended to the response: if latency is low enough to receive 16 lines while the server is busy building the next ones, most pages should take less time to fetch fully
Removed
Nothing!
Bug Fixes, Performance and Maintenance
Nothing!
0.12.0
Added
- A periodic job that precomputes the feed (
/users
and/users/mentions
) - Configurable data retention periods
Removed
Nothing!
Bug Fixes, Performance and Maintenance
- Go and dependency updates
0.11.4
Added
Nothing!
Removed
Nothing!
Bug Fixes, Performance and Maintenance
- Fix for 400 from Lemmy when poster was registered since 0.7.0