Parsing RSS feeds is always a pain. Don’t parse feeds inside the template engine kids :-)

SVG is a solid tactic. No one “inspect elements” every site. Everyone’s a user, even programmers — they won’t know until someone tells them.

I just noticed that Mastodon prefixes a user’s homepage URL route with the @at symbol. Pragmatic and clever name spacing? Tempting. Though I’d still prefer a URL of the form:

https://example.com/user

Instead of:

https://example.com/@user

Yeah… superficial, but it looks cleaner.

A lot of websites dump the entire feed — that’s nice. Ideally for bandwidth efficiency, combine multiple delivery strategies.

1. A partial content feed (Atom preferred) limited to the last 3/5/10 posts for quick queries.

2. A full content RSS feed of a similar limit for fresh content.

3. A hidden/unlisted feed for dumping all content (mirror).

Alternatively, just implement atom’s collection partial lists for feed pagination. If your post bandwidth (size/frequency) is low, then pretend you didn’t see this — be lazy and optimize later.