-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathindex.html
2904 lines (2682 loc) · 152 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html><html dir="ltr" lang="en"><head><meta charset="utf-8"><meta name="generator" content="ReSpec 19.0.1"><meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"><style>/* --- EXAMPLES --- */
div.example-title {
min-width: 7.5em;
color: #b9ab2d;
}
div.example-title span {
text-transform: uppercase;
}
aside.example, div.example, div.illegal-example {
padding: 0.5em;
margin: 1em 0;
position: relative;
clear: both;
}
div.illegal-example { color: red }
div.illegal-example p { color: black }
aside.example, div.example {
padding: .5em;
border-left-width: .5em;
border-left-style: solid;
border-color: #e0cb52;
background: #fcfaee;
}
aside.example div.example {
border-left-width: .1em;
border-color: #999;
background: #fff;
}
aside.example div.example div.example-title {
color: #999;
}
</style><style>/* --- ISSUES/NOTES --- */
div.issue-title, div.note-title , div.ednote-title, div.warning-title {
padding-right: 1em;
min-width: 7.5em;
color: #b9ab2d;
}
div.issue-title { color: #e05252; }
div.note-title, div.ednote-title { color: #2b2; }
div.warning-title { color: #f22; }
div.issue-title span, div.note-title span, div.ednote-title span, div.warning-title span {
text-transform: uppercase;
}
div.note, div.issue, div.ednote, div.warning {
margin-top: 1em;
margin-bottom: 1em;
}
.note > p:first-child, .ednote > p:first-child, .issue > p:first-child, .warning > p:first-child { margin-top: 0 }
.issue, .note, .ednote, .warning {
padding: .5em;
border-left-width: .5em;
border-left-style: solid;
}
div.issue, div.note , div.ednote, div.warning {
padding: 1em 1.2em 0.5em;
margin: 1em 0;
position: relative;
clear: both;
}
span.note, span.ednote, span.issue, span.warning { padding: .1em .5em .15em; }
.issue {
border-color: #e05252;
background: #fbe9e9;
}
.note, .ednote {
border-color: #52e052;
background: #e9fbe9;
}
.warning {
border-color: #f11;
border-width: .2em;
border-style: solid;
background: #fbe9e9;
}
.warning-title:before{
content: "⚠"; /*U+26A0 WARNING SIGN*/
font-size: 3em;
float: left;
height: 100%;
padding-right: .3em;
vertical-align: top;
margin-top: -0.5em;
}
li.task-list-item {
list-style: none;
}
input.task-list-item-checkbox {
margin: 0 0.35em 0.25em -1.6em;
vertical-align: middle;
}
</style>
<title>ActivityPub</title>
<style type="text/css">
img {
max-width: 100%;
}
</style>
<style id="respec-mainstyle">/*****************************************************************
* ReSpec 3 CSS
* Robin Berjon - http://berjon.com/
*****************************************************************/
/* Override code highlighter background */
.hljs {
background: transparent !important;
}
/* --- INLINES --- */
h1 abbr,
h2 abbr,
h3 abbr,
h4 abbr,
h5 abbr,
h6 abbr,
a abbr {
border: none;
}
dfn {
font-weight: bold;
}
a.internalDFN {
color: inherit;
border-bottom: 1px solid #99c;
text-decoration: none;
}
a.externalDFN {
color: inherit;
border-bottom: 1px dotted #ccc;
text-decoration: none;
}
a.bibref {
text-decoration: none;
}
cite .bibref {
font-style: normal;
}
code {
color: #c83500;
}
th code {
color: inherit;
}
/* --- TOC --- */
.toc a,
.tof a {
text-decoration: none;
}
a .secno,
a .figno {
color: #000;
}
ul.tof,
ol.tof {
list-style: none outside none;
}
.caption {
margin-top: 0.5em;
font-style: italic;
}
/* --- TABLE --- */
table.simple {
border-spacing: 0;
border-collapse: collapse;
border-bottom: 3px solid #005a9c;
}
.simple th {
background: #005a9c;
color: #fff;
padding: 3px 5px;
text-align: left;
}
.simple th[scope="row"] {
background: inherit;
color: inherit;
border-top: 1px solid #ddd;
}
.simple td {
padding: 3px 10px;
border-top: 1px solid #ddd;
}
.simple tr:nth-child(even) {
background: #f0f6ff;
}
/* --- DL --- */
.section dd > p:first-child {
margin-top: 0;
}
.section dd > p:last-child {
margin-bottom: 0;
}
.section dd {
margin-bottom: 1em;
}
.section dl.attrs dd,
.section dl.eldef dd {
margin-bottom: 0;
}
#issue-summary > ul,
.respec-dfn-list {
column-count: 2;
}
#issue-summary li,
.respec-dfn-list li {
list-style: none;
}
details.respec-tests-details {
margin-left: 1em;
display: inline-block;
vertical-align: top;
}
details.respec-tests-details > * {
padding-right: 2em;
}
details.respec-tests-details[open] {
z-index: 999999;
position: absolute;
border: thin solid #cad3e2;
border-radius: .3em;
background-color: white;
padding-bottom: .5em;
}
details.respec-tests-details[open] > summary {
border-bottom: thin solid #cad3e2;
padding-left: 1em;
margin-bottom: 1em;
line-height: 2em;
}
details.respec-tests-details > ul {
width: 100%;
margin-top: -0.3em;
}
details.respec-tests-details > li {
padding-left: 1em;
}
@media print {
.removeOnSave {
display: none;
}
}
</style><style>/*
github.com style (c) Vasily Polovnyov <vast@whiteants.net>
*/
.hljs {
display: block;
overflow-x: auto;
padding: 0.5em;
color: #333;
background: #f8f8f8;
}
.hljs-comment,
.hljs-quote {
color: #998;
font-style: italic;
}
.hljs-keyword,
.hljs-selector-tag,
.hljs-subst {
color: #333;
font-weight: bold;
}
.hljs-number,
.hljs-literal,
.hljs-variable,
.hljs-template-variable,
.hljs-tag .hljs-attr {
color: #008080;
}
.hljs-string,
.hljs-doctag {
color: #d14;
}
.hljs-title,
.hljs-section,
.hljs-selector-id {
color: #900;
font-weight: bold;
}
.hljs-subst {
font-weight: normal;
}
.hljs-type,
.hljs-class .hljs-title {
color: #458;
font-weight: bold;
}
.hljs-tag,
.hljs-name,
.hljs-attribute {
color: #000080;
font-weight: normal;
}
.hljs-regexp,
.hljs-link {
color: #009926;
}
.hljs-symbol,
.hljs-bullet {
color: #990073;
}
.hljs-built_in,
.hljs-builtin-name {
color: #0086b3;
}
.hljs-meta {
color: #999;
font-weight: bold;
}
.hljs-deletion {
background: #fdd;
}
.hljs-addition {
background: #dfd;
}
.hljs-emphasis {
font-style: italic;
}
.hljs-strong {
font-weight: bold;
}
</style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2016/W3C-REC"><link rel="canonical" href="https://www.w3.org/TR/activitypub/"><script id="initialUserConfig" type="application/json">{
"specStatus": "REC",
"publishDate": "2018-01-23",
"previousPublishDate": "2017-12-05",
"previousMaturity": "PR",
"license": "w3c-software-doc",
"shortName": "activitypub",
"wg": "Social Web Working Group",
"wgURI": "https://www.w3.org/Social/WG",
"wgPublicList": "public-socialweb",
"wgPatentURI": "https://www.w3.org/2004/01/pp-impl/72531/status",
"edDraftURI": "https://w3c.github.io/activitypub/",
"testSuiteURI": "https://test.activitypub.rocks/",
"errata": "https://www.w3.org/wiki/ActivityPub_errata",
"implementationReportURI": "https://activitypub.rocks/implementation-report",
"otherLinks": [
{
"key": "Repository",
"data": [
{
"value": "Git repository",
"href": "https://github.com/w3c/activitypub"
},
{
"value": "Issues",
"href": "https://github.com/w3c/activitypub/issues"
},
{
"value": "Commits",
"href": "https://github.com/w3c/activitypub/commits/gh-pages"
}
]
}
],
"editors": [
{
"name": "Christine Lemmer-Webber",
"url": "https://dustycloud.org/",
"w3cid": "57007"
},
{
"name": "Jessica Tallon",
"url": "https://tsyesika.se",
"w3cid": "72695"
}
],
"authors": [
{
"name": "Christine Lemmer-Webber",
"url": "https://dustycloud.org/"
},
{
"name": "Jessica Tallon",
"url": "https://tsyesika.se"
},
{
"name": "Erin Shepherd",
"url": "http://erinshepherd.net/"
},
{
"name": "Amy Guy",
"url": "https://rhiaro.co.uk/"
},
{
"name": "Evan Prodromou",
"url": "https://en.wikipedia.org/wiki/Evan_Prodromou"
}
],
"localBiblio": {
"ActivityStreams": {
"title": "Activity Streams 2.0",
"href": "https://www.w3.org/TR/activitystreams-core/",
"authors": [
"J. Snell"
],
"status": "Editors Draft",
"publisher": "ActivityStreams Working Group"
},
"Activity-Vocabulary": {
"title": "Activity Vocabulary",
"href": "https://www.w3.org/TR/activitystreams-vocabulary/",
"authors": [
"J. Snell"
],
"status": "Editors Draft",
"publisher": "ActivityStreams Working Group"
},
"OAuth-Server-Metadata": {
"title": "OAuth 2.0 Authorization Server Metadata",
"href": "https://tools.ietf.org/html/draft-ietf-oauth-discovery-06",
"authors": [
"M. Jones",
"N. Sakimura",
"J. Bradley"
],
"status": "Internet-Draft",
"publisher": "OAuth Working Group"
}
},
"publishISODate": "2018-01-23T00:00:00.000Z",
"generatedSubtitle": "Recommendation 23 January 2018"
}</script><meta name="description" content="The ActivityPub protocol is a decentralized social networking protocol
based upon the [ActivityStreams] 2.0 data format.
It provides a client to server API for creating, updating and deleting
content, as well as a federated server to server API for delivering
notifications and content."></head>
<!-- STYLISTIC NOTE: This document wraps on column 79 and at the end of every
sentence. -->
<body aria-busy="false" class="h-entry"><div class="head">
<p>
<a class="logo" href="https://www.w3.org/"><img src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" alt="W3C" width="72" height="48"></a>
</p>
<p><!--_hyper: 682859076;--></p>
<h1 class="title p-name" id="title">ActivityPub</h1>
<h2 id="w3c-recommendation-23-january-2018"><abbr title="World Wide Web Consortium">W3C</abbr> Recommendation <time class="dt-published" datetime="2018-01-23">23 January 2018</time></h2>
<dl>
<dt>This version:</dt>
<dd><a class="u-url" href="https://www.w3.org/TR/2018/REC-activitypub-20180123/">https://www.w3.org/TR/2018/REC-activitypub-20180123/</a></dd>
<dt>Latest published version:</dt>
<dd><a href="https://www.w3.org/TR/activitypub/">https://www.w3.org/TR/activitypub/</a></dd>
<dt>Latest editor's draft:</dt>
<dd><a href="https://w3c.github.io/activitypub/">https://w3c.github.io/activitypub/</a></dd>
<dt>Test suite:</dt>
<dd><a href="https://test.activitypub.rocks/">https://test.activitypub.rocks/</a></dd>
<dt>Implementation report:</dt>
<dd><a href="https://activitypub.rocks/implementation-report">https://activitypub.rocks/implementation-report</a></dd>
<dt>Previous version:</dt>
<dd><a href="https://www.w3.org/TR/2017/PR-activitypub-20171205/">https://www.w3.org/TR/2017/PR-activitypub-20171205/</a></dd>
<dt>Editors:</dt>
<dd class="p-author h-card vcard" data-editor-id="57007"><a class="u-url url p-name fn" href="https://dustycloud.org/">Christine Lemmer-Webber</a></dd>
<dd class="p-author h-card vcard" data-editor-id="72695"><a class="u-url url p-name fn" href="https://tsyesika.se">Jessica Tallon</a></dd>
<dt>Authors:</dt>
<dd class="p-author h-card vcard"><a class="u-url url p-name fn" href="https://dustycloud.org/">Christine Lemmer-Webber</a></dd>
<dd class="p-author h-card vcard"><a class="u-url url p-name fn" href="https://tsyesika.se">Jessica Tallon</a></dd>
<dd class="p-author h-card vcard"><a class="u-url url p-name fn" href="http://erinshepherd.net/">Erin Shepherd</a></dd>
<dd class="p-author h-card vcard"><a class="u-url url p-name fn" href="https://rhiaro.co.uk/">Amy Guy</a></dd>
<dd class="p-author h-card vcard"><a class="u-url url p-name fn" href="https://en.wikipedia.org/wiki/Evan_Prodromou">Evan Prodromou</a></dd>
<dt>Repository:</dt>
<dd>
<a href="https://github.com/w3c/activitypub">
Git repository
</a>
</dd>
<dd>
<a href="https://github.com/w3c/activitypub/issues">
Issues
</a>
</dd>
<dd>
<a href="https://github.com/w3c/activitypub/commits/gh-pages">
Commits
</a>
</dd>
</dl>
<p>
Please check the <a href="https://www.w3.org/wiki/ActivityPub_errata"><strong>errata</strong></a> for any errors or issues
reported since publication.
</p>
<p>
See also <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=activitypub">
<strong>translations</strong></a>.
</p>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2018
<a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="https://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>).
<abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
<a rel="license" href="https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document">permissive document license</a>
rules apply.
</p>
<hr title="Separator for header">
</div>
<section id="abstract" class="introductory"><h2 id="abstract-0">Abstract</h2>
<p>
The ActivityPub protocol is a decentralized social networking protocol
based upon the [<cite><a class="bibref" href="#bib-ActivityStreams">ActivityStreams</a></cite>] 2.0 data format.
It provides a client to server API for creating, updating and deleting
content, as well as a federated server to server API for delivering
notifications and content.
</p>
</section>
<section id="sotd" class="introductory"><h2 id="status-of-this-document">Status of This Document</h2>
<p>
<em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current <abbr title="World Wide Web Consortium">W3C</abbr> publications and the latest revision of this technical report can be found in the <a href="https://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports index</a> at https://www.w3.org/TR/.</em>
</p>
<p>
This document was published by the <a href="https://www.w3.org/Social/WG">Social Web Working Group</a> as a Recommendation.
</p>
<p>
All interested parties are invited to provide implementation and bug
reports and other comments through the Working Group's
<a href="https://github.com/w3c/activitypub/issues">Issue tracker</a>.
These will be discussed by the
<a href="http://www.w3.org/wiki/SocialCG">Social Web Community Group</a>
and considered in any future versions of this specification.
</p>
<p>
Please see the Working Group's <a href="https://activitypub.rocks/implementation-report">implementation
report</a>.
</p>
<p>
This document has been reviewed by <abbr title="World Wide Web Consortium">W3C</abbr> Members, by software developers, and by other <abbr title="World Wide Web Consortium">W3C</abbr>
groups and interested parties, and is endorsed by the Director as a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.
It is a stable document and may be used as reference material or cited from another
document. <abbr title="World Wide Web Consortium">W3C</abbr>'s role in making the Recommendation is to draw attention to the
specification and to promote its widespread deployment. This enhances the functionality
and interoperability of the Web.
</p>
<p>
This document was produced by
a group
operating under the
<a href="https://www.w3.org/Consortium/Patent-Policy/"><abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
<abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="https://www.w3.org/2004/01/pp-impl/72531/status" rel="disclosure">public list of any patent
disclosures</a>
made in connection with the deliverables of
the group; that page also includes
instructions for disclosing a patent. An individual who has actual knowledge of a patent
which the individual believes contains
<a href="https://www.w3.org/Consortium/Patent-Policy/#def-essential">Essential
Claim(s)</a> must disclose the information in accordance with
<a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Disclosure">section
6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
</p>
<p>This document is governed by the <a id="w3c_process_revision" href="https://www.w3.org/2017/Process-20170301/">1 March 2017 <abbr title="World Wide Web Consortium">W3C</abbr> Process Document</a>.
</p>
</section><nav id="toc"><h2 class="introductory" id="table-of-contents">Table of Contents</h2><ol class="toc"><li class="tocline"><a href="#Overview" class="tocxref"><span class="secno">1. </span>Overview</a><ol class="toc"><li class="tocline"><a href="#social-web-working-group" class="tocxref"><span class="secno">1.1 </span>Social Web Working Group</a></li></ol></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">2. </span>Conformance</a><ol class="toc"><li class="tocline"><a href="#specification-profiles" class="tocxref"><span class="secno">2.1 </span>Specification Profiles</a></li></ol></li><li class="tocline"><a href="#obj" class="tocxref"><span class="secno">3. </span>Objects</a><ol class="toc"><li class="tocline"><a href="#obj-id" class="tocxref"><span class="secno">3.1 </span>Object Identifiers</a></li><li class="tocline"><a href="#retrieving-objects" class="tocxref"><span class="secno">3.2 </span>Retrieving objects</a></li><li class="tocline"><a href="#source-property" class="tocxref"><span class="secno">3.3 </span>The source property</a></li></ol></li><li class="tocline"><a href="#actors" class="tocxref"><span class="secno">4. </span>Actors</a><ol class="toc"><li class="tocline"><a href="#actor-objects" class="tocxref"><span class="secno">4.1 </span><i>Actor</i> objects</a></li></ol></li><li class="tocline"><a href="#collections" class="tocxref"><span class="secno">5. </span>Collections</a><ol class="toc"><li class="tocline"><a href="#outbox" class="tocxref"><span class="secno">5.1 </span>Outbox</a></li><li class="tocline"><a href="#inbox" class="tocxref"><span class="secno">5.2 </span>Inbox</a></li><li class="tocline"><a href="#followers" class="tocxref"><span class="secno">5.3 </span>Followers Collection</a></li><li class="tocline"><a href="#following" class="tocxref"><span class="secno">5.4 </span>Following Collection</a></li><li class="tocline"><a href="#liked" class="tocxref"><span class="secno">5.5 </span>Liked Collection</a></li><li class="tocline"><a href="#public-addressing" class="tocxref"><span class="secno">5.6 </span>Public Addressing</a></li><li class="tocline"><a href="#likes" class="tocxref"><span class="secno">5.7 </span>Likes Collection</a></li><li class="tocline"><a href="#shares" class="tocxref"><span class="secno">5.8 </span>Shares Collection</a></li></ol></li><li class="tocline"><a href="#client-to-server-interactions" class="tocxref"><span class="secno">6. </span>Client to Server Interactions</a><ol class="toc"><li class="tocline"><a href="#client-addressing" class="tocxref"><span class="secno">6.1 </span>Client Addressing</a></li><li class="tocline"><a href="#create-activity-outbox" class="tocxref"><span class="secno">6.2 </span>Create Activity</a><ol class="toc"><li class="tocline"><a href="#object-without-create" class="tocxref"><span class="secno">6.2.1 </span>Object creation without a Create Activity</a></li></ol></li><li class="tocline"><a href="#update-activity-outbox" class="tocxref"><span class="secno">6.3 </span>Update Activity</a><ol class="toc"><li class="tocline"><a href="#partial-updates" class="tocxref"><span class="secno">6.3.1 </span>Partial Updates</a></li></ol></li><li class="tocline"><a href="#delete-activity-outbox" class="tocxref"><span class="secno">6.4 </span>Delete Activity</a></li><li class="tocline"><a href="#follow-activity-outbox" class="tocxref"><span class="secno">6.5 </span>Follow Activity</a></li><li class="tocline"><a href="#add-activity-outbox" class="tocxref"><span class="secno">6.6 </span>Add Activity</a></li><li class="tocline"><a href="#remove-activity-outbox" class="tocxref"><span class="secno">6.7 </span>Remove Activity</a></li><li class="tocline"><a href="#like-activity-outbox" class="tocxref"><span class="secno">6.8 </span>Like Activity</a></li><li class="tocline"><a href="#block-activity-outbox" class="tocxref"><span class="secno">6.9 </span>Block Activity</a></li><li class="tocline"><a href="#undo-activity-outbox" class="tocxref"><span class="secno">6.10 </span>Undo Activity</a></li><li class="tocline"><a href="#client-to-server-outbox-delivery" class="tocxref"><span class="secno">6.11 </span>Delivery</a></li><li class="tocline"><a href="#uploading-media" class="tocxref"><span class="secno">6.12 </span>Uploading Media</a></li></ol></li><li class="tocline"><a href="#server-to-server-interactions" class="tocxref"><span class="secno">7. </span>Server to Server Interactions</a><ol class="toc"><li class="tocline"><a href="#delivery" class="tocxref"><span class="secno">7.1 </span>Delivery</a><ol class="toc"><li class="tocline"><a href="#outbox-delivery" class="tocxref"><span class="secno">7.1.1 </span>Outbox Delivery Requirements for Server to Server</a></li><li class="tocline"><a href="#inbox-forwarding" class="tocxref"><span class="secno">7.1.2 </span>Forwarding from Inbox</a></li><li class="tocline"><a href="#shared-inbox-delivery" class="tocxref"><span class="secno">7.1.3 </span>Shared Inbox Delivery</a></li></ol></li><li class="tocline"><a href="#create-activity-inbox" class="tocxref"><span class="secno">7.2 </span>Create Activity</a></li><li class="tocline"><a href="#update-activity-inbox" class="tocxref"><span class="secno">7.3 </span>Update Activity</a></li><li class="tocline"><a href="#delete-activity-inbox" class="tocxref"><span class="secno">7.4 </span>Delete Activity</a></li><li class="tocline"><a href="#follow-activity-inbox" class="tocxref"><span class="secno">7.5 </span>Follow Activity</a></li><li class="tocline"><a href="#accept-activity-inbox" class="tocxref"><span class="secno">7.6 </span>Accept Activity</a></li><li class="tocline"><a href="#reject-activity-inbox" class="tocxref"><span class="secno">7.7 </span>Reject Activity</a></li><li class="tocline"><a href="#add-activity-inbox" class="tocxref"><span class="secno">7.8 </span>Add Activity</a></li><li class="tocline"><a href="#remove-activity-inbox" class="tocxref"><span class="secno">7.9 </span>Remove Activity</a></li><li class="tocline"><a href="#like-activity-inbox" class="tocxref"><span class="secno">7.10 </span>Like Activity</a></li><li class="tocline"><a href="#announce-activity-inbox" class="tocxref"><span class="secno">7.11 </span>Announce Activity (sharing)</a></li><li class="tocline"><a href="#undo-activity-inbox" class="tocxref"><span class="secno">7.12 </span>Undo Activity</a></li></ol></li><li class="tocline"><a href="#i18n-concerns" class="tocxref"><span class="secno">A. </span>Internationalization</a></li><li class="tocline"><a href="#security-considerations" class="tocxref"><span class="secno">B. </span>Security Considerations</a><ol class="toc"><li class="tocline"><a href="#authorization" class="tocxref"><span class="secno">B.1 </span>Authentication and Authorization</a></li><li class="tocline"><a href="#security-verification" class="tocxref"><span class="secno">B.2 </span>Verification</a></li><li class="tocline"><a href="#security-localhost" class="tocxref"><span class="secno">B.3 </span>Accessing localhost URIs</a></li><li class="tocline"><a href="#security-uri-schemes" class="tocxref"><span class="secno">B.4 </span>URI Schemes</a></li><li class="tocline"><a href="#security-recursive-objects" class="tocxref"><span class="secno">B.5 </span>Recursive Objects</a></li><li class="tocline"><a href="#security-spam" class="tocxref"><span class="secno">B.6 </span>Spam</a></li><li class="tocline"><a href="#security-federation-dos" class="tocxref"><span class="secno">B.7 </span>Federation denial-of-service</a></li><li class="tocline"><a href="#security-c2s-ratelimiting" class="tocxref"><span class="secno">B.8 </span>Client-to-server ratelimiting</a></li><li class="tocline"><a href="#security-c2s-response-dos" class="tocxref"><span class="secno">B.9 </span>Client-to-server response denial-of-service</a></li><li class="tocline"><a href="#security-sanitizing-content" class="tocxref"><span class="secno">B.10 </span>Sanitizing Content</a></li><li class="tocline"><a href="#security-not-displaying-bto-bcc" class="tocxref"><span class="secno">B.11 </span>Not displaying bto and bcc properties</a></li></ol></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">C. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ol class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a></li></ol></li></ol></nav>
<section id="Overview">
<!--OddPage--><h2 id="x1-overview"><span class="secno">1. </span>Overview</h2>
<p>ActivityPub provides two layers:</p>
<ul>
<li>
<b>A server to server federation protocol</b>
(so decentralized websites can share information)
</li>
<li>
<b>A client to server protocol</b>
(so users, including real-world users, bots, and other automated processes,
can communicate with ActivityPub using their accounts on servers,
from a phone or desktop or web application or whatever)
</li>
</ul>
<p>
ActivityPub implementations can implement just one of these things or
both of them.
However, once you've implemented one, it isn't too many steps to
implement the other, and there are a lot of benefits to both (making
your website part of the decentralized social web, and being able to
use clients and client libraries that work across a wide variety of
social websites).
</p>
<p>
In ActivityPub, a user is represented by "<a href="#actors">actors</a>"
via the user's accounts on servers.
User's accounts on different servers correspond to different actors.
Every Actor has:
</p>
<ul>
<li><b>An <code>inbox</code>:</b> How they get messages from the world</li>
<li><b>An <code>outbox</code>:</b> How they send messages to others</li>
</ul>
<p>
<img src="illustration/tutorial-1.png" alt="Actor with inbox and outbox">
</p>
<p>
These are endpoints, or really, just URLs which are listed in the
ActivityPub actor's ActivityStreams description.
(More on ActivityStreams later).
</p>
<p>
Here's an example of the record of our friend Alyssa P. Hacker:
</p>
<div class="example"><div class="example-title marker"><span>Example 1</span></div><pre class="highlight json hljs" aria-busy="false" aria-live="polite">{<span class="hljs-attr">"@context"</span>: <span class="hljs-string">"https://www.w3.org/ns/activitystreams"</span>,
<span class="hljs-attr">"type"</span>: <span class="hljs-string">"Person"</span>,
<span class="hljs-attr">"id"</span>: <span class="hljs-string">"https://social.example/alyssa/"</span>,
<span class="hljs-attr">"name"</span>: <span class="hljs-string">"Alyssa P. Hacker"</span>,
<span class="hljs-attr">"preferredUsername"</span>: <span class="hljs-string">"alyssa"</span>,
<span class="hljs-attr">"summary"</span>: <span class="hljs-string">"Lisp enthusiast hailing from MIT"</span>,
<span class="hljs-attr">"inbox"</span>: <span class="hljs-string">"https://social.example/alyssa/inbox/"</span>,
<span class="hljs-attr">"outbox"</span>: <span class="hljs-string">"https://social.example/alyssa/outbox/"</span>,
<span class="hljs-attr">"followers"</span>: <span class="hljs-string">"https://social.example/alyssa/followers/"</span>,
<span class="hljs-attr">"following"</span>: <span class="hljs-string">"https://social.example/alyssa/following/"</span>,
<span class="hljs-attr">"liked"</span>: <span class="hljs-string">"https://social.example/alyssa/liked/"</span>}</pre></div>
<p>
ActivityPub uses [<cite><a class="bibref" href="#bib-ActivityStreams">ActivityStreams</a></cite>] for its vocabulary.
This is pretty great because ActivityStreams includes all the common
terms you need to represent all the activities and content flowing
around a social network.
It's likely that ActivityStreams already includes all the vocabulary
you need, but even if it doesn't, ActivityStreams can be extended
via [<cite><a class="bibref" href="#bib-JSON-LD">JSON-LD</a></cite>].
If you know what JSON-LD is, you can take advantage of the cool linked
data approaches provided by JSON-LD.
If you don't, don't worry, JSON-LD documents and ActivityStreams can be
understood as plain old simple JSON.
(If you're going to add extensions, that's the point at which JSON-LD
really helps you out).
</p>
<p>
So, okay.
Alyssa wants to talk to her friends, and her friends want to talk to
her!
Luckily these "inbox" and "outbox" things can help us out.
They both behave differently for GET and POST.
Let's see how that works:
</p>
<p>
<img src="illustration/tutorial-2.png" alt="Actor with messages flowing from rest of world to inbox and from outbox to rest of world">
</p>
<p>
Hey nice, so just as a recap:
</p>
<ul>
<li>
You can POST to someone's inbox to send them a message
(server-to-server / federation only... this <em>is</em> federation!)
</li>
<li>
You can GET from your inbox to read your latest messages
(client-to-server; this is like reading your social
network stream)
</li>
<li>
You can POST to your outbox to send messages to the world
(client-to-server)
</li>
<li>
You can GET from someone's outbox to see what messages they've
posted (or at least the ones you're authorized to see).
(client-to-server and/or server-to-server)
</li>
</ul>
<p>
Of course, if that last one (GET'ing from someone's outbox) was the
only way to see what people have sent, this wouldn't be a very
efficient federation protocol!
Indeed, federation happens usually by servers posting messages sent by
actors to actors on other servers' inboxes.
</p>
<p>
Let's see an example!
Let's say Alyssa wants to catch up with her friend, Ben Bitdiddle.
She lent him a book recently and she wants to make sure he returns it
to her.
Here's the message she composes, as an ActivityStreams object:
</p>
<div class="example"><div class="example-title marker"><span>Example 2</span></div><pre class="highlight json hljs" aria-busy="false" aria-live="polite">{<span class="hljs-attr">"@context"</span>: <span class="hljs-string">"https://www.w3.org/ns/activitystreams"</span>,
<span class="hljs-attr">"type"</span>: <span class="hljs-string">"Note"</span>,
<span class="hljs-attr">"to"</span>: [<span class="hljs-string">"https://chatty.example/ben/"</span>],
<span class="hljs-attr">"attributedTo"</span>: <span class="hljs-string">"https://social.example/alyssa/"</span>,
<span class="hljs-attr">"content"</span>: <span class="hljs-string">"Say, did you finish reading that book I lent you?"</span>}</pre></div>
<p>
This is a note addressed to Ben.
She POSTs it to her outbox.
</p>
<p>
<img src="illustration/tutorial-3.png" alt="Actor posting message to outbox">
</p>
<p>
Since this is a non-activity object, the server recognizes that this is
an object being newly created, and does the courtesy of wrapping it in
a Create activity.
(Activities sent around in ActivityPub generally follow the pattern of
some activity by some actor being taken on some object.
In this case the activity is a Create of a Note object, posted by a
Person).
</p>
<div class="example"><div class="example-title marker"><span>Example 3</span></div><pre class="highlight json hljs" aria-busy="false" aria-live="polite">{<span class="hljs-attr">"@context"</span>: <span class="hljs-string">"https://www.w3.org/ns/activitystreams"</span>,
<span class="hljs-attr">"type"</span>: <span class="hljs-string">"Create"</span>,
<span class="hljs-attr">"id"</span>: <span class="hljs-string">"https://social.example/alyssa/posts/a29a6843-9feb-4c74-a7f7-081b9c9201d3"</span>,
<span class="hljs-attr">"to"</span>: [<span class="hljs-string">"https://chatty.example/ben/"</span>],
<span class="hljs-attr">"actor"</span>: <span class="hljs-string">"https://social.example/alyssa/"</span>,
<span class="hljs-attr">"object"</span>: {<span class="hljs-attr">"type"</span>: <span class="hljs-string">"Note"</span>,
<span class="hljs-attr">"id"</span>: <span class="hljs-string">"https://social.example/alyssa/posts/49e2d03d-b53a-4c4c-a95c-94a6abf45a19"</span>,
<span class="hljs-attr">"attributedTo"</span>: <span class="hljs-string">"https://social.example/alyssa/"</span>,
<span class="hljs-attr">"to"</span>: [<span class="hljs-string">"https://chatty.example/ben/"</span>],
<span class="hljs-attr">"content"</span>: <span class="hljs-string">"Say, did you finish reading that book I lent you?"</span>}}</pre></div>
<p>
Alyssa's server looks up Ben's ActivityStreams actor object, finds his
inbox endpoint, and POSTs her object to his inbox.
</p>
<p>
<img src="illustration/tutorial-4.png" alt="Server posting to remote actor's inbox">
</p>
<p>
Technically these are two separate steps... one is client to server
communication, and one is server to server communication (federation).
But, since we're using them both in this example, we can abstractly
think of this as being a streamlined submission from outbox to inbox:
</p>
<p>
<img src="illustration/tutorial-5.png" alt="Note flowing from one actor's outbox to other actor's inbox">
</p>
<p>
Cool!
A while later, Alyssa checks what new messages she's gotten.
Her phone polls her inbox via GET, and amongst a bunch of cat videos
posted by friends and photos of her nephew posted by her sister, she
sees the following:
</p>
<div class="example"><div class="example-title marker"><span>Example 4</span></div><pre class="highlight json hljs" aria-busy="false" aria-live="polite">{"@context": "https://www.w3.org/ns/activitystreams",
"type": "Create",
"id": "https://chatty.example/ben/p/51086",
"to": ["https://social.example/alyssa/"],
"actor": "https://chatty.example/ben/",
"object": {"type": "Note",
"id": "https://chatty.example/ben/p/51085",
"attributedTo": "https://chatty.example/ben/",
"to": ["https://social.example/alyssa/"],
"inReplyTo": "https://social.example/alyssa/posts/49e2d03d-b53a-4c4c-a95c-94a6abf45a19",
"content": "<p>Argh, yeah, sorry, I'll get it back to you tomorrow.</p>
<p>I was reviewing the section on register machines,
since it's been a while since I wrote one.</p>"}}</pre></div>
<p>Alyssa is relieved, and likes Ben's post:</p>
<div class="example"><div class="example-title marker"><span>Example 5</span></div><pre class="highlight json hljs" aria-busy="false" aria-live="polite">{<span class="hljs-attr">"@context"</span>: <span class="hljs-string">"https://www.w3.org/ns/activitystreams"</span>,
<span class="hljs-attr">"type"</span>: <span class="hljs-string">"Like"</span>,
<span class="hljs-attr">"id"</span>: <span class="hljs-string">"https://social.example/alyssa/posts/5312e10e-5110-42e5-a09b-934882b3ecec"</span>,
<span class="hljs-attr">"to"</span>: [<span class="hljs-string">"https://chatty.example/ben/"</span>],
<span class="hljs-attr">"actor"</span>: <span class="hljs-string">"https://social.example/alyssa/"</span>,
<span class="hljs-attr">"object"</span>: <span class="hljs-string">"https://chatty.example/ben/p/51086"</span>}</pre></div>
<p>
She POSTs this message to her outbox.
(Since it's an activity, her server knows it doesn't need to wrap it in
a Create object).
</p>
<p>
Feeling happy about things, she decides to post a public message to her
followers.
Soon the following message is blasted to all the members of her
followers collection, and since it has the special Public group
addressed, is generally readable by anyone.
</p>
<div class="example"><div class="example-title marker"><span>Example 6</span></div><pre class="highlight json hljs" aria-busy="false" aria-live="polite">{<span class="hljs-attr">"@context"</span>: <span class="hljs-string">"https://www.w3.org/ns/activitystreams"</span>,
<span class="hljs-attr">"type"</span>: <span class="hljs-string">"Create"</span>,
<span class="hljs-attr">"id"</span>: <span class="hljs-string">"https://social.example/alyssa/posts/9282e9cc-14d0-42b3-a758-d6aeca6c876b"</span>,
<span class="hljs-attr">"to"</span>: [<span class="hljs-string">"https://social.example/alyssa/followers/"</span>,
<span class="hljs-string">"https://www.w3.org/ns/activitystreams#Public"</span>],
<span class="hljs-attr">"actor"</span>: <span class="hljs-string">"https://social.example/alyssa/"</span>,
<span class="hljs-attr">"object"</span>: {<span class="hljs-attr">"type"</span>: <span class="hljs-string">"Note"</span>,
<span class="hljs-attr">"id"</span>: <span class="hljs-string">"https://social.example/alyssa/posts/d18c55d4-8a63-4181-9745-4e6cf7938fa1"</span>,
<span class="hljs-attr">"attributedTo"</span>: <span class="hljs-string">"https://social.example/alyssa/"</span>,
<span class="hljs-attr">"to"</span>: [<span class="hljs-string">"https://social.example/alyssa/followers/"</span>,
<span class="hljs-string">"https://www.w3.org/ns/activitystreams#Public"</span>],
<span class="hljs-attr">"content"</span>: <span class="hljs-string">"Lending books to friends is nice. Getting them back is even nicer! :)"</span>}}</pre></div>
<section id="social-web-working-group" inlist="" rel="schema:hasPart" resource="#social-web-working-group">
<h3 property="schema:name" id="x1-1-social-web-working-group"><span class="secno">1.1 </span>Social Web Working Group</h3>
<div datatype="rdf:HTML" property="schema:description">
<p>
<a href="#Overview">ActivityPub</a> is one of several related
specifications being produced by the Social Web Working Group.
Implementers interested in alternative approaches and complementary
protocols should review [<cite><a class="bibref" href="#bib-Micropub">Micropub</a></cite>] and the overview document
[<cite><a class="bibref" href="#bib-Social-Web-Protocols">Social-Web-Protocols</a></cite>].
</p>
</div>
</section>
</section>
<section id="conformance"><!--OddPage--><h2 id="x2-conformance"><span class="secno">2. </span>Conformance</h2>
<p>
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples,
and notes in this specification are non-normative. Everything else in this specification is
normative.
</p>
<p id="respecRFC2119">The key words <em class="rfc2119">MAY</em>, <em class="rfc2119">MUST</em>, <em class="rfc2119">MUST NOT</em>, <em class="rfc2119">SHOULD</em>, and <em class="rfc2119">SHOULD NOT</em> are
to be interpreted as described in [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].
</p>
<section id="specification-profiles">
<h3 id="x2-1-specification-profiles"><span class="secno">2.1 </span>Specification Profiles</h3>
<p>
This specification defines two closely related and interacting
protocols:
</p>
<dl>
<dt>A client to server protocol, or "Social API"</dt>
<dd>
This protocol permits a client to act <i>on behalf</i> of a user.
For example, this protocol is used by a mobile phone application to
interact with a social stream of the user's actor.
</dd>
<dt>A server to server protocol, or "Federation Protocol"</dt>
<dd>
This protocol is used to distribute activities between actors on
different servers, tying them into the same social graph.
</dd>
</dl>
<p>
The ActivityPub specification is designed so that once either of
these protocols are implemented, supporting the other is of very
little additional effort.
However, servers may still implement one without the other.
This gives three conformance classes:
</p>
<dl>
<dt>ActivityPub conformant Client</dt>
<dd>
This designation applies to any implementation of the entirety of the
client portion of the client to server protocol.
</dd>
<dt>ActivityPub conformant Server</dt>
<dd>
This designation applies to any implementation of the entirety of the
server portion of the client to server protocol.
</dd>
<dt>ActivityPub conformant Federated Server</dt>
<dd>
This designation applies to any implementation of the entirety of
the federation protocols.
</dd>
</dl>
<p>
It is called out whenever a portion of the specification only applies
to implementation of the federation protocol.
In addition, whenever requirements are specified, it is called out
whether they apply to the client or server (for the client-to-server
protocol) or whether referring to a sending or receiving server in
the server-to-server protocol.
</p>
</section>
</section>
<section id="obj">
<!--OddPage--><h2 id="x3-objects"><span class="secno">3. </span>Objects</h2>
<p>
Objects are the core concept around which both [<cite><a class="bibref" href="#bib-ActivityStreams">ActivityStreams</a></cite>] and
ActivityPub are built.
Objects are often wrapped in Activities and are contained in streams of
Collections, which are themselves subclasses of Objects.
See the [<cite><a class="bibref" href="#bib-Activity-Vocabulary">Activity-Vocabulary</a></cite>] document, particularly the
<a href="https://www.w3.org/TR/activitystreams-vocabulary/#types">Core Classes</a>;
ActivityPub follows the mapping of this vocabulary very closely.
</p>
<p>
ActivityPub defines some terms in addition to those provided by
ActivityStreams.
These terms are provided in the ActivityPub
<a href="http://www.w3.org/TR/json-ld/#the-context">JSON-LD context</a>
at
<code>https://www.w3.org/ns/activitystreams</code>.
Implementers <em class="rfc2119" title="SHOULD">SHOULD</em> include the ActivityPub context in their
object definitions.
Implementers <em class="rfc2119" title="MAY">MAY</em> include additional context as appropriate.
</p>
<p>
ActivityPub shares the same
<a href="https://www.w3.org/TR/activitystreams-core/#urls">
URI / IRI conventions as in ActivityStreams</a>.
</p>
<p>
Servers <em class="rfc2119" title="SHOULD">SHOULD</em> validate the content they receive to avoid content
spoofing attacks.
(A server should do something at least as robust as checking that
the object appears as received at its origin, but mechanisms
such as checking signatures would be better if available).
No particular mechanism for verification is authoritatively specified by
this document, but please see <a href="#security-considerations">Security
Considerations</a> for some suggestions and good practices.
</p>
<div class="informative">
As an example, if example.com receives the activity
<div class="example"><div class="example-title marker"><span>Example 7</span></div><pre class="hljs json" aria-busy="false" aria-live="polite">{
<span class="hljs-attr">"@context"</span>: <span class="hljs-string">"https://www.w3.org/ns/activitystreams"</span>,
<span class="hljs-attr">"type"</span>: <span class="hljs-string">"Like"</span>,
<span class="hljs-attr">"actor"</span>: <span class="hljs-string">"https://example.net/~mallory"</span>,
<span class="hljs-attr">"to"</span>: [<span class="hljs-string">"https://hatchat.example/sarah/"</span>,
<span class="hljs-string">"https://example.com/peeps/john/"</span>],
<span class="hljs-attr">"object"</span>: {
<span class="hljs-attr">"@context"</span>: {<span class="hljs-attr">"@language"</span>: <span class="hljs-string">"en"</span>},
<span class="hljs-attr">"id"</span>: <span class="hljs-string">"https://example.org/~alice/note/23"</span>,
<span class="hljs-attr">"type"</span>: <span class="hljs-string">"Note"</span>,
<span class="hljs-attr">"attributedTo"</span>: <span class="hljs-string">"https://example.org/~alice"</span>,
<span class="hljs-attr">"content"</span>: <span class="hljs-string">"I'm a goat"</span>
}