GNUsocial
/
gnusocial.rocks
4
0
Fork 1
Code Issues Pull Requests Releases Activity

improve text of post 4

This commit is contained in:
Diogo Peralta Cordeiro 2021-08-19 03:20:52 +01:00
parent 69d0d5d6e0
commit f9f64f242c
Signed by: diogo
GPG Key ID: 18D2D35001FBFAB0
8 changed files with 83 additions and 147 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

105
v3/feed.rss
View File

@ -2,8 +2,8 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel><title>GNU social V3</title><link>https://gnusocial.rocks/v3/index.html</link>
<description>Development blog where we announce our progress.</description><language>en</language>
<lastBuildDate>Thu, 19 Aug 2021 03:15:08 +0100</lastBuildDate>
<pubDate>Thu, 19 Aug 2021 03:15:08 +0100</pubDate>
<lastBuildDate>Thu, 19 Aug 2021 03:21:16 +0100</lastBuildDate>
<pubDate>Thu, 19 Aug 2021 03:21:16 +0100</pubDate>
<atom:link href="https://gnusocial.rocks/v3/feed.rss" rel="self" type="application/rss+xml" />
<item><title>
Updates: V3 blog
@ -26,6 +26,8 @@ forget to subscribe!</p>
<!-- text end -->
]]></description><link>https://gnusocial.rocks/v3/updates-v3-blog.html</link>
<guid>https://gnusocial.rocks/v3/./updates-v3-blog.html</guid>
@ -116,6 +118,8 @@ functionality with more stability.</p>
@ -128,14 +132,30 @@ functionality with more stability.</p>
Updates: Improve the Attachments system
</title><description><![CDATA[
<p>With the milestone "Port Media system from v2" we had ported the existing
<p>With the milestone <a href="https://www.gnusocial.rocks/v3/milestone-port-media-handling-from-v2.html">Port Media system from
v2</a> we had ported the existing
attachment system. The fact is that this system wasn't good enough.</p>
<p>It's always important to start with the original code as that allows us
to review past decisions and understand all the corner cases.</p>
to review past decisions and understand all the corner cases previously
considered.</p>
<p>Sadly, what motivated us to re-design the attachment system was the
non-considered corner cases.</p>
<p>Sadly, what motivated us to re-design the attachment system were the
non-considered corner cases. In particular:</p>
<ul>
<li>Remove <code>title</code> from attachment, as it's part of the relation between attachment and note.</li>
<li>Remove <code>actor</code> from attachment, many actors may publish the same attachment.</li>
<li>Remove <code>is_local</code> from attachment, as it's part of the relation between attachment and note.</li>
<li>Remove <code>remote_url</code> from attachment, different urls can return the same attachment.</li>
<li>Attachment now has a reference counter </li>
<li>Add entity GSActorToAttachment</li>
<li>Add entity GSActorToRemoteURL</li>
<li>Add entity RemoteURL</li>
<li>Add entity RemoteURLToNote</li>
<li>Add entity RemoteURLToAttachment</li>
<li>AttachmentToNote now has a title attribute</li>
</ul>
<p>Key commits:</p>
@ -144,7 +164,7 @@ non-considered corner cases.</p>
<li><a href="https://code.undefinedhackers.net/GNUsocial/gnu-social/commit/c381e58d3307e7dd07abeb9cf5b3998e34f5bd48">c381e58d33 - [ENTITY] Refactor RemoteURL entities to Link</a></li>
</ul>
<p>The reasoning leading to these entities and structure is detailed in our
<p>The structural changes and how it compares to v2 is detailed in our
<a href="http://agile.gnusocial.rocks/doku.php?id=attachment">wiki</a>.</p>
<p>Some relevant observations:</p>
@ -156,71 +176,6 @@ any remote URL being shared in a note.</li>
</ul>
<!-- text end -->
]]></description><link>https://gnusocial.rocks/v3/updates-improve-the-attachments-system.html</link>
<guid>https://gnusocial.rocks/v3/./updates-improve-the-attachments-system.html</guid>
@ -300,6 +255,8 @@ Updates: Finish the Avatar component
@ -349,6 +306,8 @@ is properly tested, we have the
<a href="https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/tests">tests</a>. And the coverage is available <a href="https://coverage.gnusocial.rocks/">here</a>. At the time of writing the coverage has 98.76% code lines tested.</p>
<!-- text end -->
]]></description><link>https://gnusocial.rocks/v3/milestone-documentation-and-tests-infrastructure.html</link>
<guid>https://gnusocial.rocks/v3/./milestone-documentation-and-tests-infrastructure.html</guid>
@ -399,6 +358,8 @@ The key ones are:</p>
<!-- text end -->
]]></description><link>https://gnusocial.rocks/v3/milestone-port-media-handling-from-v2.html</link>
<guid>https://gnusocial.rocks/v3/./milestone-port-media-handling-from-v2.html</guid>

2
v3/milestone-documentation-and-tests-infrastructure.html
View File

