diff --git a/v3/assets/unbound/example_linked_note.png b/v3/assets/unbound/example_linked_note.png
new file mode 100644
index 0000000..b55bbba
Binary files /dev/null and b/v3/assets/unbound/example_linked_note.png differ
diff --git a/v3/assets/unbound/settings_link.png b/v3/assets/unbound/settings_link.png
new file mode 100644
index 0000000..1f83d0d
Binary files /dev/null and b/v3/assets/unbound/settings_link.png differ
diff --git a/v3/feed.rss b/v3/feed.rss
index 083f41c..f3903d0 100644
--- a/v3/feed.rss
+++ b/v3/feed.rss
@@ -2,10 +2,44 @@
We have started with +FEP-8485 Unbound Actor, aiming at a ValueFlows based relationship between any kind of actors.
+ +And this was discussed, re-thought, re-designed, and went through various +iterations on SocialHub Thread Decentralised Group.
+ +It wasn't until we had finished implementing the federation of Groups, +polishing our Notification system, and defined how we wanted to represent all of +this internally for GNU social v3, that we fresh started with all these ideas in +mind and came with the simpler FEP-2100 Unbound Group and Organization.
+ +Which instead builds on top of the already existing logic for Following. Of +course, this FEP assumes how GNU social (and Lemmy, Friendrica, and Lotide) +understands groups (and organisations). But we believe that, now that +implementations are using these ideas and strategies, after a few more testing +time, everything should become reasonably specified and formalized. Being this +FEP already a step and contribution in that direction.
+ ++
+ + + +]]>https://gnusocial.rocks/v3/milestone-unbound-group.html +-
- - - - - - - - - - - - - - - - - - - - - - - - - - -]]>@#circle_name
.
+
diff --git a/v3/milestone-documentation-and-tests-infrastructure.html b/v3/milestone-documentation-and-tests-infrastructure.html
index 643cd53..03a11c4 100644
--- a/v3/milestone-documentation-and-tests-infrastructure.html
+++ b/v3/milestone-documentation-and-tests-infrastructure.html
@@ -134,6 +134,7 @@ is properly tested, we have the
+
diff --git a/v3/milestone-mute-notifications-from-a-conversation.html b/v3/milestone-mute-notifications-from-a-conversation.html
index cdd64ec..915ab6b 100644
--- a/v3/milestone-mute-notifications-from-a-conversation.html
+++ b/v3/milestone-mute-notifications-from-a-conversation.html
@@ -70,6 +70,7 @@ to stop receiving notifications derived from that, it is now possible:
+
diff --git a/v3/milestone-notes-and-actors-with-languages.html b/v3/milestone-notes-and-actors-with-languages.html
index 53b7c37..811639e 100644
--- a/v3/milestone-notes-and-actors-with-languages.html
+++ b/v3/milestone-notes-and-actors-with-languages.html
@@ -112,6 +112,7 @@ for actual internationalization of the free network.
+
diff --git a/v3/milestone-notes-with-latex.html b/v3/milestone-notes-with-latex.html
index 5e69f0a..d1f98f5 100644
--- a/v3/milestone-notes-with-latex.html
+++ b/v3/milestone-notes-with-latex.html
@@ -70,6 +70,7 @@ GNU social development team
+
diff --git a/v3/milestone-notes-with-markdown.html b/v3/milestone-notes-with-markdown.html
index 73cc664..a692a35 100644
--- a/v3/milestone-notes-with-markdown.html
+++ b/v3/milestone-notes-with-markdown.html
@@ -71,6 +71,7 @@ GNU social development team
+
diff --git a/v3/milestone-oauth-20.html b/v3/milestone-oauth-20.html
index 3d7623c..11110e9 100644
--- a/v3/milestone-oauth-20.html
+++ b/v3/milestone-oauth-20.html
@@ -56,6 +56,7 @@ discussion available at:
+
+
+
+
+
+
+
+
+This was quite a long milestone that builds on top of everything we've been +working on. From the Notification and FreeNetwork components to the ActivityPub plugin.
+ +We have started with +FEP-8485 Unbound Actor, aiming at a ValueFlows based relationship between any kind of actors.
+ +And this was discussed, re-thought, re-designed, and went through various +iterations on SocialHub Thread Decentralised Group.
+ +It wasn't until we had finished implementing the federation of Groups, +polishing our Notification system, and defined how we wanted to represent all of +this internally for GNU social v3, that we fresh started with all these ideas in +mind and came with the simpler FEP-2100 Unbound Group and Organization.
+ +Which instead builds on top of the already existing logic for Following. Of +course, this FEP assumes how GNU social (and Lemmy, Friendrica, and Lotide) +understands groups (and organisations). But we believe that, now that +implementations are using these ideas and strategies, after a few more testing +time, everything should become reasonably specified and formalized. Being this +FEP already a step and contribution in that direction.
+ ++
+ + + + +