Currently the identity (key pair) is stored in local storage and can only be extracted from there or set there.

It would be nice however to have a way to do that in the GUI.

Currently only a text converter is implemented. It would be nice though if we could also publish images.

The first formats we want to support would be (jpg, png, webp)

Failed to compile.
ipsm/packages/web/src/App.tsx(33,7):
Type 'string' is not assignable to type 'CID'.  TS2322

    31 | 					{
    32 | 						mime: 'text/plain',
  > 33 | 						data: message,
       | 						^
    34 | 					},
    35 | 				],
    36 | 			})

Any idea? I did a yarn install and then a yarn web with ipfs running.

Currently the app will always try to connect to ipfs on the default localhost address. But since this does not match every setup, it should be configurable through the ui.

Supporting a PubSub topic format like this:

/ipsm/$PKHash/inbox

would allow direct messages between users. The $PKHash would be the hash of the PublicKey of the recipient. Message would be asymmetric encrypted using the PublicKey of the recipient to, so that only the recipient can read the message, if it's intended to be private.

Recipients can of course configure their system to only accept messages from their "Allowed Keys" list if they want, and of course there can be a list of keys each user maintains as "Blocked Keys" well, which always get ignored. But the Allows/Blocked keys is independent of this inbox concept, and would apply to all PubSub 'reads'

Originally posted by @Clay-Ferguson in #12

Currently everything in this is app english only. If we want a wider adoption, having the app available in your native language will help.

I've previously used mady as a translation editor and i18next to use those translations.

are you dogfooding a discussion on this project?

i thought i would give this project a look but im not sure i grok the need for an npm user account during the build.

/home/jim/.nvm/versions/node/v16.10.0/bin/node /home/jim/.nvm/versions/node/v16.10.0/lib/node_modules/yarn/bin/yarn.js run install
yarn run v1.22.11
warning ../../package.json: No license field
$ lerna bootstrap
lerna notice cli v4.0.0
lerna info Bootstrapping 4 packages
lerna info Installing external dependencies
lerna ERR! npm install exited 1 in '@undyingwraith/ipsm-client'
lerna ERR! npm install stderr:
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/ipfs-utils/node_modules/native-fetch
npm WARN native-fetch@"^3.0.0" from [email protected]
npm WARN node_modules/ipfs-utils
npm WARN ipfs-utils@"^9.0.2" from [email protected]
npm WARN node_modules/ipfs-http-client
npm WARN 1 more (ipfs-core-utils)
npm WARN
npm WARN Could not resolve dependency:
npm WARN native-fetch@"^3.0.0" from [email protected]
npm WARN node_modules/ipfs-utils
npm WARN ipfs-utils@"^9.0.2" from [email protected]
npm WARN node_modules/ipfs-http-client
npm WARN 1 more (ipfs-core-utils)
npm ERR! code E401
npm ERR! Incorrect or missing password.
npm ERR! If you were trying to login, change your password, create an
npm ERR! authentication token or enable two-factor authentication then
npm ERR! that means you likely typed your password in incorrectly.
npm ERR! Please try again, or recover your password at:
npm ERR! https://www.npmjs.com/forgot
npm ERR!
npm ERR! If you were doing some other operation then your saved credentials are
npm ERR! probably out of date. To correct this please try logging in again with:
npm ERR! npm login

npm ERR! A complete log of this run can be found in:
npm ERR! /home/jim/.npm/_logs/2021-10-02T18_42_31_723Z-debug.log
lerna ERR! npm install exited 1 in '@undyingwraith/ipsm-client'
lerna WARN complete Waiting for 2 child processes to exit. CTRL-C to exit immediately.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Process finished with exit code 1
attached

2021-10-02T18_42_31_723Z-debug.log

Currently all posts are stored on the ipfs mfs in a folder per board. But they do not get read from there in the correct order.