Re: The Web's Missing Piece: How DID-Nostr Quietly Solves Social Portability

út 23. 9. 2025 v 16:30 odesílatel Evan Prodromou <evan@prodromou.name>
napsal:

> I think your assumptions are incorrect.
>
>    - ActivityPub is not focused on microblogging. It covers a lot of
>    different types of activities. It defines side effects for
>    activities focused on content creation and sharing (CRUD, sharing, etc.)
>    but it supports other types of activities. We have 30 activity types in the
>    Activity Vocabulary, and AP is extensible so you can add new activity and
>    object types.
>    - We have a directed social graph as part of ActivityPub, and we cover
>    the creation and maintenance of that graph pretty extensively in the spec.
>
>
Thanks, Evan, I take your point. While ActivityPub was designed for a broad
set of activities, in practice the primary use case so far has been
microblogging.

On the social graph side: AP certainly has a directed graph model, but it
feels like there is more room to explore. For example, tighter integration
with Solid WebIDs might have given us a more browsable Linked Data social
graph. And looking forward, DIDs and URIs could let us describe and connect
richer social graphs across different open protocols in a uniform way.

Seen that way, DIDs may provide a useful kind of “glue” for heterogeneous
open protocols to interoperate.

So perhaps the opportunity is less about inventing new machinery, and more
about using what’s already there and making it portable across stacks.


>
>
> Evan
> On 2025-08-29 5:00 a.m., Melvin Carvalho wrote:
>
> Much of the SWICG focus is currently on the microblogging use case, and
> streams of activities. Outside our group, though, “social web” often means
> people, friends, and connections, the Facebook-style social graph. I’ve
> been exploring whether today’s W3C building blocks can make a portable,
> URI-addressable social graph practical, alongside streams rather than
> instead of them.
>
> The blog post uses Nostr, self-sovereign, portable, identity as a worked
> example, but the graph model aims to be broadly compatible with
> ActivityPub, Bluesky/AT, Solid, and the wider social web. The intent isn’t
> to pick winners, just to surface a simple, portable graph that could serve
> as common ground across stacks. Perhaps useful food for thought, for some
> here.
>
>
> https://dev.to/melvincarvalho/the-webs-missing-piece-how-did-nostr-quietly-solves-social-portability-1bg
>
>