@ -80,6 +80,8 @@ is properly tested, we have the
<a href="https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/tests">tests</a>. And the coverage is available <a href="https://coverage.gnusocial.rocks/">here</a>. At the time of writing the coverage has 98.76% code lines tested.</p>
<!-- text end -->
<!-- entry end -->
</div>

2
v3/milestone-port-media-handling-from-v2.html
View File

@ -84,6 +84,8 @@ The key ones are:</p>
<!-- text end -->
<!-- entry end -->
</div>

2
v3/updates-finish-the-avatar-component.html
View File

@ -113,6 +113,8 @@ GNU social development team

2
v3/updates-implement-storeremotemedia-for-v3-and-port-embed.html
View File

@ -124,6 +124,8 @@ functionality with more stability.</p>

91
v3/updates-improve-the-attachments-system.html
View File

@ -43,14 +43,30 @@ GNU social development team
</div>
<!-- text begin -->
<p>With the milestone "Port Media system from v2" we had ported the existing
<p>With the milestone <a href="https://www.gnusocial.rocks/v3/milestone-port-media-handling-from-v2.html">Port Media system from
v2</a> we had ported the existing
attachment system. The fact is that this system wasn't good enough.</p>
<p>It's always important to start with the original code as that allows us
to review past decisions and understand all the corner cases.</p>
to review past decisions and understand all the corner cases previously
considered.</p>
<p>Sadly, what motivated us to re-design the attachment system was the
non-considered corner cases.</p>
<p>Sadly, what motivated us to re-design the attachment system were the
non-considered corner cases. In particular:</p>
<ul>
<li>Remove <code>title</code> from attachment, as it's part of the relation between attachment and note.</li>
<li>Remove <code>actor</code> from attachment, many actors may publish the same attachment.</li>
<li>Remove <code>is_local</code> from attachment, as it's part of the relation between attachment and note.</li>
<li>Remove <code>remote_url</code> from attachment, different urls can return the same attachment.</li>
<li>Attachment now has a reference counter </li>
<li>Add entity GSActorToAttachment</li>
<li>Add entity GSActorToRemoteURL</li>
<li>Add entity RemoteURL</li>
<li>Add entity RemoteURLToNote</li>
<li>Add entity RemoteURLToAttachment</li>
<li>AttachmentToNote now has a title attribute</li>
</ul>
<p>Key commits:</p>
@ -59,7 +75,7 @@ non-considered corner cases.</p>
<li><a href="https://code.undefinedhackers.net/GNUsocial/gnu-social/commit/c381e58d3307e7dd07abeb9cf5b3998e34f5bd48">c381e58d33 - [ENTITY] Refactor RemoteURL entities to Link</a></li>
</ul>
<p>The reasoning leading to these entities and structure is detailed in our
<p>The structural changes and how it compares to v2 is detailed in our
<a href="http://agile.gnusocial.rocks/doku.php?id=attachment">wiki</a>.</p>
<p>Some relevant observations:</p>
@ -71,71 +87,6 @@ any remote URL being shared in a note.</li>
</ul>
<!-- text end -->
<!-- entry end -->
</div>

24
v3/updates-improve-the-attachments-system.md
View File

@ -1,20 +1,34 @@
Updates: Improve the Attachments system
With the milestone "Port Media system from v2" we had ported the existing
With the milestone [Port Media system from
v2](https://www.gnusocial.rocks/v3/milestone-port-media-handling-from-v2.html) we had ported the existing
attachment system. The fact is that this system wasn't good enough.
It's always important to start with the original code as that allows us
to review past decisions and understand all the corner cases.
to review past decisions and understand all the corner cases previously
considered.
Sadly, what motivated us to re-design the attachment system was the
non-considered corner cases.
Sadly, what motivated us to re-design the attachment system were the
non-considered corner cases. In particular:
* Remove `title` from attachment, as it's part of the relation between attachment and note.
* Remove `actor` from attachment, many actors may publish the same attachment.
* Remove `is_local` from attachment, as it's part of the relation between attachment and note.
* Remove `remote_url` from attachment, different urls can return the same attachment.
* Attachment now has a reference counter
* Add entity GSActorToAttachment
* Add entity GSActorToRemoteURL
* Add entity RemoteURL
* Add entity RemoteURLToNote
* Add entity RemoteURLToAttachment
* AttachmentToNote now has a title attribute
Key commits:
* [32ad5dbd74 - [ENTITY] Split Attachment in various new entities](https://code.undefinedhackers.net/GNUsocial/gnu-social/commit/32ad5dbd74ebb369c4b3ed688e1fb78464fabe49)
* [c381e58d33 - [ENTITY] Refactor RemoteURL entities to Link](https://code.undefinedhackers.net/GNUsocial/gnu-social/commit/c381e58d3307e7dd07abeb9cf5b3998e34f5bd48)
The reasoning leading to these entities and structure is detailed in our
The structural changes and how it compares to v2 is detailed in our
[wiki](http://agile.gnusocial.rocks/doku.php?id=attachment).
Some relevant observations:

2
v3/updates-v3-blog.html
View File

@ -60,6 +60,8 @@ forget to subscribe!</p>
<!-- text end -->
<!-- entry end -->
</div>