@jonny@neuromatch.social tracks doesn't it 😝

@julian
@evan @benpate @PortaFed
Can't make heads or tails of this one

Warm up the fire! We're LIVE!

Summer in Winter: Norcal Gma 2's Journey with her Dog - E79

#owncast #streaming #interview #fediverse #fedi #people #show #firesidefedi #FsF

https://stream.firesidefedi.live

@PortaFed That's awesome. Let's work you into the existing effort. We could use all the help we can get.

Also: I'm pretty new to the data portability spec; so I know that "hostile server" is out of scope, but I wasn't there to know why that choice was made. I'm *guessing* is was too much to tackle at the time.

But one way or another, it would be great to have something in place for this situation, too.

I still need to read your work fully, so I understand what we're talking about :)

@benpate Yes, that’s exactly the gap I’m aiming at: the case where the old server is gone, hostile, or unavailable, and the user needs some way to carry forward verifiable account state without relying on that server’s cooperation.
My reading is that LOLA covers the cooperative portability path well, while this harsher failure case still needs more work. I don’t see PortaFed as a competing standard so much as a possible building block for that scenario.

@PortaFed ~ do you think these ideas would work alongside the existing work being done by the W3C social web community group? https://swicg.github.io/activitypub-data-portability/lola

I *think* you're solving the issue of "my server disappeared, I don't have a backup, and I can't prove I'm still me." Is this close?

Because that's the one use case that the portability spec DOESN'T do. So, maybe there's a way for us to work together, instead of making competing standards.

@julian @evan @jonny @PortaFed

@PortaFed cc @silverpill

Bravo! I like the idea, and honestly I was thinking of making something similar myself. Maybe I’ll implement it into my platform.