Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mitra.social/objects/018be58f-eb4b-a8f7-b03c-5dc2fce0788a">silverpill (silverpill@mitra.social)'s status on Sunday, 19-Nov-2023 12:12:57 JST</a><a href="https://mitra.social/users/silverpill" title="silverpill@mitra.social"><img src="https://gnusocial.jp/avatar/85321-48-20230105202807.webp" width="48" height="48" alt="silverpill" style="position: absolute; left: 0; top: 0;">silverpill</a><div><a href="https://mitra.social/objects/018be460-1b63-02a2-01a8-494545bb1c7a" rel="in-reply-to">in reply to</a><ul><li></ul></div></section><article><p><a href="https://were.social/users/arcanicanis">@arcanicanis</a></p><p>&gt;I think a separate property could be used instead, despite it adding more cruft</p><p>With a separate property it will be difficult to create links. Take for example inReplyTo property, if you use a separate property the reply will look like this:</p>{
  "type": "Note",
  "id": "https://alice.example/objects/123",
  "didUrl": "did🔑xyz/objects/123",
  "content": "This note has two IDs",
  "inReplyTo": {
    "id": "https://bob.example/objects/567",
    "didUrl": "did🔑ijk/objects/567"
  },
  ...
}
<p>Mastodon probably won't accept such inReplyTo value, so you'll get a separate fediverse either way. I think single ID approach is cleaner</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2347472#notice-4636688">In conversation</a><time datetime="2023-11-19T12:12:57+09:00" title="Sunday, 19-Nov-2023 12:12:57 JST">Sunday, 19-Nov-2023 12:12:57 JST</time> <span>from <span><a href="https://mitra.social/objects/018be58f-eb4b-a8f7-b03c-5dc2fce0788a" rel="external" title="Sent from mitra.social via ActivityPub">mitra.social</a></span></span><a href="https://mitra.social/objects/018be58f-eb4b-a8f7-b03c-5dc2fce0788a">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/1851556">Untitled attachment</a></label><br></li><li><label><a rel="external" href="https://gnusocial.jp/attachment/1851557">Untitled attachment</a></label><br></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
silverpill (silverpill@mitra.social)'s status on Sunday, 19-Nov-2023 12:12:57 JSTsilverpill
in reply to
- arcanicanis
@arcanicanis
>I think a separate property could be used instead, despite it adding more cruft
With a separate property it will be difficult to create links. Take for example inReplyTo property, if you use a separate property the reply will look like this:
{ "type": "Note", "id": "https://alice.example/objects/123", "didUrl": "did🔑xyz/objects/123", "content": "This note has two IDs", "inReplyTo": { "id": "https://bob.example/objects/567", "didUrl": "did🔑ijk/objects/567" }, ... }
Mastodon probably won't accept such inReplyTo value, so you'll get a separate fediverse either way. I think single ID approach is cleaner
In conversationSunday, 19-Nov-2023 12:12:57 JST from mitra.socialpermalink
Attachments
1. Untitled attachment
2. Untitled attachment

Public

Embed Notice

HTML Code

Corresponding Notice