Name: twtxt
Homepage: https://dev.twtxt.net/
Short description: Decentralised self-hosted social media that has a privacy-first focus
Optional API documentation URL: https://dev.twtxt.net/doc/api.html

--edit--

Made a better introduction that refers to the protocol rather than an instance. Here's the old introduction.

Name: Yarn.social
Homepage: https://yarn.social
Short description: Decentralised self-hosted social media that has a privacy-first focus
Optional API documentation URL: https://dev.twtxt.net/doc/api.html

Here's the JSON result to an API call to fetch profile data:

// https://twtxt.net/api/v1/profile/example

{
  "profile": {
    "Type": "User",
    "URL": "https://twtxt.net/user/prologic/twtxt.txt",
    "Username": "example",
    "Avatar": "https://....",
    "Tagline": "Some text!",
    "Links": [
      {
        "Title": "Keyoxide",
        "URL": "https://..."
      }
    ],
    ...
  }
}

I detect two possibilities: using the links to a Keyoxide profile containing the fingerprint, or inserting the fingerprint in the Tagline.

Need to figure if either the tagline has a character limit or if there's a limit to the number of links.

10 days later

I think it might be better to generically support twtxt, rather than specifically Yarn.social.

Either way, I think "using the links to a Keyoxide profile containing the fingerprint" is the best solution – except that you wouldn't need to link to Keyoxide profile specifically, links to a PGP key should also be supported. Maybe also links with the openpgp4fpr URI scheme.

Alternatively, https://twtxt.net/~prologic/ could be approached about adding a new field to the twtxt metadata extension.

yarmo changed the title to Add twtxt .

Updated the intro post to refer to the protocol instead of the instance. Good catch, @caesar!

Yes, I agree links would be best and indeed, doesn't need to be a Keyoxide link. The openpgp4fpr is sufficient!

And soon, with "multiple verification methods" support, we can have both link and tagline 😉 We can contact https://twtxt.net/~prologic/ for their opinion but I don't think we need extra fields (yet).

a year later

Hiya! Any update on this? twtxt / yarn.social now supports activitypub too, fyi, if that's any help. 🙂

I'm happy to liaise with prologic, if that's helpful, or work on testing with my twtxt / yarn.social 'pod' at twt.nfld.uk (although, I haven't been able to get activitypub working on my instance just yet -- it's definitely working on the flagship, twtxt.net, though!).

    Sorry, been so busy with other aspects of Keyoxide development. Well, if they support activitypub, then Keyoxide already supports twtxt! I'd have to try it out.

    jlj although, I haven't been able to get activitypub working on my instance just yet --

    Ok, so twtxt+AP is not foolproof yet and thus it would be great to specifically support twtxt. I'll try and find someone to investigate this further.

        a year later

        jlj Hiya! Any update on this? twtxt / yarn.social now supports activitypub too, fyi, if that's any help. 🙂

        Unfortunately, leveraging ActivityPub to verify twtxt accounts hosted on Yarn.social pods is no longer viable. First, it has been disabled on the flagship twtxt.net instance for quite some time (https://search.twtxt.net/search?q=conv:%23ydvbawq&s=created&s=_id), and here are James's thoughts about it: https://search.twtxt.net/twt/jrmwywq

        yarmo Ok, so twtxt+AP is not foolproof yet and thus it would be great to specifically support twtxt. I'll try and find someone to investigate this further.

        Going to open a new feature request on doip.js issue tracker and copy over all relevant info.