I added the ability to manage property values on users' profiles to #Enigmatick.

[jdt@enigmatick.social]

I added the ability to manage property values on users' profiles to #Enigmatick. As I'm using this more as my full-time #Fediverse platform, I'm running into things that I've sort of blown off in the past as silly or unnecessary but finding useful now.

In this case, I implemented it using Add and Remove messages posted by the client (a single-page application in Svelte mediated by a wasm module) to the user's outbox on the server. The Actor is the target and the PropertyValue is the Object.

It's not canonically how those #ActivityPub messages should be used (e.g., managing a Collection - the attachment field on an Actor is not really a Collection). But I think logically it makes sense. And it's client communication only; those activities are not federated. When a profile is updated via the Add or Remove, a separate Update is sent out to known servers to update the profile.

Also, I may have gone a little overboard with my own properties.

[smallcircles@social.coop]

@jdt very nice!

To what extent are you, or do you intent to, support the #ActivityPub #C2S parts of the spec? I am keeping track of a list of projects who do, at:

https://codeberg.org/fediverse/delightful-fediverse-experience/issues/130

[jdt@enigmatick.social]

@smallcircles@social.coop That's my plan. I don't use any kind of session management, so all authenticated actions use HTTP signatures generated by a dedicated client key provided by the wasm module in the browser. I want to avoid any unique API calls as much as I can (although I do have a few right now).