Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://xoxo.zone/users/KevinMarks/statuses/111597703976685489">Kevin Marks (kevinmarks@xoxo.zone)'s status on Monday, 18-Dec-2023 05:49:24 JST</a><a href="https://xoxo.zone/@KevinMarks" title="kevinmarks@xoxo.zone"><img src="https://gnusocial.jp/avatar/25142-48-20221112232850.webp" width="48" height="48" alt="Kevin Marks" style="position: absolute; left: 0; top: 0;">Kevin Marks</a><div><a href="https://cosocial.ca/@evan/111597605191170992" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/75487" title="luis_in_brief@social.coop">Luis Villa</a></li><li><a href="https://gnusocial.jp/user/77066" title="evan@cosocial.ca">Evan Prodromou</a></li></ul></div></section><article><p><a href="https://cosocial.ca/@evan">@evan</a> <a href="https://social.coop/@luis_in_brief">@luis_in_brief</a> <a href="https://fedi.simonwillison.net/@simon">@simon</a> previously <a href="https://github.com/mastodon/mastodon/issues/177#issuecomment-292780728" rel="nofollow noreferrer">https://github.com/mastodon/mastodon/issues/177#issuecomment-292780728</a></p><p>We had a mechanism for this in OStatus that worked by delegating to the http and dns stacks. AP half bought into the dns is bad, keys are good worldview so to migrate you need a separate protocol to do a key handover and follower migration to the new instance. However historic posts are stuck on the old instance because it can't 301 them to the new one because signing posts is bound to the user, not the domain.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2463596#notice-4879999">In conversation</a><time datetime="2023-12-18T05:49:24+09:00" title="Monday, 18-Dec-2023 05:49:24 JST">Monday, 18-Dec-2023 05:49:24 JST</time> <span>from <span><a href="https://xoxo.zone/@KevinMarks/111597703976685489" rel="external" title="Sent from xoxo.zone via ActivityPub">xoxo.zone</a></span></span><a href="https://xoxo.zone/@KevinMarks/111597703976685489">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: opengraph.githubassets.com</div><h5><a href="https://github.com/mastodon/mastodon/issues/177#issuecomment-292780728We">Support account migration · Issue #177 · mastodon/mastodon</a></h5><div></div></header><div>A lot of people seem to be jumping on https://mastodon.social right now, even though the end goal is to have users separated out across multiple federated instances. However, if people start puttin...</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Kevin Marks (kevinmarks@xoxo.zone)'s status on Monday, 18-Dec-2023 05:49:24 JSTKevin Marks
in reply to
@evan @luis_in_brief @simon previously https://github.com/mastodon/mastodon/issues/177#issuecomment-292780728
We had a mechanism for this in OStatus that worked by delegating to the http and dns stacks. AP half bought into the dns is bad, keys are good worldview so to migrate you need a separate protocol to do a key handover and follower migration to the new instance. However historic posts are stuck on the old instance because it can't 301 them to the new one because signing posts is bound to the user, not the domain.
In conversationabout a year ago from xoxo.zonepermalink
Attachments
1. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
  Support account migration · Issue #177 · mastodon/mastodon
  A lot of people seem to be jumping on https://mastodon.social right now, even though the end goal is to have users separated out across multiple federated instances. However, if people start puttin...

Public

Embed Notice

HTML Code

Corresponding Notice