Re: Issue triage today

čt 13. 7. 2023 v 0:41 odesílatel Evan Prodromou <evan@prodromou.name>
napsal:

> Yes, great idea.
>
> I think the current plan is to document the behaviour of Mastodon in this
> area, as step one, with a Note or FEP.
>
> We'd probably need to then discuss problems with the Mastodon technique,
> namely:
>
> 1. If the origin server goes offline, there's no way to move the account.
> 2. Similarly if the account is defederated.
> 3. All activities and content stay at the origin server, which keeps their
> URLs active, but doesn't help if the server goes down.
>

An area where JSON-LD shines is to download content and merge or move it to
another place.  It was designed for that use case.

It does require cooperative servers though.  How do we figure out which
servers cooperate though?  Shutting down of a server can be partially
mitigated by incrementally archiving data too.

It's also the case that the structure of the profile and data can be in
some cases strongly tied to the server, and in other cases loosely tied.
More flexible profile examples could help instances that regularly move
users.


>
> The topology of the fediverse is such that most  users have gratis
> accounts on small, unstable, volunteer-run servers, donation-supported.
> That has made this migration process very important.
>
> I'm personally a fan of using a domain as your identity, and moving from
> service provider to service provider as needed, transparent to your social
> connections. But that's not the fediverse we've got right now.
>
> Evan
>
> On Jul 12, 2023 18:19, Melvin Carvalho <melvincarvalho@gmail.com> wrote:
>
>
>
> st 12. 7. 2023 v 23:05 odesílatel Evan Prodromou <evan@prodromou.name>
> napsal:
>
> A quick report on outcomes:
>
> - #296 <https://github.com/w3c/activitypub/issues/296> has been pending
> review for about a month, so it was closed today
> - #294 <https://github.com/w3c/activitypub/issues/294> has been pending
> review for about a month, so it was closed today
> - #297 <https://github.com/w3c/activitypub/issues/297> points out a
> discrepancy in the spec where a behaviour is defined as MUST, yet is
> defined to be overruled in other parts of the spec. Proposed resolution is
> to include an erratum to rephrase it as a SHOULD, to reflect actual usage.
> - #299 <https://github.com/w3c/activitypub/issues/299> suggested that the
> original point (addressable contact lists) be made into a FEP, and added
> documentation for best practices for the `streams` property
> - #300 <https://github.com/w3c/activitypub/issues/300> is about a
> particular property but branches into discussion of account migration.
> Merged into #357 <https://github.com/w3c/activitypub/issues/357> and
> provided a plan for documenting account migration current status, and then
> standardizing improvements.
>
>
> formerlyKnownAs and account migration seems a very big topic, almost worth
> a spec in its own right, and it ties into so many other things
>
> Could we perhaps tag issues related to migration with it's own label,
> namely "migration"?
>
>
>
> Thanks to everyone who attended the session. It really helps a lot to have
> people around for it!
>
> Evan
>
> On Jul 12, 2023, at 11:00 AM, Evan Prodromou <evan@prodromou.name> wrote:
>
> As on most Wednesdays, I’ll be doing issue triage on the ActivityPub
> GitHub issues today at 11:30AM ET.
>
>
> https://meet.jit.si/moderated/c1c3c53fd2a3a78819e0cbb534848202b26b6af380c0af284edab895e35cb3c1
>
> All CG members and other interested parties are welcome.
>
> Evan
>
>
>
>