Post

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.

0 reposts0 likes

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 🙈

I'm willing to wait to hear more thoughts! ...I still need to flesh out some kind of RFC / feedback process in the GitHub repos to facilitate these conversations. For now I've only stubbed issue #1 in each repo.

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)

gist.github.comFeedback for https://socialspec.org/ based on / inspired by RFC 6415, 7033 and 8288Feedback for https://socialspec.org/ based on / inspired by RFC 6415, 7033 and 8288 - host-meta.json