Current

This package is used to create and update personal websites on IPNS. When publishing a new article, it creates a separate directory with HTML, JS, CSS, and media files, attaches it to the IPNS directory, and updates the RSS feed, JSON feed, and index.html.

New feature requested

• Able to store ActivityPub data: JSON files of ActivityPub are stored in the same IPNS directory, alongside HTML, RSS, and JSON feed.
• Render article comments: The HTML web app can retrieve ActivityPub data from relative paths and render article comments.
• It should be able to accept an IPNS key pair and create or update the corresponding IPNS record
• It should be able to be used with local or remote IPFS nodes, likely by accepting the address of the IPFS.

The final API could be:

f(Activity: any, IPFSNodeAddress: string, IPNSKeyPair: any, NewDirectory: bool) ->  UpdatedIPNSRecord: string

Related work

ActivityPub integration by Distributed Press: hyphacoop/distributed-press-organizing#80 It would be ideal if both features/modules share the same API.

Description

• APIs of thematters/ipns-site-generator and thematters/matters-server to support ActivityPub;
• IPFS/IPNS infrastructure

Epic

• thematters/developer-resource#273

Implementation

TODO

Checklist

• Revise matters.news -> matters.town;
• Bump version & publish npm package;
• Update to matters-server;

During assembling html bundle, image and audio assets are downloaded and included in bundle. For security and cost, there should be a check on file size or domain.

via IPNS entry to each article is no problem is link back to top IPNS entry,

1. https://cloudflare-ipfs.com/ipns/k51qzi5uqu5dh119p9my3wre5ul8unkpakjwop3hwbn30eydajby9hkbb0l9gh/
2. https://cloudflare-ipfs.com/ipns/k51qzi5uqu5dh119p9my3wre5ul8unkpakjwop3hwbn30eydajby9hkbb0l9gh/{id}-{slug}/

but if via each single article's IPFS Dialog entry:
https://ipfs.filebase.io/ipfs/QmcZwZLrZbp6YiHSpDJUSfF4kUdk4zCZCrFEExWJSMC5Pv/

the top links are not linking back:

References:

1. https://github.com/ned14/static-website-activitypub
2. https://jasonrbriggs.com/journal/2023/05/08/activitypub-on-a-static-site.html
3. https://paul.kinlan.me/adding-activity-pub-to-your-static-site/
4. https://socialhub.activitypub.rocks/t/static-file-activitypub/2785
5. https://github.com/RangerMauve/staticpub.mauve.moe/

We need to add an analytic script to HTML files on IPFS in order to know the page views.

• Analytics script should be injected to head in the HTML template
• Analytics script should be loaded from https://static.matters.news/analytics.js. Currently, it's an obsolete script using segment, we should update it to firebase.
  • Firebase Doc can be found here. Note that it uses event screen_view, but we might want to use page_view for consistency with matters.news
  • The analytic script is stored in AWS S3 bucket matters-public-files and mapped to https://static.matters.news already. The updated script should be uploaded here and tested on firebase console to see if it works.
  • Then bump the version, and CI will publish a new version of the package.
  • Finally update the version number of this package on matters server.

Tasks

• Correct time parameter passing to IPFS generator. It seems like passing date instead of timestamp

References

• Thread discussion

Describe the bug
two tests throw Timeout - Async callback was not invoked within the 5000 ms timeout specified by jest.setTimeout.Timeout - Async callback was not invoked within the 5000 ms timeout specified by jest.setTimeout.Error

To Reproduce
Steps to reproduce the behavior:

1. git clone this repo
2. cd to root dir and run npm ci or npm i
3. run npm run test
4. See error

Expected behavior
test pass without errors

Screenshots
npm run test :

Desktop (please complete the following information):

• node: v16.16.0
• npm: 8.11.0
• git revision: 9242e4c

Additional context

I tried upgrading jest family to v28, but tests still failed with same errors after work out other problems brought by upgrade

To avoid unnecessary changes to codebase, we'll keep most of publishing flow the same but revise content published to IPFS for Circle article:

• Summarize post content and publish it to IPFS
• Put the Circle page link at the end of the content

TBD:
IPFS content format with link to circle.

Description

TODO

Epic

• thematters/developer-resource#273

Implementation

• #152

https://www.notion.so/matterslab/Publish-content-feed-to-IPNS-from-Matters-server-e294ee05fc76479c893dd6c24370caaf

[discussion] can be modified from ‣(renamed as matters-content-store?)