Confusion that arises with me is in how I conceptually perceive the notion of self-sovereign identity. Namely as your identity in some digital representation, that is decoupled from the data you own and where it resides. Where SSI allows one to have nomadic homes just as well.

Maybe that is not the case in how the standards are developed and 'something extra' i.e. nomadic identity is required.

Either that or it may be better named to avoid the confusion with other uses of "identity".

The issue with digital identity is that people don’t have a single, unified identity. Identity, like many things, is a social construct, not part of some natural order. As a dual national, I'm acutely aware that when and how I assert an identity credential, or characteristic, depends on context. Therefore, digital systems that help us assert these identities must be responsive to people’s contextual needs and under their control. Otherwise, we’re just building more surveillance tools.

While developing the initial version of the #polls for #ActivityPub#WordPress plugin, I so often got reminded to the preamble words of @gancio from @lesion

"Building software means taking a stand, making decisions, choices. These choices start from a precise look at reality, from specific needs and ends implementing specific features, choose default values, simplify some flow and patterns while making difficult others."

It's just a tiny poll plugin, but there are still decisions to be made: For example, when to reveal the poll vote counts, to whom, and when to reset the vote counts (e.g. when changing the type from single choice to multiple).

There are many flow patterns that I don't consider worth striving for. Please help me by leaving some comments on the scenarios you can imagine.

Interested. I collected some C2S resources together before.

I can offer forum space and matrix chatroom, if you are interested. 'Groundwork labs' on Social coding commons is themed to exploring the foundational technologies of social web / fediverse.

There's no membership, just affiliation. Groundwork labs is a fellowship, where interested parties collaborate, not a community.

https://discuss.coding.social/c/fellowships/groundwork-labs/42

https://matrix.to/#/#groundwork-matters:matrix.org

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

I did not mention a #SocialHub thread. There are multiple discussions where various aspects were discussed, that might still be useful. The search facility is best way to find them.

As for AndStatus the github issue lists their step-by-step progress in investigating what was needed, and what the challenges were. One of them was unavailibility of appropriate server back-ends to test against, mentioned *at the time* as challenge.

Would ❤️ more #ActivityPub C2S dev.

@smallcircles
> what is needed client-side can be found in the AndStatus project ... there were among others no server implementations to test against

Seems like Pleroma had it working before mid-2020;

https://pleroma.social/announcements/2020/05/10/pleroma-security-release-2-0-4/

The Epicyon server has support for AP C2S too, so that could also be used to test apps trying to implement it;

https://libreserver.org/epicyon/

Was any of this mentioned in the SH thread?

#ActivityPub #APC2S

@skyfaller @hugh
@bob