okunaorg / okuna-web Goto Github PK

Not hangs like out-of-memory but just shows an endless skeleton loading doing nothing.

Add the User Menu -> Lists modal window wth the same management style as the mobile version Menu -> Lists

When clicking on a hashtag, community or username, the modal persists while in the background the route changes. We need to close it when this happens. We can perhaps listen for route changes that are not in the current post route.

We should have basic reporting tools in place.

We should be able to click on a persons name or photo and go to otheir profile from the post comments

As Jakob suggested, the search tabs should stick to the top of the container.

Please make sure proposed solution works both on mobile and desktop search

When clicking a c/link or username mention, sometimes the page does not load.

Try to reproduce the bug and let's discuss your findings.

Add the User Menu -> following modal window wth the same overview style as the mobile version Menu -> following

Hi!

Currently, the dropdown menu (by the username) only works when you are at the very top of the timeline. I think it should work elsewhere:

It also seems that once the menu is active (if clicked) it "sticks" to the very top of the timeline, so when scrolling down it dissapears, maybe it should stick to whatever position the user is at?

Create a user menu, similar to the menu tab on the mobile version, as a dropdown on the top right.

I don't know if it's possible to use a main variable scss file, but after i stumbled over some css rules like

I asked myself if this value should come from a shared variable.
Or maybe they should use the same class since the use the exact same values.
I can understand that there can be reasons to use different classes, but if you change one of these values in the future you might wanna change the other one, too.

Add the User Menu -> followers modal window wth the same overview style as the mobile version Menu -> Followers

The now page should display both the Trending posts and Explore posts sections as the mobile page "search" page does.

Start by building the mobile resolution component. When building the web resolution component, reuse as much as possible from the mobile resolution component.

Please look at the OkPostPage to see how to manage the switchinig between the two resolutions screens.

https://github.com/OkunaOrg/okuna-web/tree/feature/user-dropdown-menu/pages/home/pages/post

For mobile:

Please try to reproduce as closely as possible as the mobile app but with buttons perhaps instead of tabs for switching views.

For desktop:

Please before starting, draw a sketch skeleton and share on the slack channel for feedback.

You can use as inspiration the early kickstarter prototypes

https://www.kickstarter.com/projects/1520156881/openbook-privacy-friendly-fun-and-honest-social-ne/description#prototype-slide-151796

We forgot about the hashtag page.

Create it and display an endless feed of posts retrieved using the hashtags api

We should be able to search for communities, hashtags and accounts.

It should probably be a generic component we can use both on desktop and mobile.

Right now it waits until it hits the bottom to start loading more posts, should be like in the mobile app where it starts loading once its some 2/4 the current height.

When scrolling out of a video view, it should stop playing.

When expanding a post with a video, it should also stop, and open the video on the expanded window where it left off. We can probably do this passing some parameter to the openPostTheatre call

Not all hashtags are recognized correctly.
Especially hashtags wird numbers and special characters.

I had a look at the HashtagMatcher, which is used by OkSmartText, but the regex just works fine for all hashtags.

It seems that the vue-text-highlight has a problem with numbers and special characters.

We need to add the same Manage profile settings that we have in the mobile app.

Start by building the mobile resolution component. When building the web resolution component, reuse as much as possible from the mobile resolution component.

Please look at the OkPostPage to see how to manage the switchinig between the two resolutions screens.

https://github.com/OkunaOrg/okuna-web/tree/feature/user-dropdown-menu/pages/home/pages/post

For mobile:

Please try to reproduce as closely as possible as the mobile app.

For desktop:

The /username page where we display the user profile together with its feed, we can use the early prototype as inspiration for the layout.

https://www.kickstarter.com/projects/1520156881/openbook-privacy-friendly-fun-and-honest-social-ne/description#prototype-slide-151796

Please before starting, draw a sketch skeleton and share on the slack channel for feedback.

Create a modal called OkWIP and display a message stating that the web version of Okuna is still in development and the functionality trying to be used has not yet being developed.

Add two images with links to the Apple and Playstore mobile version downloads.

We will call this modal whenever the user tries to click or do something that is not yet implemented.

Please create the modal in the same way we've created others. Using the ModalService and the OkModals component.

Add some skeletons for a better loading experience.

When the images height is longer than its width, the images get cropped.

