jkap

jae

@jkap

CEO of posting

butch jewish dyke
part of @staff, cohost user #1
married to @kadybat

This user can say it
osu stats

log inask
🔵 tumblr
yrfriendjkap.tumblr.com/
🐘 mastodon
xoxo.zone/@jkap
🖼️ icon credit
twitter.com/osmoru
🐦 twitter
not anymore lol
🎬 letterboxd
letterboxd.com/yrfriendjkap/
jkap
@jkap
jkap
@jkap
jkap
@jkap

open question re: our atom implementation

  • the atom spec defines <title /> as a required field within an <entry />
  • not all cohost posts have titles
  • including an empty title is invalid, not including a title is invalid
  • fucking. come on

do you use atom? what do you want to see in the title field for posts that don't have titles?

(also at some point i need to change how we do shares but that's Actually Hard)

jkap
@jkap

lmao posts with no body aren't valid either

look. i love open specs syndicating Content. but if your content diverges even a little bit from what the spec is designed for, you are in for a fucking world of pain. atom is from 2005; twitter didn't exist, the fucking iphone didn't even exist yet. people were writing Blogs. not writing a blog? too fucking bad. make it look like a blog post or we'll kill you.

you'd assume that JSON feed wouldn't have as many of these problems because it's Modern (only 6 years old instead of 18!) but it's designed around the type of blogging that a very specific subset of bloggers do, so it supports shit like Link Blogs but ALSO requires Content, so title only posts (which is how we interpret posts with content in only the headline field) are also invalid! augh!!!!!!!!

You must log in to comment.

in reply to @jkap's post:

noahtheduke
@noahtheduke

title, if blank: According to all known laws of aviation, there is no way a bee should be able to fly. Its wings are too small to get its fat little body off the ground. The bee, of course, flies anyway because bees don't care what humans think is impossible. Yellow, black. Yellow, black. Yellow, black. Yellow, black. Ooh, black and yellow! Let's shake it up a little. Barry! Breakfast is ready. Coming! Hang on a second. Hello? Barry?

login to reply

in reply to @jkap's post:

fluffy
@fluffy

Think of atom feeds as the API for alternate dashboards/clients. It's really nice to be able to give people the ability to use whatever tools they want to follow their social feeds, instead of being locked in to a specific frontend. It's good for accessibility, good for interoperability, and good for the Internet in general.

Plus I like being able to follow all my friends from a single dashboard (i.e. feed reader), especially for friends and things that I definitely want to see everything from (such as webcomics, or folks on Tumblr or Cohost who I enjoy reading most content from). It's also nice to have a reader app that keeps track of what I've seen arleady, and it fits my brain way better than having to deliberately page through many pages of Stuff until I find things that I remember seeing already. If I deliberately skip something in my feed reader, it's gone forever.

login to reply
fluffy
@fluffy

I think you are allowed to have a content-less <title> and <content> tag.

RSS and Atom certainly leave a lot to be desired (and I am extremely non-fond of how Atom has a bunch of specification for category tags but no documentation on how they're meant to be used, and how its concept of a "repost" also requires that you include a bunch of information from the original feed including its URL, which has huge implications on privacy for things like private individual feeds), but they're still the least-shitty of all the standards out there for this stuff that actually get used.

HTML+mf2 is a better standard in general but it's not really supported outside of IndieWeb purists, and most IndieWeb folks also provide an Atom feed as a concession to tooling (or at least provide a granary.io mf2->atom autoconversion).

login to reply
Pinned Tags