kotollc / peacenik Goto Github PK

Nodes are where messages and images are stored. Anyone who is friends with the node admin can join the node. After that, anyone who is friends of a friend can also join.

Please ask questions in Discourse if you are confused

This will only show me users who have a friend that I am friends with.

We will serve a JSON object representing people, friendships, and communities, which we can visualize in the browser (later). No user information will be shown.

If there's a pending friend request, it should show the 'schedule' material design icon.

Later this should trigger an invite email. For now it's all visual.

There should be an endpoint at a community to see:

Who tagged me.
Who responded to my messages
Who reaponded to things that I responded to.
Who responded to something I liked
Who liked one of my posts

All of these should have links to the posts / comments.

It looks like I can register two users with different emails but the same username. Your username should be unique, so that people can't pretend to be you.

We should return the poster's picture.

A button "+ Friend" on the list of friends.

These are coming from any node where I have friends.

I would like the following

1. Docker files for the following (note that the first 3 appear to be finished):

• Node servers (written in go): https://github.com/mreider/koto/blob/master/backend/node.md
• Central server (written in go): https://github.com/mreider/koto/blob/master/backend/central.md
• Minio for s3 testing
• Frontend (written in React TypeScript): https://github.com/mreider/koto/blob/master/frontend/readme.md
• Postgres database for central server
• Postgres database for node server

2. Docker compose for local testing with all the above.

3. Script or pipelinr that builds images when git release is tagged including:

• images for node serve, central server, and frontend
• pushing images to dockerhub with same release tag

4. Kubernetes deployment files for productiion deployments - all the above (except minio) including:

• Postgres databases have persistent storage
• All secrets for S3, SMTP, and Postgrs, etc. use K8s secrets
• Scripts for deploying using Kubectl
• References to release images

When I try to filter names, it is case sensitive.

If I tag a friend they will get an email message with a link to my message or comment.

Keep in mind that this should also work in public groups, in which case it will need a different endpoint - since the members will not be friends.

The list has:

• who the report is from
• date reported
• a link to the post / response
• who posted the message / response
• what the status of that person is (banned or not)

Registering a node should:

1. Create a file /registrations/disabled/{nodeid} with domain or IP, node ID, email, username, application text ("hi, I am just a normal person who wants to create a node")
2. If node ID is added to list /registrations/enabled/nodes then the site is enabled.

If a friend reports a post or comment, an email is sent to the admin, with a link to the post or comment.

If someone reject my friend request, I will nolonger see it as pending ( see this story: #45 )

So now I can invite them all over again and it will show up in the invitations list of my friend.

This takes a backend change @falconandy

An admin can suspend a user from a community so he can't see any messages or post anything there. He can also unsuspend them.

A user can download all their stuff in a .zip file.

Not the year. Just the month and day.

If I post something I can edit or delete the post.

An admin can make decisions about when to freeze his community by looking at the usage estimator which will show:

• number of messages total
• messages posted per day
• average gigabytes used per user
• gigabytes stored in s3
• Increase of gigabytes per week (%)
• cost estimate of s3 storage per month
• increase of storage costs per week (%)
• average number of emails sent per user
• increase of emails sent by user per week (%)
• cost estimate of sendgrid per month

If I don't want you to be a friend, I can make it impossible for you to see me on your friend's friend list. This means you can not send friend requests to me.

An admin can send an email to everyone that uses their community. This does not include banned users.

This will be stored in an S3 account.

Profile picture should be scaled to a thumbnail image if it's too large, or expanded to a size that @falconandy and @dimakrsna agree upon

I found this library. You can use others if you find them.

https://github.com/nfnt/resize

A community can be private or public. So far they are all public. But an admin can also make a private community.

Private communities are local, ans everyone is automatically friends from the start. Sort of like a message board.

You have to choose to post a message to a private community. It doesn't happen like public communities where the message can go anywhere.

Ask questions to make sure we get this right.

There should be a way to see:

• Average amount of $$ being spent on storage and mail by node unlocked nodes.
• Same number for locked nodes.
• How many additional unlocked nodes would bring $$ down to a target monthly cost ($30?)
• average growth of network (by new members) by month.
• rate of new nodes needed per month to keep up with network growth for target cost ($30).

We can make a "we need your help" page showing this information to recruit people to create nodes.

When I post a message, I can also send a picture or a video, which will be stored in the admins s3 account.

The image below was created with the following icons:

• Forum: https://material.io/resources/icons/?icon=forum&style=baseline
• People: https://material.io/resources/icons/?icon=people&style=baseline
• Notifications: https://material.io/resources/icons/?icon=notifications&style=baseline
• Account circle: https://material.io/resources/icons/?icon=account_circle&style=baseline
• DNS: https://material.io/resources/icons/?icon=dns&style=baseline

When an admin starts a new community, he is automatically added when he logs into the central server.

User profile is very simple. Just a photo, username, email. That's it.

Later we can try to delete all
Messages and things from the browser too.

An admin can create a rolling delete that will destroy messages and pictures / videos that are N days old.

I can reply to a message you posted.

The approve button is for ADMINS ONLY.

Also the list includes ALL the node requests from all users

@falconandy this requires a new endpoint to delete node qpplications (I am now calling them node requests).

Let's sort this list by date applied (most recent first). And the filter will only show ones that are not approved.

When I post a message, it will go to the community where I have most of my friends. Perhaps there is a count of friends returned so the React client can make a decision. (See comments - rethinking this)

I can send a friend an email without knowing their email address.

If you are my friend, I can click on your name and see all the messages you have posted

An admin can lock a community so that no new members can post anything. This means if I invite you to be friends, and an admin has locked a community, you get a message that says "it looks like this community won't allow new members to post messages. Usually this is to save on storage costs."

There are two parts to this page. Notice that these are only the nodes that I have / have requested. The admin story (49) sees everything. (sorry, forgot the submit button in the picture.

Please also buiild the Code of Conduct page, and I'll write the test later.

If I make a comment, I can edit or delete it.

When we are friends, I can see a list of your friends in the communities I am a part of already.

The recent activity stream will tell you if someone is having a birthday and suggest you post a happy birthday message.

The super user that set up the central server can add a community to a conf file, or somewhere, so that nobody can login to that community.