microfed 0.0.4 → 0.0.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +14 -14
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -20,11 +20,11 @@
20
20
  [![npm](https://img.shields.io/npm/dw/microfed.svg)](https://npmjs.com/package/microfed)
21
21
  [![Github Stars](https://img.shields.io/github/stars/micro-fed/microfed.org.svg)](https://github.com/micro-fed/microfed.org/)
22
22
 
23
- # Introduction
23
+ # ⚡️ Introduction
24
24
 
25
- Tthis project is still at concept stage and aims to brain storm the intersection of micro servcies and the fediverse
25
+ Tthis project is still at concept stage and aims to brain storm the intersection of [micro servcies](https://en.wikipedia.org/wiki/Microservices) and the [fediverse](https://en.wikipedia.org/wiki/Fediverse).
26
26
 
27
- The idea is that each component of a fediverse server can be composed from smaller services
27
+ The idea is that each component of a fediverse server can be composed from smaller services.
28
28
 
29
29
  These include:
30
30
  - [Profile](#Profile)
@@ -32,21 +32,21 @@ These include:
32
32
  - [Outbox](#Outbox)
33
33
  - [Authentication](#Authentication)
34
34
 
35
- # Profile
35
+ # ✍️ Profile
36
36
 
37
37
  Your profile page is the starting point for microfed services. It will generally be an HTTP page, but the data should be agnostic to HTTP or any other protocol so that it can live in a database, or run over a P2P network.
38
38
 
39
39
  The profile will be in HTML, with the data in in JSON(-LD). It will contain:
40
40
 
41
- - The profile page
42
- - The User / Actor / Agent
43
- - Attributes about the User
44
- - Ability to store a public key
45
- - A list of connections (friends, knows, followers etc.)
46
- - Endpoint for inbox
47
- - Endpoint for outbox
48
- - Authentictation endpoints
49
- - Arbitrary fields specified by the user
41
+   ✓ The profile page
42
+   ✓ The User / Actor / Agent
43
+   ✓ Attributes about the User
44
+   ✓ Ability to store a public key
45
+   ✓ A list of connections (friends, knows, followers etc.)
46
+   ✓ Endpoint for inbox
47
+   ✓ Endpoint for outbox
48
+   ✓ Authentictation endpoints
49
+   ✓ Arbitrary fields specified by the user
50
50
 
51
51
  The Profile can be self hosted, or part of a multi user service. It should be able to run on a mobile device, or in the browser.
52
52
 
@@ -62,6 +62,6 @@ The outbox is a service that allows messages to be sent to other inboxes. It sh
62
62
 
63
63
  Initially, strong authentication via PKI will be supported. Delegated authenticaiton, such as OAuth and OIDC may be considered desirable. A loosely coupled authentication suite will allow the user to add different authentication modules. This could also work with enterprise authentication.
64
64
 
65
- # License
65
+ # ⚖️ License
66
66
 
67
67
  - MIT
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "microfed",
3
- "version": "0.0.4",
3
+ "version": "0.0.5",
4
4
  "description": "microfed",
5
5
  "main": "index.js",
6
6
  "scripts": {