I would love this but unfortunately lemmy doesn’t have it yet. it’s not even a complex feature to implement locally though — maybe federating the data is a bit more complex, but my gut says it could just be a new field on each ActivityPub person. permissions on who could assign flairs and scoping to communities is possibly a bit more complicated, but it’s all pretty solvable in general
yeah nfi what activitypub looks like, I’ve so far still managed to avoid having to stare into that abyss. I could conceptually see a possible issue on the federated side for resolving whatever may be in that field, but dunno if that’s not something that’s already provided for at protocol. indeed quite easy locally
I would love this but unfortunately lemmy doesn’t have it yet. it’s not even a complex feature to implement locally though — maybe federating the data is a bit more complex, but my gut says it could just be a new field on each ActivityPub person. permissions on who could assign flairs and scoping to communities is possibly a bit more complicated, but it’s all pretty solvable in general
and now I kind of want to do it
yeah nfi what activitypub looks like, I’ve so far still managed to avoid having to stare into that abyss. I could conceptually see a possible issue on the federated side for resolving whatever may be in that field, but dunno if that’s not something that’s already provided for at protocol. indeed quite easy locally
ideally it should ignore fields it doesn’t already know for forward compatibility, though a lot about how lemmy works is pretty far from ideal