tootik posts are Note
s and polls are Mastodon-compatible Question
s.
In addition, it supports Page
and Article
posts.
Different servers, frontends and clients use different HTML tags and attributes or even add extra whitespace when they construct content
from the user's raw input, so tootik's HTML to plain text converter is only a 80/20 solution. Most posts look fine and pretty much follow the way a web frontend renders them.
tootik users are Person
s.
tootik communities are Group
s.
tootik automatically sends an Announce
activity to followers of the community when to
or cc
of a post by a follower mention the community. In addition, tootik forwards the original activity but without wrapping it with an Announce
activity like FEP-1b12 says.
tootik's UI treats Group
actors differently: /outbox/$group
hides replies and sorts threads by last activity.
tootik implements draft-cavage-http-signatures-12 but only partially:
- It ignores query
- It always uses
rsa-sha256
, ignoresalgorithm
and putsalgorithm="rsa-sha256"
in outgoing requests - It validates
Host
,Date
(seeMaxRequestAge
) andDigest
- Validation ensures that key size is between 2048 and 8192
- Incoming
POST
requests must have at leastheaders="(request-target) host date digest"
- All other incoming requests must have at least
headers="(request-target) host date"
- Outgoing
POST
requests haveheaders="(request-target) host date content-type digest"
- All other outgoing requests have
headers="(request-target) host date"
tootik has no Application Actor. It uses a special user named nobody
to sign outgoing requests not initiated by a particular user.
This user can be discovered using WebFinger, just like any other user:
https://example.org/.well-known/webfinger?resource=acct:nobody@example.org
For compatibility with servers that allow discovery of the Application Actor, the domain is an alias of nobody
:
https://example.org/.well-known/webfinger?resource=acct:example.org@example.org
The sharedInbox
of other users points to nobody
's inbox, to allow wide delivery of posts.
tootik forwards replies (and replies to replies [...], until MaxForwardingDepth
) to followers of the user who started the thread.
tootik does not fetch missing posts to complete threads with "ghost replies".
tootik sets the outbox
attribute on users, so servers that don't rely on reply forwarding and fetch missing replies can do so. However, this collection only lists public activities.
tootik supports Mastodon's account migration mechanism, but ignores Move
activities. Account migration is handled by a periodic job. If a user follows a federated user with the movedTo
attribute set and the new account's alsoKnownAs
attribute points back to the old account, this job sends follow requests to the new user and cancels old ones.
tootik users can set their alsoKnownAs
field (to allow migration to tootik), or set the movedTo
attribute and send a Move
activity (to allow migration from tootik), through the settings page.
tootik supports Mastodon's follower synchronization mechanism, also known as FEP-8fcf.
tootik attaches the Collection-Synchronization
header to outgoing activities if to
or cc
includes the user's followers collection.
Received Collection-Synchronization
headers are saved in the tootik database and a periodic job (see FollowersSyncInterval
) synchronizes the collections by sending Undo
activities for unknown remote Follow
s and clearing the accepted
flag for unknown local Follow
s (see FollowAcceptTimeout
).