Post

I've added endpoints to my website to follow Caleb's new SocialSpec APIs - feed, following, about, and contact. Interested to see where this goes.

How does it compare to the IndieWeb at large?

I've spent a lot of time looking at the various indie web projects, including microformats (e.g. h-cards), and I love me some HTML templating (that's why I built hypertexting.dev/docs/referen...)! SocialSpec shouldn't be in conflict with indie web ideas.

And my initial goal with SocialSpec is to think of it as a **documentation** project. I haven't invented anything here really. Just documenting some ideas based on existing open standards.

...but my thinking about approaches like h-cards has always been that they require per-theme implementation effort as opposed to a per-CMS implementation effort. The SocialSpec APIs should require significantly less effort; they are single purpose, single file, and a single request APIs.

Sounds like your aim is similar to what OStatus was some 10-15 years ago – connect existing things together with some minimal additional glue rather than inventing something new. I have lots I want to say and propose but little time to do so 🙈

Here's how I would do it: gist.github.com/voxpelli/fbe... Base it on link relations rather than .well-known URL:s as: - link relations are possible to create without having to register them to be spec compliant - one request can discover everything - builds on existing WebFinger (and/or host-meta)

I still go back to this old mockup when I think of what we want: factoryjoe.com/2008/12/20/w... I do think link relations through Webfinger / Host-meta would be a good solution that would be more extensible and reinvent less. /cc @chrismessina.me @blaine.bsky.social

Eg. both Mastodon and @ap.brid.gy already supports both `/.well-known/host-meta` and `/.well-known/webfinger?resource=...` Only thing out of spec for Mastodon is that it only publishes JSON-based JRD while the current host-meta spec still mandates XML-based XRD as default. /cc @snarfed.org