lucidiot/rsrsss
lucidiot
/
rsrsss
2
1
Fork 0
Code Issues Releases Activity

Post about HINA and LIRS

This commit is contained in:
~lucidiot 2021-07-26 09:58:20 +02:00
parent 88408f3994
commit 7137158504
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
feed.xml
View File

@ -328,5 +328,21 @@
<p><a href="https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/aa768139(v=vs.85)" target="_blank">Channel Definition Format</a> allows for nested channels, so you could at least create a structured representation of a thread as a tree if you, the original author of the post, knew about all the replies. You cannot, however, specify that you are replying to something yourself. The format does support XML namespace extensions, so you could use <code>thr</code> or mod_annotation.</p>
]]></description>
</item>
<item>
<title>Exploring obsolete Japanese syndication formats</title>
<pubDate>Sat, 03 Apr 2021 16:24:10 +0200</pubDate>
<guid isPermaLink="false">japanese-formats</guid>
<category domain="https://envs.net/~lucidiot/rsrsss/">HINA</category>
<category domain="https://envs.net/~lucidiot/rsrsss/">LIRS</category>
<description><![CDATA[
<p>I am always fascinated when I somehow manage to learn a bit about the early days of the Internet in South East Asia. At a time when Unicode barely even existed, when non-Latin alphabet support was just relying on a ton of hacks, a lot of interesting things happened.</p>
<p>I recently translated some Japanese specifications I found on the Wayback Machine for two obsolete syndication formats. I first had to determine which encoding the specifications were using, because Google Translate was really unhappy with that; I had to convert from Shift-JIS to UTF-16 then to UTF-8, and from EUC-JP to UTF-8. I am using Google Translate because I know absolutely nothing about Japanese; I just take the messy "English" translation and turn it into comprehensible English.</p>
<p>I first translated <a href="https://envs.net/~lucidiot/hina/" target="_blank">HINA</a>, a format that relies on RFC 822 message headers and was designed for Asahina-Antenna. It appears that in Japan, feed readers were called "antennas". This format is apparently still served by some websites according to a quick online search; I will look into that later, just as I will look into those antennas.</p>
<p>Today, I translated <a href="https://envs.net/~lucidiot/lirs/" target="_blank">LIRS</a>, a format that uses a gzipped simili-CSV to report the same thing.</p>
<p>These two formats do not have item descriptions or optional URLs; they are only meant to report changes on external content. They already take into account the notion of feed aggregation. HINA even has image-related data for photo galleries.</p>
<p>It is pretty hard to trace those formats, first because of the rather obvious language barrier I am facing, and second because the Wayback Machine did not always catch everything, so there are many dead links. Of course, everything is completely dead today. I am however going to keep looking into those formats, and they will soon be implemented in <a href="https://tilde.town/~lucidiot/itsb/" target="_blank">ITSB</a> just for the sake of keeping them alive.</p>
]]></description>
</item>
</channel>
</rss>