Conversation

Here’s a neat architecture/class design question, most ActivityPub implementations have different styles of handles compared to Bluesky/AtProto

ActivityPub @alice@example.com
Bluesky alice.example.com

Kaiteki stores author information as id, username and host. This makes sense for Twitter and Mastodon and the like. However this is incompatible with Bluesky. So… hmm..

1
0
0
@Kaiteki what if author information for bluesky was forcibly adapted to the kaiteki schema? as in, if the user is a subdomain, rewrite it to @alice@example.com, and if the user is using a domain of their own, rewrite it to @alice.tld@example.com
1
0
0
@Kaiteki or copy the tld for username and host and add a case match on FE that will shorten them if matching
1
0
0

@m That is an option however doing this will manifest elsewhere where Kaiteki is used to the double @ system.

I think this is in general an issue that Kaiteki is not allowing different kinds of handles.

0
0
1