Post about Gitea feeds

This commit is contained in:
~lucidiot 2022-03-06 21:59:05 +01:00
parent eb759f6492
commit 1d5fe98f0b
1 changed files with 19 additions and 0 deletions

View File

@ -580,6 +580,7 @@
This is a very interesting blog that ran in 2019 with one post a day. Each post studied one <abbr title="Request for Comments">RFC</abbr> at once, starting from the very first one, and its author went as far as visiting the <a href="https://www.computerhistory.org/">Computer History Museum</a> to get access to the original RFCs as they were before they got poorly transcribed into their current online forms, as they included handwritten diagrams. That blog is now dead, but if you want to learn about the history of the Internet, this is a very good resource. This taught me among other things that Telnet is older than the Internet itself.
]]></description>
</item>
<item>
<title>computers are bad</title>
<pubDate>Sun, 19 Dec 2021 19:48:30 +0100</pubDate>
@ -618,6 +619,7 @@
<p>It's always great to see someone other than me show some interest in feeds, especially to the point of creating new feeds. This service might not have the most well written Python code, or might break easily should any of those websites choose to change something, but it has the merit of existing and of being a reminder that feeds do exist and that some people want them. Just that alone gives me warm fuzzies.</p>
]]></description>
</item>
<item>
<title>sfeed</title>
<pubDate>Sun, 09 Jan 2022 22:31:53 +0100</pubDate>
@ -635,6 +637,7 @@
<p>While the Atom feed feels a little crude to me, a constant abuser of XML namespaces inside of feeds, I like the idea of what is basically a static site generator whose content comes from feeds. Static sites always feel much more manageable to me, be it as a developer, as a server administrator, or as an archivist. I do have an archivist side, with how much I've been using the Internet Archive in all my projects.</p>
]]></description>
</item>
<item>
<title>DeviantArt feeds</title>
<pubDate>Wed, 19 Jan 2022 21:40:42 +0100</pubDate>
@ -745,6 +748,7 @@
<p>I couldn't find out what truly is the <code>.sfm</code> file extension, so if you know about it, please <a href="//tilde.town/~lucidiot/contact.html" target="_blank">let me know</a>.</p>
]]></description>
</item>
<item>
<title>Requests for Comments</title>
<pubDate>Wed, 09 Feb 2022 11:40:18 +0100</pubDate>
@ -756,6 +760,7 @@
<p>I guess having that Atom feed was quite predictable, considering that Atom has been standardized in <a href="https://datatracker.ietf.org/doc/html/rfc4287" target="_blank">RFC 4287</a>. Also note that RFCs should now be written using a specific XML format, also defined in another RFC; <a href="https://datatracker.ietf.org/doc/html/rfc7991">RFC 7991</a> being the current version. It feels quite strange to me to see such "high-level" formats in an RFC; I am more used to seeing RFCs about lower-level protocols like <abbr title="Transmission Control Protocol">TCP</abbr>/<abbr title="Internet Protocol">IP</abbr> or <abbr title="Border Gateway Protocol">BGP</abbr>.</p>
]]></description>
</item>
<item>
<title>Emojipedia Blog</title>
<pubDate>Tue, 15 Feb 2022 01:34:54 +0100</pubDate>
@ -766,6 +771,7 @@
Another proof that Unicode probably goes too far: there is enough to say about emojis that an entire blog is dedicated to them. This is an RSS feed that has been sent to me by a friend, and this feed will definitely not make it into my RSS reader. I am posting this from a PuTTY session on a Windows XP laptop; I can't see any emojis there, so it is completely irrelevant.
]]></description>
</item>
<item>
<title>linkbudz</title>
<pubDate>Sun, 27 Feb 2022 21:21:45 +0100</pubDate>
@ -776,5 +782,18 @@
<p>A new project of <a href="https://m455.casa" target="_blank">~m455</a> involves an IRC bot that listens to the <code>!post</code> command on his private IRC server to let a user post a link with some title to <a href="https://linkbudz.m455.casa" target="_blank">a webpage</a>. The project kicked off nicely by not having any HTML sanitization, so the trolls (and QA engineers I guess) that we are on this IRC server sent tons of JavaScript, CSS overrides, iframes, background music, etc. That broke the RSS feed, but the sanitization is now properly in place and the feed is usable. If you are curious to see what our little corner of the internet finds on other corners of the internet, feel free to look around and subscribe to the feed.</p>
]]></description>
</item>
<item>
<title>Gitea's first feeds</title>
<pubDate>Sun, 06 Mar 2022 21:58:39 +0100</pubDate>
<guid isPermaLink="false">gitea-user-feed</guid>
<category domain="https://envs.net/~lucidiot/rsrsss/">Tip</category>
<description><![CDATA[
<p>Gitea 1.16.0 <a href="https://github.com/go-gitea/gitea/pull/16002" target="_blank">adds support</a> for user feeds. Those feeds include the things you see on a user's recent activity page. They are accessible either by setting the <code>Accept</code> header to <code>application/rss+xml</code> or <code>application/atom+xml</code>, or by appending <code>.rss</code> or <code>.atom</code> to a username.</p>
<p>For example, you can check out the <a href="https://tildegit.org/lucidiot.rss" target="_blank">RSS feed</a> and the <a href="https://tildegit.org/lucidiot.atom" target="_blank">Atom feed</a> for my profile on <a href="https://tildegit.org" target="_blank">tildegit.org</a>, the Gitea instance hosted by and for <a href="https://tildeverse.org" target="_blank">the tildeverse</a>.</p>
<p>This is a nice first step, though I feel that user feeds are among the least useful of all the feeds that most common Git platforms provide. As I also maintain Alpine Linux packages, help manage <a href="https://breadpunk.club" target="_blank">breadpunk.club</a> and manage my own server at home, the feeds that would matter the most to me are the tags or release notes feeds. Those feeds are the most efficient way to be notified of any new releases on most software, and I have opened <a href="https://github.com/wustho/epy/issues/47" target="_blank">some</a> <a href="https://github.com/iscc/mobi/issues/8" target="_blank">issues</a> in the past to ask some maintainers to use Git tags just so I can use the feed.</p>
<p>There is <a href="https://github.com/go-gitea/gitea/issues/569" target="_blank">an issue for global feed support</a>, and it is on the 1.17.0 roadmap. I subscribed to it, using the unfortunately email-based GitHub notification system, and will definitely follow it closely.</p>
]]></description>
</item>
</channel>
</rss>