• We want to be able to filter posts that are posted from same site

  • These should be determined by the site that it is posted from
    • github.com links should be scoped by user: github.com/usirin/foo -> github.com/usirin
    • twitter.com links should be scoped by user: twitter.com/usirin/ -> twitter.com/usirin
    • all other links should be scoped by the top level url: umut.co/blog/foo/bar -> umut.co

• When users click to a site link that appears next to the post title, they should be directed to a list of posts that are posted from that site.

https://www.epicweb.dev/fully-typed-web-apps

we want to be able to share post links to "Twitter", "Reddit" and maybe "Whatsapp". It's because posts are easy to share, whatsapp could be a nice way to send post links to your friends as well.

expected behavior

brave behavior

• Brave Version 1.38.115

Since pano is open-source and welcome anyone who want to open pull request, it is better to standardize formatting in the project.

css loads later than html resulting in white screen initially

As a user

• I can create a new collection for posts.
• I can post new links to it
• I can add already created posts to it.
• I can see all the collections i created in my profile page
• I can discover new collections and start following them
• I can see a list of all the collections i am following on "my collections" page

Describe the bug

When we try to delete a post, if that post has comments, the delete button doesn't work

Browser(s)

Edge

Steps to reproduce the behavior

No response

Expected behavior

No response

Screenshot

• Brave Version 1.38.115
• Safari Version 15.4

Describe the bug

As can be seen from the video, after the dialog is opened and closed, other buttons on the interface cannot be interacted with.

https://www.youtube.com/watch?v=HSz5aNl0Nnw

Browser(s)

Edge

Steps to reproduce the behavior

No response

Expected behavior

No response

We want kampus members to be able to share links and have discussions for those links. Pano is a platform to solve this problem.

• can only post links
• add replies
• replies can have replies
• only publisher members can post links
• username/email/password
• predetermined set of tags
• a post can have many tags
• upvote

tech

• v0
  • amplify
  • gql
  • remix.run

• remix.run
• gql
• twirp services
  • post & comments
  • tags
  • users

Nonusers can access the page and send a request.

This problem causes the site to crash for everyone.

the /settings page (critical)

the /send page

link route is wrong
Sample;
when clicked this link https://csirin.com => going this https://pano.kamp.us/https://csirin.com

Meta tags are needed when we share posts to other websites

when you click to upvote button, it is getting smaller and disrupts the visual of the page.

Go over

• Pull request template
• issue template

• Most recent
• Most upvoted
  • Date range

we don't need apollo anymore because we don't make gql requests from client, so we don't need it's cache.

Replace all usages of apollo with SSR.API.graphql calls.

• my posts
• my collections
• my comments ?????
• social links ???

Handle this as same as we handle the empty body for post creation

When submitting the "password update form" we get the following error and it fails:

Auth.ts:1680 Uncaught (in promise) TypeError: user.getSession is not a function
    at Auth.ts:1680:9
    at new Promise (<anonymous>)
    at AuthClass2.userSession (Auth.ts:1678:10)
    at Auth.ts:1981:9
    at new Promise (<anonymous>)
    at AuthClass2.changePassword (Auth.ts:1980:10)
    at onSubmit (settings.tsx:120:18)
    at React3.createElement._extends2.onSubmit (components.js:704:19)
    at HTMLUnknownElement.callCallback2 (react-dom.development.js:4157:14)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:4206:16)

Title: Persist dark/light mode settings per user

Description:
We want to be able to persist the dark/light mode setting for each user in our web project. Currently, we have a users service that allows us to store user-specific settings, so we can use this to store the dark/light mode setting for each user.

To implement this, we will need to add a new field to the user's settings to store the dark/light mode preference. This preference should be saved whenever the user switches between dark and light mode in the application.

Once the preference is saved, we can use it to automatically apply the correct mode when the user logs in to the application.

Suggested Implementation:

1. Add a new field to the user's settings to store the dark/light mode preference (e.g. dark_mode_enabled).
2. Whenever the user switches between dark and light mode in the application, save the preference in the user's settings.
3. When the user logs in to the application, check their settings and apply the correct mode based on their preference.

Additional Considerations:

• We should also provide a way for the user to manually override the default mode if they want to use a different mode for a specific session.
• We should consider how to handle users who have not saved a preference, and whether we want to use a default mode for these users.

we need user friendly url support, add slug field to posts.

Write a proper CONTRIBUTING.md file for the monorepo.

• put everything from individual readme files to this file.
• add detailed instructions on how to manage monorepo things.
• add highlevel overview of how the repo is structured and how to contribute to packages and apps, and link to individual contribution guides if any.

In order to run an accessibility audit on our website, we need to follow the steps below:

• First, we need to identify any potential barriers to access on our website. This can be done by manually testing the website, using accessibility tools and checking for common accessibility issues.

• Once we have identified potential barriers to access, we need to prioritize them based on their impact on users. This will help us determine which issues need to be addressed first.

• Next, we need to develop a plan for addressing the identified accessibility issues. This may include implementing fixes, adding alternative methods of accessing content, and making other necessary changes.

• After implementing the necessary changes, we need to re-test the website to ensure that the accessibility issues have been resolved.

• Finally, we need to regularly monitor the website for any new accessibility issues, and continue to make improvements as needed.

By following these steps, we can ensure that our website is accessible to all users, regardless of their abilities.

Describe the bug

test

Reproducer

No response

React version

18.x

Language

TypeScript

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

screenshot

• safari -version 15.4
• [] brave

error messages need translations
more meaningful response messages
discord role based registration
deployment
logo

Describe the bug

As you can see, after the "test" comment is posted, it remains in the textarea.

I think there is a problem with state

Browser(s)

Chrome

Steps to reproduce the behavior

No response

Expected behavior

No response

Describe the bug

Background turns white when input autocomplete is done

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

Describe the bug

Reproducer

No response

React version

18.x

Language

ALL

Browser(s)

safari, brave, google chrome

Steps to reproduce the behavior

step 1

https://pano.kamp.us/posts enter address

step 2

Click on profile dropdown in topnav

Expected behavior

We need contributors to be able to run pano on their preferred dev environment and let them contribute that way.

current behaviour

https://remix.run/docs/en/v1/tutorials/jokes#seo-with-meta-tags

example:

export const meta: MetaFunction = ({
  data,
}: {
  data: LoaderData | undefined;
}) => {
  if (!data) {
    return {
      title: "No joke",
      description: "No joke found",
    };
  }
  return {
    title: `"${data.joke.name}" joke`,
    description: `Enjoy the "${data.joke.name}" joke and much more`,
  };
};