<p><ahref="https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/plugins/Pinboard/Pinboard.php#L45">Most endpoints of Pinboard v1 API were implemented</a>. We've left out some such as tag delete (as one can't really delete one in GNU social), among others that don't really fit. We have tested our implementation against <ahref="https://github.com/fibelatti/pinboard-kotlin">Pinkt</a> and we will soon be contacting the maintainer so the functionality of using a different <code>API_TARGET</code> is included with this app (as it was all we had to change to have this working).</p>
<p>Discussion regarding <ahref="https://socialhub.activitypub.rocks/t/explicitly-attached-links/2357/16">how bookmarks are better expressed in terms of ActivityStreams 2.0</a> is also developing in SocialHub.</p>
<p>This was quite a long milestone that builds on top of everything we've been
working on. From the <ahref="https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/components/Notification">Notification</a> and <ahref="https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/components/FreeNetwork">FreeNetwork</a> components to the <ahref="https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/plugins/ActivityPub">ActivityPub</a> plugin.</p>
<p>We have started with
<ahref="https://codeberg.org/GNUsocial/fep/src/branch/fep-8485-bkp/feps/fep-8485.md">FEP-8485 Unbound Actor</a>, aiming at a ValueFlows based relationship between any kind of actors.</p>
<p>And this was discussed, re-thought, re-designed, and went through various
iterations on <ahref="https://socialhub.activitypub.rocks/t/decentralised-group/2200">SocialHub Thread Decentralised Group</a>.</p>
<p>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 <ahref="https://codeberg.org/GNUsocial/fep/src/branch/fep-8485/feps/fep-2100.md">FEP-2100 Unbound Group and Organization</a>.</p>
<p>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.</p>
<p>This FEP was implemented in GS <ahref="https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/plugins/UnboundGroup">via a plugin</a>.</p>
<p>GNU social has <ahref="https://web.archive.org/web/20190320033635/https://chromic.org/blog/lifestream-architecture/">always been a project dear to hackers</a>.</p>
<p>And it's because we love the project history and nature of being easily
extensible and capable of communicating with the most diverse platforms that we
insist on implementing robust and expressive specifications.</p>
<p>Want the notes mentioning you showing up on your toasts, then just code a quick
script and GNU social will definitely not be the one holding you back. We can
think of this <ahref="https://notabug.org/HackersAtPorto/gs-arduino">old GNU social <-> Arduino bridge</a>.</p>
<p>Webhooks is thus one more natural step on this direction.</p>
Milestone: Blog plugin and Notes of type Article and Page
</title><description><![CDATA[
<p>We have implemented group federation, and <ahref="https://github.com/LemmyNet/lemmy/pull/2100/">ensured compatibility with Lemmy (MR #2100)</a>.</p>
<p>This was achieved by strategically introducing the <ahref="https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/plugins/Blog">Blog Plugin</a>.</p>
<p>This milestone elaborates on the <ahref="https://www.gnusocial.rocks/v3/updates-local-groups.html">Local Groups update</a>. We have decided that internally a organisation would be a specialization of the Group Actor. The same way we handle happenings, polls, articles, and pages as specializations of notes.</p>
<p>It is already possible to create organization actors,
<p><ahref="https://webmonetization.org/">Web Monetization</a> is being proposed as a W3C
standard at the Web Platform Incubator Community Group.</p>
<p>GNU social now supports that initiative with the <ahref="https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/plugins/WebMonetization">Web Monetization plugin</a>.</p>
<p>With this, we also introduce an ActivityPub (<ahref="https://codeberg.org/fediverse/fep/pulls/1">FEP-8c3f</a>) GS extension
<code>gs:webmonetizationWallet</code>. This enables actors to support other actors with Web
<p>We have generalized collections around our search engine. For that introducing
the <ahref="https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/components/Collection">Collection component</a>.</p>
<p>This structure has the following implication:</p>
<pre><code>Collection -> OrderedCollection
|-> Notes (known as Feed)
|-> Actors (known as Circle)
|-> Other Object (known as Collection of ...)
|-> Attachments: AttachmentCollection
|-> Tags: TagCollection
</code></pre>
<p>And it allow us to centralise the scope system in the core, ensuring that no
actor will have access to notes or other objects that shouldn't be able to see.</p>
<p>Finally, with this, a plugin such as <ahref="https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/plugins/NoteTypeFeedFilter">Note Type Feed Filter</a> can be useful in
every note collection (feed).</p>
<p>It also allows plugins such as ActivityPub to <ahref="https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/plugins/ActivityPub/Util/OrderedCollectionController.php">translate every collection
<p>We also introduced the <ahref="https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/components/Circle">Circle component</a>, which has a UI similar to the
<p>We haven't implemented federation of Groups yet, but group tags and <ahref="https://socialhub.activitypub.rocks/t/decentralised-group/2200/17?u=diogo">discussion
on how unbounded groups can be federated via ActivityPub</a> has already started.</p>
<p>Concerning federation of traditional groups, we will port our logic from v2 and
translate following the same rules as AndStatus <ahref="https://github.com/andstatus/andstatus/issues/248#issuecomment-558703558">because they work</a>, as yvolk beautifully stated :)</p>