<?xml version="1.0" encoding="UTF-8"?>
<oembed>
 <version>1.0</version>
 <type>link</type>
 <provider_name>Rainbow Dash Network</provider_name>
 <provider_url>http://rainbowdash.net/</provider_url>
 <title>RDN's Lucifer (nerthos)'s status on Monday, 13-Feb-17 15:12:13 UTC</title>
 <author_name>RDN's Lucifer (nerthos)</author_name>
 <author_url>http://rainbowdash.net/nerthos</author_url>
 <url>http://rainbowdash.net/notice/4609678</url>
 <html>@&lt;span class=&quot;vcard&quot;&gt;&lt;a href=&quot;http://quitter.se/hannes2peer&quot; class=&quot;url&quot; title=&quot;hannes2peer&quot;&gt;&lt;span class=&quot;fn nickname mention&quot;&gt;hannes2peer&lt;/span&gt;&lt;/a&gt;&lt;/span&gt; conversation_id is in place to prevent one of the most annoying things we had to deal with back in 2011 when most of the fediverse ran on statusnet: whenever someone deleted a post, the entire conversation tree would crumble and going into context would just show loose messages, or an individual post. It has a good reason to exist and should not be removed unless you want to go back 6 years in development. While it's not an issue for networks focused in ultra-casual, meaningless interaction, it's highly consequential for any node that values extensive and meaningful discussion, and for any implementation of GNUsocial in a work environment where easily following conversations is required.</html>
</oembed>
