onur-ozkan / feednext Goto Github PK

Get rid of the CH words from client side

Create a documentation including following informations

• Running project on local
• API endpoints
• Project Structure
• Todo list
• Contributing to project

Frontend framework will be transform to NextJS.

The problems that caused to this refactorization:

• There is a huge documentation problems with Umi. Almost all official documentations are Chinese.
• %90 of the issues are Chinese and English ones does not get response in time. And responses are does not fix the issues really.
• Not enough contributors. Available ones are not experienced as expected.

User session expires in less than 60 seconds.

This message seems to come from antd -
User session has been expired, please Sign in again

createError file:/C:/site/client/.next/static/development/pages/auth/sign-in.js (58034:15) handleAbort /_next/static/development/pages/auth/sign-in.js (57515:14)

Create components and pages that can use backend functionalities

Timeout the connections that take longer time than usual via Nginx.

Categories that will be on the production

• Electronic
• Games & Game Consoles
• Appliances
• Baby
• Vehicles
• Books
• Musics & Songs
• Pet Supplies
• Musical Instruments
• Fashion
• Sports & Outdoors
• Industrial & Scientific
• Automotive
• Collectibles & Fine Art
• Home, Life & Furniture
• Patio, Lawn & Garden
• Arts, Crafts & Sewing
• Beverage & Food
• Health & Household
• Beauty & Cosmetics

There are still some class components exists on client side, refactor them to FC.

I got this error when running npm run start:dev. I already install via npm ci.

I use node v12.22.12

Create an algorithm that automatically upgrades(up to Mid Level Author) the user role based on the user's statistics.

Get rid of type errors on frontend, so we can use "npm build" command with CI services.

https://github.com/ozkanonur/feednext/blob/100aafd62c000777f19b3fd2d3f23c7328f62081/.docker/nginx/prod/app.conf#L18

Filter the exceptions by which ones will report to the Sentry.

• Refactor password hashing algorithm with using argon2 in Users Entity
• Hash recovery_key in Users Entity
• Optimize types in redis service

Use tag system instead of category

In case of overload, put the jobs that overloads the server's power into queue mechanism via RabbitMQ.

Push error logs into some accessable channel services such as slack or discord

Create an algorithm to calculate user's reliability score and provide it on client-side user page

Show existing feeds that are similar to the creating one on New Feed page

Find workaround on routing issue of Umi for SSR.

When sign-in with 'rememberMe=true' on chromium based browsers, refresh token does not apply to cookies.

Encountered on Google Chrome, Chromium Web Browser

Add sort by popularity (by highest vote count to lowest one) feature on feed page.

Nginx proxy pass causes wss connection problem on production environment.

Create a component that pops on middle of the screen when user triggers click event on some buttons like voting, rating, etc..

When creating a new feed, rating the title must be mandatory as well as posting first entry.

Hey there,

I just skimmed through most of the code because I wanted to see if there was any inspiration for a project of mine.

I found the following points which might be interesting to you. Keep in mind that it was a very rough skim, so it's very possible i might have missed things.

• You are using JWTs for sessions (which I would not recommend) and using a Redis-backed blacklist for invalidated tokens. The Redis instance is (at least as far as I can tell) not started with correct persistence enabled. This means if Redis crashes all keys that got invalidated in the last 60 seconds are now valid again.
• Your types for Redis are set(key: string, value: any) when Redis can only handle value: string correctly
• Your rate limiting is setup to use in-memory storage, but you are running your processes clustered, so they don't share the same rate limit values. You should move that limit information into Redis, for example.
• You are hashing the password with sha256 which is vulnerable to a rainbow table attack. Please read this article on how to implement password storage safely.
• Your password length is limited to a max of 20 characters, when you should not limit it at all (or to something like 4k).
• You are saving password reset tokens as plaintext in the DB when they should be hashed

Run the backend functionalities by using client side