Start move to unify ID generation
All checks were successful
/ docker (push) Successful in 4m14s

This commit is contained in:
Melody Becker 2025-04-28 17:28:28 +02:00
parent aa2b056f8b
commit d32818af09
Signed by: mstar
SSH key fingerprint: SHA256:9VAo09aaVNTWKzPW7Hq2LW+ox9OdwmTSHRoD4mlz1yI
8 changed files with 51 additions and 8 deletions

View file

@ -103,8 +103,10 @@ type ConfigMail struct {
}
type ConfigSelf struct {
// The display name of the server actor
ServerActorDisplayName string `toml:"server_actor_display_name"`
ServerDisplayName string `toml:"server_display_name"`
// The name of the server provided via nodeinfo
ServerDisplayName string `toml:"server_display_name"`
}
// Contains experimental features that could be good to have
@ -120,11 +122,20 @@ type ConfigExperimental struct {
// implementations
// Both are created and stored for each local user. If this flag is enabled,
// Linstrom shares the ED25519 key on request, otherwise the RSA key
// Changing this setting after connections to other servers have been made might cause
// invalid signature problems where the remote server will use the old key instead
// of the new one. This is not really viable to fix within Linstrom
UseEd25519Keys bool `toml:"use_ed25519_keys"`
// Require authorized fetch signing for requests to the server actor too
// The implementation itself is stable, but might cause issues during initial connect
// if the other server also requires authorized fetch for the server actor
// Changing this setting is not expected to cause permanent problems
AuthFetchForServerActor bool `toml:"auth_fetch_for_server_actor"`
// Use cuid2 for generation of new IDs that are expected to be used via Activitypub
// They are shorter than the main method used (uuid v4) but should still provide enough
// uniqueness such that collisions are not to be expected.
// Changing this option will only affect new ID generations, not update existing ones
UseCuid2Ids bool `toml:"use_cuid2_ids"`
}
type Config struct {