bitwave-tv / bitwave Goto Github PK

View counter on each streamer's profile page

Allow streamers to create polls in chat

With the current live notification API, users can get multiple live notifications if a streamer drops out.

Solution:
Throttle notifications by specifying a cool down period after user goes offline

Add pagination to streamers page to improve load time.

Optionally make it auto paginate based on scrolling.

Create a dedicated component for displaying messages related to chat loading / reconnecting / errors.

Store bumps in database to make it easier to add / remove / update bumps. Optionally at a later date we could use this to link stream profiles with custom bump lists to allow users to specify offline bumps that they choose.

Sign in dialog may require a captcha to be added in case of multiple failed password entry attempts.

May also consider utilizing on demand CAPTCHA escalation as a feature that can be enabled if / when it's needed to reduce a DDoS or targeted spam attack. (e.g. add code to client / server in disabled state, but linked to a server side feature flag that allows us to enable / disable dynamically).

Create UI components for displaying & managing archives.

Add a key combo to blur the video in case things get too spicy on stream.

Cancel setTimeout of second autoscroll on new message to attempt to prevent 'jumping' down.

Consider adding option to disable smooth scroll

Breakout the stream card to it's own component to simplify code.

/chat pages still use outdated toolbar instead of app-bar.

'app' has been removed, use '<v-app-bar app>' instead.

Add timestamps to notifications

Add a local / global indicator badge to users to help users distinguish whether users are in local or global chat.

Let users modify and update Stream Title, description, and NSFW/SFW status, directly from user page.

Allow users to change their own profile photo

If API server is unavailable during SSR then errors are thrown. We should properly handle errors so that we don't crash if the API server fails.

This issue also means that running a Dev server on an offline machine causes a crash.

Create OBS overlay specific page.

Basic Features:

• Automatic transparent background
• Account synchronized via unique token
• Synchronize username (show @ tags in overlay) & ignore list
• Allow setting global / local (hide labels in local)
• Allow showing / hiding trolls
• Do not show input or top bar

Advanced Features

• Compact mode (hide avatars)
• Emote toggle
• Clear command

Polls don't work anymore.

Add toggle to user profiles for enabling or disabling archives.

Autosuggest username when @'ing people

A place to post stream quotes (optionally with a sound byte).

Crowd sourced soundboard basically

On mobile, the follow button is directly under the send message button. These should be further apart.

Add a dropdown hint for emotes in chat

Allow users to watch multiple streams at once

Add option to chat to allow hiding avatars and making messages appear inline with usernames so that more chats can be viewed.

Try to figure out a better way to at users in chat. At the minimum, we should try to prevent multi-tagging a user when lagging

When copying the streamkey, if the key is hidden it will copy the mouse event instead of the actual key value.

We should always explicitly pass the value to the copyToClipboard function to prevent this corner case.

By opening multiple tabs of a stream while not following a streamer, users can artificially inflate follower counts by following a streamer on each tab

Streams will not play on any browser I try to use which includes Safari, Chrome, Firefox, Beaker and others when I am using my VPN. I get the message "The media could not be loaded, either because the server or network failed or because the format is not supported." regardless of the stream I choose.

Load livestreams via asyncData in index page, then pass results to stream-grid component while waiting for database socket to connect to improve load response and take advantage of SSR.

Allow users to filter out offline / NSFW streamers

Allow users to change their own password & e-mail address.

This is more of a bitwave-media-server issues foremost, but improve the method of kicking / banning a stream such that is

1. More stable. Lost processes mean entire server reboots are required to remove a stream
2. More robust. Kicked streams need to have stream keys reset in order to prevent immediate re-connections. Banned streams need to have ban flags set in their profile ( temp duration / perm )
3. More convenient. Having to pull up postman to send API requests to multiple endpoints to kill a stream is time consuming, confusing, and error prone. Especially when dealing with lost processes.

Mitigate issues by at the minimum marking the stream as offline and modifying the endpoints to a bumper in order to force clients to drop the stream immediately (maybe a designated banned / kicked bumper?)

Immediately flag account as kicked / temp banned / banned. Change or remove stream key.

Prevent user from acquiring additional stream key(s) if possible.

Integrate into either an admin control panel or directly on page - lazy-loaded and injected into pages if an admin account is detected.

Create page or component that is capable or showing stream Stream Errors, Stream Data, and other streamer analytics (similar to YouTube dashboard).

Remove and (optionally) re-render non 16:9 bumps as they overflow the video container and break page layout.

Stream.me style raffles

Allow users to choose what bump plays when they are offline.

Create automated form for requesting and approving streamkeys

Allow users to hop channels by clicking on channels in user list drop down

Update UI framework to latest version.

Upgrade Guide: https://github.com/vuetifyjs/vuetify/releases/tag/v2.0.0-beta.0

Currently chat commands use a mix of /command and !code combinations and are mixed case sensitive / insensitive. We should work to unify chat commands to 1 use pattern.

• Allow mobile chat to autoscroll.
• Hide Jump to bottom button by default
• Make scroll to bottom button appear only when chat is scrolled up. past threshhold;
• Animate fly in / out of scroll to bottom button.

I'm using ffmpeg and I'm seeing the stream fall behind as if it's publishing faster than the framerate. These settings worked fine on other platforms. It's be nice to have encoder examples to help with such issues.

Ability to send a private direct message to other bitwave users