# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 14
# self = https://watcher.sour.is/conv/hl4muca
@mckinley Now do one on Twtxt vs. Activity Pub and then Mastodon vs. Yarn.social š
@mckinley Now do one on Twtxt vs. Activity Pub and then Mastodon vs. Yarn.social š
@prologic I'd like to write about twtxt at some point but I'm not very familiar with Mastodon and ActivityPub. Maybe you should write that one :)
I love the "RSS appear to have been duct-taped to the specification as an afterthought" part.
@mckinley Nice, thank you!
Oof, right, Iām beginning to remember. š
RSS is quite the mess.
Hmm, my feeds use type="html"
for <content>
and <title>
. Iām gonna fix that.
@mckinley Nice, thank you!
Oof, right, Iām beginning to remember. š
RSS is quite the mess.
Hmm, my feeds use type="html"
for <content>
and <title>
. Iām gonna fix that.
@mckinley Nice, thank you!
Oof, right, Iām beginning to remember. š
RSS is quite the mess.
Hmm, my feeds use type="html"
for <content>
and <title>
. Iām gonna fix that.
@mckinley Nice, thank you!
Oof, right, Iām beginning to remember. š
RSS is quite the mess.
Hmm, my feeds use type="html"
for <content>
and <title>
. Iām gonna fix that.
@mckinley Thank you! I didn't even know about signing and encrypting XML documents. Right, RSS is a little bit messy.
Unfortunately, the autodiscovery document in one of your linked resources does not exist anymore. What annoys me in Atom is the distinction between <id>
and <link>
. I always want my URL also to be my ID, so I have to duplicate that ā unnecessarily in my opinion.
Also, never found a good explanation why I should add <link rel="self" ā¦ />
to my feeds. I just do, but I don't understand why. The W3C Feed Validation Service says:
> [ā¦] This value is important in a number of subscription scenarios where often times the feed aggregator only has access to the content of the feed and not the location from which the feed was fetched.
This just sounds like a very questionable bandaid to bad software architecture. Why would the feed parser need access to the feed URL at this stage? And if so, why not just pass down the input source? Just doesn't make sense to me.
Also, I just noticed that I reference the http://purl.org/rss/1.0/modules/syndication/
namespace, but don't use it in most of my feeds. Gotta fix that. Must have copied that from my yfav feed without paying attention what I'm doing.
Your article made me reread the Atom spec and I found out, that I can omit the <author>
in the <entry>
when I specify a global <author>
at <feed>
level. Awesome! Will do that as well and thus reduce the feed size.
@mckinley @lyse The link rel bit is because the feed can have relative urls. ie, if it is on http://example.com/feed, in can have somewhere in there a
for eg.. If I download that feed I to my hard-drive and then try to render it, I need to know that "icon.jpg" is relative to http://example.com/feed, ie, that I will find it at http://example.com/icon.jpg (and not locally, next to the feed file I downloaded).
I hope my explanation makes sense...=
@mckinley @lyse The link rel bit is because the feed can have relative urls. ie, if it is on http://example.com/feed, in can have somewhere in there a
for eg.. If I download that feed I to my hard-drive and then try to render it, I need to know that "icon.jpg" is relative to http://example.com/feed, ie, that I will find it at http://example.com/icon.jpg (and not locally, next to the feed file I downloaded).
I hope my explanation makes sense...=