reiver, 2 months ago

2/

The first thing I did was make WebFinger work on my (new) personal website.

(I.e., "/.well-known/webfinger".)

Which needs to return JSON similar to what is in the attached screenshot.

(And also best return a "Content-Type: application/jrd+json".)

...

Your implementation would replace "subject" and "href" with your own values.

...

So, next —

reiver, 2 months ago

3/

The next thing I did was make that "self" URL I returned from WebFinger work.

It needs to return something like what is in the attached screenshot.

...

There is a lot there, but what is there is straightforward.

I will go into what it means in a practical sense —

reiver, 2 months ago (edited 2 months ago)

4/

"preferredUsername" is your Fediverse handle (without the host).

"name" is your name.

"summary" is the text for your profile's (short) bio.

"attachement" are a list of name-value pairs you set on your profile. I used it just for a "Location". You could create a list of them.

"published" is the date when you joined the Fediverse.

...

reiver, 2 months ago

5/

"url" is the URL of the version of your profile someone would go to to see it in a web-browser. (Since this is a my (new) personal website is a solo single-user site, I set it to my home-page.)

You can just set "id" to whatever URL you returned from WebFinger (for the "self" URL).

"icon" is the profile avatar image.

"image" is the banner image on your profile.

...

reiver, 2 months ago

6/

And then there are a bunch of new URLs in there.

"following", "followers", "icon.url", "image.url"., "inbox".

We need to make those work, too.

So let's do that —

reiver, 2 months ago

7/

Making "icon.url" and "image.url" (from the "self" URL) work are straight forward —

They are just images — the avatar image and banner image respectively.

Upload those images somewhere. (It doesn't have to be the same place I put mine.)

And make the JSON returned from your "self" URL return the URLs to wherever you uploaded your avatar image and banner image.

...

reiver, 2 months ago

8/

So now let's look at making the "following" and "followers" URLs work.

...

reiver, 2 months ago

9/

This (in the attached screenshot) is what I return from my "following" URL.

...

For your implementation —

"totalItems" is probably the most interesting thing in there at this point — that is the number of people you follow.

(A full implementation would get this number from the actual number of people you follow. But this VERY BASIC implementation can just put whatever number you want.)

Just set "id" whatever URL you have for "following".

...

reiver, 2 months ago

10/

For your implementation —

The URL for "first" will eventually matter — but not yet.

I didn't implement it. It you go to it right now it will return a "404 Not Found".

But — that seems to be OK if all you want to do is — look up your website using a Fediverse ID and have a profile show up.

...

reiver, 2 months ago

11/

This (in the attached screenshot) is what I return from my "followers" URL.

...

For your implementation —

Again, "totalItems" is probably the most interesting thing in there at this point — that is the number of people who follow you.

(A full implementation would get this number from the actual number of people who follow you. But this VERY BASIC implementation can just put whatever number you want.)

Just set "id" whatever URL you have for "followers".

...

reiver, 2 months ago

12/

For your implementation —

Again, the URL for "first" will eventually matter — but not yet.

I didn't implement it. It you go to it right now it will return a "404 Not Found".

But — that seems to be OK if all you want to do is — look up your website using a Fediverse ID and have a profile show up.

reiver, 2 months ago (edited 2 months ago)

13/

And that seems to be all you need to do to be able to look up your website using a Fediverse ID and have a profile show up.

I didn't even implement "inbox" (even though I included a URL for it)

You could probably do all this with static files.

...

For me, the next step is probably to make it so people can follow my (new) personal website on the Fediverse.

More on that later, after I implement it.

reiver, 2 months ago

14/

FOLLOW-UP №1:

I've been noticing that Mastodon has been trying to POST something to the "inbox" URL I provided.

And it seems to have been doing that, more or less, non-stop since I first looked up my (new) personal website with a Fediverse ID.

(It started way before I wrote this thread.)

The lookup worked. But, I wonder what it is trying to POST. (I didn't try following. So I wouldn't expect that.)

reiver, 2 months ago

15/

FOLLOW-UP №2:

A least one server is trying to do 'nodeinfo' lookups on my (new) personal website.

I haven't implemented nodeinfo yet either.

(nodeinfo is one of the other protocols used on the Fediverse. Most people are aware of ActivityPub. But there is more than just ActivityPub.)

...

The nodeinfo lookup probably has nothing directly to do with what I described in this thread. But because someone put the Fediverse ID to my (new) personal website in a post.

https://mas.to/@tezoatlipoca/112134212848812497

.

reiver, 2 months ago

16/

FOLLOW-UP №3:

These logs are interesting.

I wonder if they are Friendica specific URLs?

Or if other (non-Friendica + forks) servers also implement them?