Make sure the forgot password flow works.

Deploy the web-app to Okuna.io and move the other page to us.okuna.io

Just like in the mobile app, when we start with any of those characters, we should switch the tab to its corresponding thing.

The /c/:communityName page where we display everything displayed on the mobile app. We can use the early web prototype as inspiration for the layout.

Start by building the mobile resolution component. When building the web resolution component, reuse as much as possible from the mobile resolution component.

Please look at the OkPostPage to see how to manage the switchinig between the two resolutions screens.

https://github.com/OkunaOrg/okuna-web/tree/master/pages/home/pages/post

For mobile:

Please try to reproduce as closely as possible as the mobile app.

For desktop:

Please before starting, draw a sketch skeleton and share on the slack channel for feedback.

You can use as inspiration the early kickstarter prototypes

https://www.kickstarter.com/projects/1520156881/openbook-privacy-friendly-fun-and-honest-social-ne/description#prototype-slide-151796

We should show notifications realtime with a badge just as the mobile version

I was able to install the current okuna-web on my Google cloud. Since my okuna-api is also on this server, I added some lines to nuxt.config with host: "0.0.0.0", port: "8080". After npm run dev, the page starts to load, albeit very slowly, and later login gives an error. The error shown within npm run dev is

ERROR (node:6813) [DEP0097] DeprecationWarning: Using a domain property in MakeCallback is deprecated. Use the async_context variant of MakeCallback or the A syncResource class instead. (Use node --trace-deprecation ... to show where the warning was created)

I have tried connecting to my local api as well as the api.openbook.social via .env but both giving the same error.

@Komposten , @lifenautjoe

Add some link previews!

Restrict the max height of the post to the visibile screen

Add the possibility to register without an invite and instead contributing an amount to Okuna for signing up.

The notifications dropdown to be opened when tapping the notifications header.

Should match the mobile version with two tabs and scrollable functionality.

Create on the auth page the registration flow which the user should paste an invite in.

Add the same Community -> Manage settings as the mobile version.

I am getting a bunch of serializer related errors when trying to install dev and production build. Here is the screenshot:

Is this because the website is still under construction or something ?

A page where to display the communities, same as the mobile app communities tab.

Start by building the mobile resolution component. When building the web resolution component, reuse as much as possible from the mobile resolution component.

Please look at the OkPostPage to see how to manage the switchinig between the two resolutions screens.

https://github.com/OkunaOrg/okuna-web/tree/feature/user-dropdown-menu/pages/home/pages/post

For mobile:

Please try to reproduce as closely as possible as the mobile app.

For desktop:

Please before starting, draw a sketch skeleton and share on the slack channel for feedback.

You can use as inspiration the early kickstarter prototypes

https://www.kickstarter.com/projects/1520156881/openbook-privacy-friendly-fun-and-honest-social-ne/description#prototype-slide-151796

There should be a easy way to navigate to the search results with the keyboard. E.g. by pressing key down or up?
The only way I can navigate with the keyboard, is by pressing Shift+Tab if there are any search results, but its impossible for me to switch between the search categories.

I don't know if its a common behaviour, but maybe you could close the search result by clicking the escape key.

Add the User Menu -> Circles modal window wth the same management style as the mobile version Menu -> Circles

Steps to reproduce:

1. Open the post theatre by clicking on the comment button below a post.
2. Double-click outside the modal (on the semi-transparent background).

Add the User Menu -> Invites modal window with the same overview style as the mobile version Menu -> Invites

User´s bio links are not highlighted and are not displayed as links on the web.

Instead it just redirects to the permalink (/p/uuid).

We should be able to X an account where X is:

• Request to follow
• Follow
• Unfollow
• Connect
• Block
• Add to list

For our own account, perhaps no manage button at the beginning.

As reported by Jakob #35 a message "The field may not be blank" is displayed 3 times when a search is started with a leading blank.

In this case I would suggest that the search query be trimmed before calling the api.

On the post and comments actions, there should be an extra action on their actions window with "Copy link to post", "Copy link to commment" that copy the respectives links to the persons clipboard.

After leaving a comment we get a OkPostCommenter element validation error. There's probably some flag misconfigured somewhere.

We should be able to

Own content

• Delete a post

Moderated content

• Delete post
• Close a post
• Disable post comments