Social Network

Publish three files, and share yourself with the world.

social.jake.fun is this specific social domain.

• Visit buddy.pizza.jake.fun for the latest reader (repo).
• Visit buddy.pizza.jake.fun?s=your-domain.com if you want to see your personal feed.
• Visit buddy.pizza.jake.fun/post for a post template.

Instructions

Participate by publishing three JSON files to the internet.

• profile.json is an object describing yourself.
• stream.json is an array of your posts.
• following.json is an array of the domains you are following.

Anyone that knows about your profile and stream can access it on the internet. If someone knows about many streams, they can collect them all together in a "feed" to be displayed however they like.

CORS

You'll want to allow CORS (adding a Access-Control-Allow-Origin: * header) so that client side JavaScript can access your files. _headers in this repo is an example of how to do this for Netlify. GitHub pages should support this out of the box!

What does the data look like?

Your profile and stream can look however you want them to look. As long as they are valid JSON, they can be read by anyone.

However, if you are looking to do this with other people, you'll want the structure of your JSON to follow at least some rules so that a reader knows how to handle your stream and profile.

profile.json

Currently, I am proposing the following for a minimal profile.json

{
  "@": "jandoe",
  "name": "Jan Doe",
  "pronouns": "whoever/you/are",
  "location": "Anytown, USA",
  "bio": "normal bio [with links](https://links.com)",
  "website": "https://jandoe.com",
  "image": {
    "url": "https://website.com/image.jpg",
    "alt": "A picture of me looking directly into the camera",
    "height": 600,
    "width": 600
  }
}

stream.json

For stream.json the only important value is a time value. This way posts can be ordered when streams are combined into a feed. For that, use a millisecond epoch. You can get that by running Date.now() in a JavaScript console, or using a tool like buddy.pizza.jake.fun/post which provides templates. The number should be 13 digits long and in the JSON as numbers (not strings).

Currently, I am proposing something like this for a basic stream that supports text, image, and link posts:

[
  {
    "text": "a text post with an image",
    "image": {
      "url": "https://image.com/image.jpg",
      "alt": "alt text of the image.",
      "height": 600,
      "width": 600
    },
    "time": 1650938694864
  },
  {
    "text": "a text post with a link at the end",
    "url": "https://link.com/something",
    "time": 1650938170000
  },
  {
    "text": "a pure text post",
    "time": 1650938164497
  }
]

These can really look however you want them to though. No one is saying you have to do it this way. I am making a reader that reads ^ this format, but you can make a reader that reads whatever you and your friends want to post.

following.json

Currently using following.json as an array of domains that you are following. This array can be used by a reader to assemble your feed, and can be used by others to explore the network.

The domains at following.json are listed without protocol. SSL is assumed.

[
  "social.jake.fun",
  "social.buddy.pizza.jake.fun",
  "profile.rog.ie",
  "social.daverupert.com",
  "social.andy-bell.co.uk"
]

Threads / Replies

This is very much WIP, but here's a proposal for threads and replies.

It is important that you host your stream at a location that wont change, that way your friends can easily find you and communicate with you.

Your stream has one message and it looks like this, hosted at social.yourwebsite.com:

[
  {
    "text": "a pure text post",
    "time": 1650938164497
  }
]

You could thread to that status using the following syntax:

[
  {
    "text": "@social.yourwebsite.com#1650938164497 this one is a reply",
    "time": 1650938694864
  },
  {
    "text": "a pure text post",
    "time": 1650938164497
  }
]

The format is @ + domain + # + time. This way a reader can find the post an link to it, visualize the thread however it wants. You can use this to reply to another stream's thread as well, since the domain is the unique identifier for each stream.

[
  {
    "text": "@stream.anotherwebsite.com#1650933416323 hiya, pal!",
    "time": 1650938695555
  },
  {
    "text": "@social.yourwebsite.com#1650938164497 this one is a reply",
    "time": 1650938694864
  },
  {
    "text": "a pure text post",
    "time": 1650938164497
  }
]

Readers

A reader will only read the streams it is subscribed to following the formats it expects. That means if you want to read your own streams, you'll have to make one until someone makes a tool that makes this easier. I created an unstyled example on CodePen if you want to do it that way, or checkout the buddy.pizza source code.