Datasets:

giseldo

/

neodataset

like 1

2020-06-23 15:59:33.652

Do not allow adding an image when editing a post.

### Summary: I have an existing post but when I edit it to add a graphic I get a brief indication of the scroll bar and the popup occasionally clears the screen but the image never appears in the post. I have tried it both as a jpeg and as a png. The problem is sporadic. I have uploaded a different image okay on its own but it would also not upload when I tried to add it to a post. ### Steps to reproduce: Go to my page and try it: https://www.minds.com/Jan_Strepanov/ ### Browser and OS Firefox 77.0.1 (64 bit) on Windows 10 reported by: @Jan_Strepanov

2020-05-19 19:02:48.864

Two or three posts instead of one

### Summary: I share once. But it appear twice or three times ### Steps to reproduce: I share once. But it appear twice or three times ### Browser and OS Firefox reported by: @Polska_chce_wyjsc_z_UE

2020-05-12 04:23:11.469

Fix local stack installer issues

TBD

2020-05-04 16:20:16.245

Bug Triage and Customer Support

Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.

2020-05-01 19:11:49.027

Captcha failures

### Summary: Trying to register but capcha will not accept correct input ### Steps to reproduce: 1. typing capcha characters in field 2. get red capcha failed message instead of WELCOME TO MINDS! ### Browser and OS Firefox OX 10 reported by: @

2020-04-24 13:20:31.217

Introduce the Severity labels and document their usage

- [ ] See gitlab severity tag definitions - [ ] Update the analytics yaml file so we have some graphs - [ ] use 'Severity::X' pattern. - [ ] Update documentation

2020-04-17 21:08:40.465

Bug Triage and Customer Support

Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.

2020-04-16 18:30:15.169

Include react native image picker library and enable cropping for Channel Banner

Use the same libraries as the avatar picker https://github.com/ivpusic/react-native-image-crop-picker Image picker for banners https://design.minds.com/hosted/mobile/michael/mobile%23-channel/#artboard5 (same as the avatar, but with different text) Cropper https://design.minds.com/hosted/mobile/michael/mobile%23-channel/#artboard6 - [ ] When the channel owner clicks on their banner (camera button) - [ ] Display the image picker Select a banner from the camera roll / image gallery - [ ] When the user selects and image allow them to crop and position the image - [ ] Back button should go back to channel page and not change the image / display the old banner - [ ] Save button should go back to channel page and change the image - [ ] Light mode and dark mode - [ ] e2e and unit tests https://design.minds.com/hosted/mobile/michael/mobile%23-channel/#artboard2

2020-04-16 18:26:50.763

Include react native image picker library and enable cropping for Channel Avatar

This image picker for react native supports cropping and a round circle for the avatar https://github.com/ivpusic/react-native-image-crop-picker Image picker https://design.minds.com/hosted/mobile/michael/mobile%23-channel/#artboard3 Cropper https://design.minds.com/hosted/mobile/michael/mobile%23-channel/#artboard4 - [ ] When the channel owner clicks on their profile picture (camera button) - [ ] Display the image picker Select an Avatar from the camera roll / image gallery - [ ] When the user selects and image allow them to crop and position the image - [ ] Back button should go back to channel page and not change the image / display the old avatar - [ ] Save button should go back to channel page and change the image - [ ] Light mode and dark mode - [ ] e2e and unit tests https://design.minds.com/hosted/mobile/michael/mobile%23-channel/#artboard2

2020-04-16 18:16:37.034

Include ReactNative effect for linear gradients

So we can achieve the parallax gradient (the disappearing text on the channel's description) We need to implement and test a react native library for linear gradients (@msantang78)'s suggestion https://design.minds.com/hosted/mobile/michael/mobile%23-channel/

2020-04-05 23:42:10.612

Bug Triage and Customer Support

Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.

2020-03-21 21:31:34.647

Bug Triage and Customer Support

Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.

2020-03-09 23:33:36.386

Bug Triage and Customer Support

Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.

2020-02-26 19:10:38.995

Bug Triage and Customer Support

Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.

2020-02-23 18:22:19.254

Sidebar chat for groups should be able to turn on/off

The Help and Support sidebar chat should be removed. Update these existing MRs and let's get them cleaned up. Might be easier to cherry-pick their commits and close them off https://gitlab.com/minds/front/-/merge_requests/420 https://gitlab.com/minds/front/-/merge_requests/117 There's a bunch of closed off MRs associated with this issue as well https://gitlab.com/minds/front/issues/418

2020-02-20 14:27:58.850

Minds installation fails at ElasticSearch 6.x+ step

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Minds local stack installation times out using Windows' WSL 2 ### Steps to reproduce - Join Windows Insider and enable WSL 2 - Install Docker for Windows with WSL 2 support - Try to install the stack with `minds install` - ElasticSearch 6.x+ step times out and fails ### Platform information Windows 10 Pro with Ubuntu 18 LTS running on WSL 2 mode ### What is the current *bug* behavior? Local stack installation fail at ElasticSearch provision step due to vm.max_map_count being too low for ES. ### What is the expected *correct* behavior? Local stack installation to succeed. ### Relevant logs and/or screenshots ``` Pulling elasticsearch (elasticsearch:6.6.2)... Creating minds_elasticsearch_1 ... done Operation timed out 6.6.2: Pulling from library/elasticsearch Digest: sha256:59dd45d05fe89cd713dfc20874c6298e1ec7eaf384e58410b677b9dead6986f1 Status: Downloaded newer image for elasticsearch:6.6.2 Provisioning elastic search Waiting for elastic search to come online... at makeError (D:\Minds\minds\local\node_modules\execa\lib\error.js:58:11) at handlePromise (D:\Minds\minds\local\node_modules\execa\index.js:114:26) at runMicrotasks (<anonymous>) at processTicksAndRejections (internal/process/task_queues.js:97:5) { shortMessage: 'Command failed with exit code 1: docker-compose -f docker-compose.yml -f docker-compose.with-phpspec.yml run elasticsearch-provisioner', command: 'docker-compose -f docker-compose.yml -f docker-compose.with-phpspec.yml run elasticsearch-provisioner', exitCode: 1, signal: undefined, signalDescription: undefined, stdout: '6.6.2: Pulling from library/elasticsearch\r\n' + 'Digest: sha256:59dd45d05fe89cd713dfc20874c6298e1ec7eaf384e58410b677b9dead6986f1\r\n' + 'Status: Downloaded newer image for elasticsearch:6.6.2\r\n' + 'Provisioning elastic search\n' + 'Waiting for elastic search to come online...', stderr: 'Pulling elasticsearch (elasticsearch:6.6.2)...\r\n' + 'Creating minds_elasticsearch_1 ... \r\r\n' + '\u001b[1A\u001b[2K\rCreating minds_elasticsearch_1 ... \u001b[32mdone\u001b[0m\r\u001b[1BOperation timed out', failed: true, timedOut: false, isCanceled: false, killed: false, context: [Object: null prototype] {} } ``` ### Possible fixes We need to detect if we're on a Linux environment (either standalone or via WSL 2) scenarios and ask the user to set vm. max_map_count=262144 in their sysctl.

2020-02-17 19:28:43.599

Email address registration failure

### Summary: on your website and on the Apple app, it would not accept my email address hzmd@me.com so I could not register. On the app I also tried hzmd@icloud.com without success ### Steps to reproduce: I tried it more than once ### Browser and OS iOs reported by: @

2020-02-13 11:32:36.189

Local stack tweaks and enhancements

- [x] "[...] include the minimum system requirements (ie. RAM, storage and number of CPU cores) for both MS Windows, MacOS and Linux / BSD kernel based operating systems to the requirements section" - [x] Suggestion to restart terminals on all platforms after adding the aliases. - [x] "[...] minor typo in the README.md. You have got "at leas" were I suspect that you mean "at least" (ie. "it uses at leas 2 CPUs")." - [x] Expand and update README - [x] Add an `eol=lf` entry to `containers/**` - [x] Mirror .gitattributes in front, engine and sockets repositories, since it's not cascading down to minds/minds. - [x] Find a more unified way to handle front and SSR - [x] Init scripts - [x] Warnings on wrong line endings and Windows issues ## Merge Requests - https://gitlab.com/minds/minds/-/merge_requests/175 - https://gitlab.com/minds/engine/-/merge_requests/466 - https://gitlab.com/minds/front/-/merge_requests/781 - https://gitlab.com/minds/sockets/-/merge_requests/3

2020-02-08 02:30:40.303

Bug Triage and Customer Support

Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.

2020-02-05 14:50:12.774

Make our stack work with SSR and HMR on linux in docker compose

Fix up the minds docker-compose so the installation runs on linux with ```docker-compose up -d nginx``` and have the front end build with SSR. - [x] Get the environment working in linux - [x] Get the front end building for developers with one command - [x] Get the dev stack running with SSR that recompiles the files that change - [ ] Have @brianhatchet test and verify the stack on Mac and windows

2020-02-03 04:45:25.300

About Us link

### Summary: link titled 'Minds IRL' leads to a dead website - ### Steps to reproduce: Go to homepage (new homepage) Click Minds IRL ### Browser and OS chrome reported by: @

2022-08-24 17:27:11.159

NIP-26 working prototype

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal <!--- Clearly outline the goal of the issue and why we are doing it ---> Have working prototype of NIP-26 ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> Now that we have achieved general consensus with Nostr devs on [NIP-26](https://github.com/nostr-protocol/nips/pull/28) we can temporarily disregard our former [Whitelist](https://gitlab.com/minds/minds/-/issues/3306) proposal for ingestion and build the initial implementation of NIP-26 (which is required for the MR to be accepted anyway). - Add section in Settings, under Account called Nostr - Subsections will be Add relay, Delegate key, Generate key - For the usecase of users with existing Nostr keypair, this section will have an input field for a token to establish the pairing of their key with the Minds delegated key - For the usecase of users without existing Nostr keypair, this section will have an option to generate and download or copy a new Nostr keypair similar to the setup field on branle - For the usecase of adding relays to post to, this section will enable users to add more like in other clients ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design <!--- Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged. ---> For the token input field, something like : https://www.figma.com/file/NKmR2WGnVeZ42KzHURbFeg/Nostr-Pages?node-id=0%3A1 For the Add relay section, something like:  For the new key generation, something like:    ## Personas <!--- Who does this user impact and why (optional) ---> ## Experiments <!--- Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined. ---> ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [x] A settings (GUI) console where users can pair their keys - [x] Minds to sign events with the new delegate keypair - [ ] Integration tests ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-08-18 11:49:54.053

Boost console: Activity posts do not appear for rejected Boosts

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary The Boost console shows a history of Boosts and their status. Completed Boosts show the activity post that was boosted. However, Boosts that are rejected/cancelled do not show the activity post. ### Steps to reproduce - Make a Boost - Get rejected (e.g. due to backlog overflow) - View the Boost console ### Platform information - Web app ### What is the current *bug* behavior? - Activity posts do not appear for rejected Boosts ### What is the expected *correct* behavior? - Activity posts appear for all Boosts, regardless of status ### Relevant logs and/or screenshots   Relevant minds post: https://www.minds.com/newsfeed/1406297118418669571 ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-08-18 08:31:50.351

Discover Groups button does not work

### Summary Clicking Discover Groups button does nothing  ### Steps to reproduce 1. Use channel that does not belong into any groups (Not a must) 2. Navigate here: `https://www.minds.com/groups/memberships` 3. Click Discover Groups button on the top 4. Notice nothing happens 5. Hover over Discover Groups button 6. See that the link produced is: `https://www.minds.com/groups/memberships/'/discovery/suggestions/group` 7. The link that is part of the text works properly ### Platform information Brave & Chrome, Win10 ### What is the current *bug* behavior? Discover Groups button does not work ### What is the expected *correct* behavior? Discover Groups button should work ### Relevant logs and/or screenshots (Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.) ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-08-17 15:11:07.653

V2 activities: Videos do not autoplay in feeds / single activity view

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary In V2 activities, native Minds videos do not autoplay when the user's settings have autoplay videos enabled. ### Steps to reproduce - Ensure your Video Autoplay setting is enabled (https://www.minds.com/settings/account/autoplay-videos) - Visit a channel page with native Minds videos (https://www.minds.com/timcastirl/) - Scroll the videos into frame ### Platform information - MacOS + Chrome ### What is the current *bug* behavior? - The native Minds videos do not autoplay - The native Minds videos require the user to click the play button to begin playing ### What is the expected *correct* behavior? - The native Minds videos should autoplay in a muted state when scrolled into view ### Relevant logs and/or screenshots (Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.) ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-08-09 11:13:56.437

Login crash

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Login crashes, presumably with long usernames ### Steps to reproduce Try to login with `bentest123456789012345678901234567890123456789012` (Any password will do) ### Platform information Web ### What is the current *bug* behavior? Too much recursion error ### What is the expected *correct* behavior? Should allow login ### Relevant logs and/or screenshots  ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-08-05 22:14:58.921

YouTube sync double-posts when video is edited on YouTube

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary When a video is edited on YouTube, Minds YouTube sync creates a new activity post for the video. ### Steps to reproduce - Connect a Minds channel to a YouTube channel via YouTube sync - Publish a video on YouTube - (Minds will make an activity post linking to the YouTube video) - Edit the video (description, title, etc.) on YouTube ### Platform information n/a ### What is the current *bug* behavior? - Minds creates a duplicate activity post linking to the YouTube video ### What is the expected *correct* behavior? - No duplicate activity post is made ### Relevant logs and/or screenshots n/a ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-07-27 18:57:35.656

Implement new interest tags selector in onboarding

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Improve the UI of onboarding tag selection and synchronize tag selection UI across the app. ## What needs to be done Implement the new interest tags selector component into the onboarding flow, replacing the old tags selector. ## QA ... ## UX/Design This is the old selector being replaced:  This is the new selector interface, in the context of user content settings. For the onboarding context, we don't need / want the Compass tab.  ## Personas New users ## Experiments No experiment ## Acceptance Criteria - [x] During onboarding, the user is asked to select their interest tags. - [x] The old interest tags selection component is not presented. - [x] The new interest tags selection component IS presented. ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-07-26 22:23:39.466

Improve messaging for rejected boosts

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Ambiguous messaging in the Boost Console is creating confusion when boosts get refunded due to high volumes of boost orders.  ## What needs to be done Change the language displayed in the Boost Console, from: > Your boost was rejected: Onchain payment failed or High Boost backlog To: > Due to high boost backlog, your tokens have been auto-refunded. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design n/a ## Personas Core users who boost ## Experiments n/a ## Acceptance Criteria - [ ] Given a boost order is rejected due to high boost backlog, the message above is displayed in the boost console. ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-07-18 17:16:39.876

Spike: Create NIP for Delegated Event Signing

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal <!--- Clearly outline the goal of the issue and why we are doing it ---> Investigate how a Minds custodial Nostr public key can be paired to a user owned keypair. ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> This task is to investigate what is involved to achieve the goal above. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> N/A ## UX/Design <!--- Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged. ---> N/A ## Personas <!--- Who does this user impact and why (optional) ---> Nomads ## Experiments <!--- Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined. ---> N/A ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Further tasks and/or implementation plan ## Definition of Ready Checklist - [x] Definition Of Done (DoD) - [x] Acceptance criteria - [x] Weighted - [x] QA - [x] UX/Design - [x] Personas - [x] Experiments

2022-07-14 23:46:48.611

Implement in-feed notices in app (all)

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Synchronize in-feed notice communication experience between the web and mobile app. ## What needs to be done Implement in-feed notices in the mobile app using the backend logic endpoint developed for the web app. 1. Setup Channel 2. Verify Uniqueness 3. build-your-algorithm 3. Push Permissions 4. Update Tags ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design - [In-feed activity notice mobile](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=815%3A9478) ## Personas - New users ## Experiments No experiment ## Acceptance Criteria - [ ] In-feed notices appear in the app [when their conditions are met](https://docs.google.com/spreadsheets/d/1FHWiKdYobssgXQt8Cc6l3IyiFwjWnf2_jCc-ObHUsuM/edit?usp=sharing) - [ ] Only one in-feed notice appears in the feed at a time ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-07-14 23:30:13.947

Email verification in-feed notice

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Clearly communicate to users that they need to verify their email address, and make it easy for them to do so. ## What needs to be done Implement the `Verify your email address` in-feed notice on the mobile app. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design - [Figma mocks](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=815%3A9478) Screenshot for reference, see Figma mocks for latest spec.  ## Personas New users ## Experiments No experiment for this change specifically, but this change should be rolled out before experimenting with code-based email verifications (https://gitlab.com/minds/minds/-/issues/3296). ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Given a user has not already verified their email address, when they visit the Newsfeed, then the `Verify your email address` in-feed notice appears. - [ ] Given the `Verify your email address` in-feed notice appears, when the user clicks the `Re-send email` button, then a new email verification link is sent to the user's email address. ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-07-14 23:16:01.911

Code-based email verifications in mobile app

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Implement code-based email verifications in the mobile app and make the verification part of the initial onboarding flow, before a user reaches the Newsfeed. ## What needs to be done - Implement code-based email verification flow to the mobile app new user onboarding. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design - [Figma designs](https://www.figma.com/file/zKXef5Dyr3CiCEhTjALkzl/Mobile-Onboarding-Quirk?node-id=0%3A1) Screenshot for quick reference, see Figma mocks for latest spec.  ## Personas - New users ## Experiments Code-based verification should be tested versus existing link-based email verification, measuring for % of signups that result in email verification. ## Acceptance Criteria - [ ] Given a user is creating a new account in the app, and the user has already filled out the fields on `Join Minds` screen, and all fields are valid, when the user clicks the blue `Join Minds` button, then a code-based verification email is sent to the user's email address, and the user is navigated to the code-based `Verify Account` screen. - [ ] When the user is navigated to the code-based `Verify Account` screen, then the user's cursor is automatically positioned in the `Verification code` text field, and the keyboard defaults a numeric layout. - [ ] Given the user is on the code-based `Verify Account` screen, and the user inputs an invalid code, when the user taps `Verify` button, then the "Invalid code" error is displayed adjacent to the code field. - [ ] Given the user is on the code-based `Verify Account` screen, and the user inputs a VALID code, when the user taps `Verify` button, then the email address is verified and the user is navigated to the Newsfeed. ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-07-14 22:35:40.225

Top post push notification are undescriptive

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Occasionally, top post push notifications read: > @username posted These notifications are pretty vague and I think can be improved by always having a bit more context. ### Steps to reproduce - Enable notifications for `Top Posts` - Wait for a daily push top post push notification ### Platform information iOS, Mac + Chrome ### What is the current *bug* behavior? The push notification reads: > @username posted ### What is the expected *correct* behavior? Depending on the type of post that's being promoted, more context is expected. | Post type (sample) | Sample | Title | Message / Body | |----------------------------------|--------------------------------------------------------------------------------------------------------------|-----------------------------|---------------------------------------------------------| | Text post | https://www.minds.com/newsfeed/1351609905466839058 | Minds posted | Who are your favorite channels on Minds? | | Blog post | https://www.minds.com/minds/blog/minds-is-now-a-censorship-resistant-progressive-web-app-1363941884392640521 | Minds posted a blog | Minds Is Now A Censorship-Resistant Progressive Web App | | Media post (with title + body) | https://www.minds.com/newsfeed/1367998512221917203 | Bashynx posted an image | New survey dropped: About Multi-Image posting! | | Media post (with title, no body) | https://www.minds.com/newsfeed/1371197780126601227 | rogansent posted an image | A challenge | | Media post (no title, with body) | https://www.minds.com/newsfeed/1369805494683701250 | Ryan @ Minds posted a video | Silent Hill on water. | | Media post (no title, no body) | https://www.minds.com/newsfeed/1371198067109269511 | rogansent posted an image | | ### Relevant logs and/or screenshots  ### Possible fixes I initially thought this was happening when the top post was a media post without any text. But in the example screenshot above, it's from Babylon Bee and looking at their post history I don't see any posts without text. They are all posts with links, however -- which may be indicative of the cause. Let's assume this post was being sent as a top post push notification:  | Post type (sample) | Sample | Title | Message / Body | Launch URL / Link | |--------------------------------------------|----------------------------------------------------|-------------------------------|----------------------------------------|----------------------------------------------------| | Link (no title, no body) | https://www.minds.com/newsfeed/1394053308640923658 | The Babylon Bee posted a link | Big Tech Is Censoring Comedy... Again! | https://www.minds.com/newsfeed/1394053308640923658 | | Link (no title, no body, no text inported) | https://www.minds.com/newsfeed/1394053308640923658 | The Babylon Bee posted a link | | https://www.minds.com/newsfeed/1394053308640923658 |

2022-07-14 14:00:01.028

"Actions Taken" stats on content-policy page are not accurate

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary The `minds.com/content-policy` page has statistics for Actions Taken, Appeals, and Actions Overturned in the past 30 days. Currently, this reads "0" for all values. ### Steps to reproduce Visit https://minds.com/content-policy , scroll to bottom. ### Platform information Brave browser on Ubuntu ### What is the current *bug* behavior? Values show "0" ### What is the expected *correct* behavior? Values show actual actions taken, etc. ### Relevant logs and/or screenshots ### Possible fixes

2022-07-14 13:52:59.213

Fix Cassandra extract instability caused by lazy instantiation of SQLAlchemy `insert` operators

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary SQLAlchemy `insert` operators are lazy instantiated, which means that they may trigger exceptions not at the point of creation, but at the point of use. When placed into a worker queue, these delayed exceptions may kill worker threads. ### Steps to reproduce Create a SQLAlchemy `insert` operator with incompatible values argument. Place in worker queue. Worker triggers `sqlalchemy.exc.CompileError` exception, and exits. ### Platform information Data ETL ### What is the current *bug* behavior? ETL pipeline fails ### What is the expected *correct* behavior? ETL pipeline doesn't fail ### Relevant logs and/or screenshots ``` Unexpected error: CompileError('Unconsumed column names: tokenomics_version, multiplier, user_guid, reward_type, date, payout_tx, token_amount, score') Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/prefect/engine/runner.py", line 48, in inner new_state = method(self, state, *args, **kwargs) File "/usr/local/lib/python3.8/site-packages/prefect/engine/task_runner.py", line 865, in get_task_run_state value = prefect.utilities.executors.run_task_with_timeout( File "/usr/local/lib/python3.8/site-packages/prefect/utilities/executors.py", line 323, in run_task_with_timeout return task.run(*args, **kwargs) # type: ignore File "extract-cassandra-token-flow.py", line 191, in extract_all_tables logger.warn(queue.get()) File "/usr/local/lib/python3.8/logging/__init__.py", line 1463, in warn self.warning(msg, *args, **kwargs) File "/usr/local/lib/python3.8/logging/__init__.py", line 1458, in warning self._log(WARNING, msg, args, **kwargs) File "/usr/local/lib/python3.8/logging/__init__.py", line 1589, in _log self.handle(record) File "/usr/local/lib/python3.8/logging/__init__.py", line 1599, in handle self.callHandlers(record) File "/usr/local/lib/python3.8/logging/__init__.py", line 1661, in callHandlers hdlr.handle(record) File "/usr/local/lib/python3.8/logging/__init__.py", line 954, in handle self.emit(record) File "/usr/local/lib/python3.8/site-packages/prefect/utilities/logging.py", line 151, in emit msg = self.format(record) File "/usr/local/lib/python3.8/logging/__init__.py", line 929, in format return fmt.format(record) File "/usr/local/lib/python3.8/logging/__init__.py", line 668, in format record.message = record.getMessage() File "/usr/local/lib/python3.8/logging/__init__.py", line 371, in getMessage msg = str(self.msg) File "/usr/local/lib/python3.8/site-packages/sqlalchemy/sql/elements.py", line 562, in __str__ return str(self.compile()) File "/usr/local/lib/python3.8/site-packages/sqlalchemy/sql/elements.py", line 494, in compile return self._compiler(dialect, **kw) File "/usr/local/lib/python3.8/site-packages/sqlalchemy/sql/elements.py", line 558, in _compiler return dialect.statement_compiler(dialect, self, **kw) File "/usr/local/lib/python3.8/site-packages/sqlalchemy/sql/compiler.py", line 776, in __init__ Compiled.__init__(self, dialect, statement, **kwargs) File "/usr/local/lib/python3.8/site-packages/sqlalchemy/sql/compiler.py", line 451, in __init__ self.string = self.process(self.statement, **compile_kwargs) File "/usr/local/lib/python3.8/site-packages/sqlalchemy/sql/compiler.py", line 486, in process return obj._compiler_dispatch(self, **kwargs) File "/usr/local/lib/python3.8/site-packages/sqlalchemy/sql/visitors.py", line 82, in _compiler_dispatch return meth(self, **kw) File "/usr/local/lib/python3.8/site-packages/sqlalchemy/sql/compiler.py", line 3837, in visit_insert crud_params = crud._get_crud_params( File "/usr/local/lib/python3.8/site-packages/sqlalchemy/sql/crud.py", line 168, in _get_crud_params raise exc.CompileError( sqlalchemy.exc.CompileError: Unconsumed column names: tokenomics_version, multiplier, user_guid, reward_type, date, payout_tx, token_amount, score ``` ### Possible fixes Pre-instantiate arguments to `insert` operators before placing in queue.

2022-07-13 22:09:08.026

Boost inventory: Add boosts to Discovery

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Increase boost inventory. ## What needs to be done Add in-feed boost placements to the Discovery > Top feed, using the same spacing logic as used on the Newsfeed. Note: This does NOT include the Boost rotator. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No new design, the in-feed boosts should appear the same way they would on the Newsfeed. ## Personas Core users ## Experiments We should roll this out as an experiment to see if it negatively impacts engagement on the Discovery feed. ## Acceptance Criteria - [ ] In-feed boosts appear on the Discovery > Top feed with the same frequency as they appear on the Newsfeed - [ ] The boost rotator does not appear on Discovery > Top ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-07-11 18:22:31.562

Switch channel recommendations to Vitess

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal <!--- Clearly outline the goal of the issue and why we are doing it ---> Change 'friends of friends' ElasticSearch to be on Vitess ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> See above ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> Recommendations display. ## UX/Design <!--- Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged. ---> N/A ## Personas <!--- Who does this user impact and why (optional) ---> users ## Experiments <!--- Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined. ---> Yes ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Refactor elasticsearch 'friends of friends' logic to point to vitess - [ ] Add in experiment - [ ] Spec tests ## Definition of Ready Checklist - [x] Definition Of Done (DoD) - [x] Acceptance criteria - [x] Weighted - [x] QA - [x] UX/Design - [x] Personas - [x] Experiments

2022-07-08 10:33:42.544

Create page with links to tools to aide development

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Aide development and usage of SKALE tasks such as https://gitlab.com/minds/engine/-/issues/2349 ## What needs to be done Create docs page with info for development ## QA N/A ## UX/Design N/A ## Personas Developers of SKALE MINDS system ## Experiments N/A ## Acceptance Criteria - [ ] Docs pages - [ ] Blockexplorer - [ ] Usage examples - [ ] Explanations ## Definition of Ready Checklist - [X] Definition Of Done (DoD) - [X] Acceptance criteria - [X] Weighted - [X] QA - [X] UX/Design - [X] Personas - [X] Experiments

2022-07-07 14:14:28.618

Display a modal of mutual subscribers to be displayed when clicking 'other' on `m-channel__mutualSubscriptions`

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal <!--- Clearly outline the goal of the issue and why we are doing it ---> Now we have 'also subscribed to' blocks on channels, we want to expand to be able to see more than 2 results. ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> We already have a modal that displays for subscribes on notifications, this is just a time ordered list. Modify this modal to support mutual 'also subscribed to'. The backend needs a slight tweak to support pagination. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> The modal display when relevant. ## UX/Design <!--- Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged. ---> ? ## Personas <!--- Who does this user impact and why (optional) ---> Subscribers. ## Experiments <!--- Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined. ---> M/A ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Click on the component will launch a modal (same as what is currently used to display who up-voted a post) and list any mutual subscriptions, or redirect to a channel. * [ ] clicking directly on a channel handle will direct the user to that channel * [ ] clicking on `x others` or any of the avatars will launch a the modal. - [ ] Backend to support pagination. ie `LIMIT 12,20` in the SQL statement will offset to 20-32 results. ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-07-05 16:02:24.086

Show toast message before launching modal if email verification is required to complete modal actions

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Reduce UX clumsiness by warning user about email verification requirement before they try to do something that requires email verification. ## What needs to be done Throw a toast message instead of opening a modal, if the modal action requires email verification. Examples: - [Verifying phone number](https://gitlab.com/minds/front/-/issues/5568) - [Creating an activity post](https://gitlab.com/minds/engine/-/issues/2209) ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design Message: > You must confirm your email address ## Personas - New users ## Experiments None ## Acceptance Criteria - Given a user hasn't verified their email address, - when the user clicks something that generates a modal, - and that modal's action requires email verification, - then prevent the modal from displaying, - and throw a toast message that indicates that email verification is required. ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-07-01 03:56:26.079

Notifications feed jumps when closing image overlay

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary When on the notifications screen and viewing an image in an overlay view, when closing the image overlay, the notifications feed jumps. ### Steps to reproduce - Navigate to the notifications feed - Scroll the notifications until the app has to load more in - Scroll down to a notification that includes an image - Double-tap the image to view the image in an overlay - Swipe the image to close it ### Platform information - iPhone 12 Mini w/ latest Testflight build ### What is the current *bug* behavior? - The image is dismissed - The feed jumps and the user loses their position ### What is the expected *correct* behavior? - The image is dismissed - The feed scroll position is unchanged ### Relevant logs and/or screenshots  ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-06-30 21:25:38.421

Activities v2: Boost rotator improvements

## Goal Address the following UX concerns with respect the Boost Rotator in the context of the new activity post designs. 1. The social interactions at the bottom of the rotator get pushed outside the confines of the boost rotator when posts are lengthy. 2. The presentation of the post content within the boost rotator is oftentimes poorly presented. 3. The navigation controls (more left/right) are perceived to be lost/unclear ## What needs to be done - [ ] Address the above three issues as indicated in the UX/Design heading ### Other bugs that should be research / resolved as part of this issue MAKE NEW TASKS PLEASE - [ ] The rotator shows horizontal scroll bars for quote posts - [ ] Videos don't autoplay within the boost rotator - [ ] When just a youtube link is contained within the post, the video embed does not appear. Just the link is displayed. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design 1. [New Boost Rotator Header](https://www.figma.com/file/oYPYya9Z4G5wqgLvdKDbOB/Activity-Post-revised-%5BWeb%5D?node-id=707%3A3838) * Larger clearer boost rotator header with its own BG colour. * Larger nav controls moved to the RHS 2. [Social Interactions](https://www.figma.com/file/oYPYya9Z4G5wqgLvdKDbOB/Activity-Post-revised-%5BWeb%5D?node-id=818%3A3769) * Social interaction should remain in a fixed position at the bottom on the boost rotator. * The length height of the boosted post should not impact upon the position of the social interactions. * Where content overruns a slight gradient fadeout appears as indicated in the above design link. * Clicking `See More` will navigate the user to the post page 3. [Revised content positioning](https://www.figma.com/file/oYPYya9Z4G5wqgLvdKDbOB/Activity-Post-revised-%5BWeb%5D?node-id=808%3A3662) * Content should be positioned in the middle of the available area between the post header and social interactions. * Where there is text with an embed (URL, Image, Video) the [associated text should sit alongside the embed](https://www.figma.com/file/oYPYya9Z4G5wqgLvdKDbOB/Activity-Post-revised-%5BWeb%5D?node-id=808%3A3725). * See below numerous design examples which should clarify this. * [Text and image not overflowing](https://www.figma.com/file/oYPYya9Z4G5wqgLvdKDbOB/Activity-Post-revised-%5BWeb%5D?node-id=707%3A3838) * [Text and image overflowing](https://www.figma.com/file/oYPYya9Z4G5wqgLvdKDbOB/Activity-Post-revised-%5BWeb%5D?node-id=818%3A3769) * [Short text](https://www.figma.com/file/oYPYya9Z4G5wqgLvdKDbOB/Activity-Post-revised-%5BWeb%5D?node-id=818%3A3808) * [Text and large URL embed](https://www.figma.com/file/oYPYya9Z4G5wqgLvdKDbOB/Activity-Post-revised-%5BWeb%5D?node-id=818%3A3846) * [Text and small URL embed](https://www.figma.com/file/oYPYya9Z4G5wqgLvdKDbOB/Activity-Post-revised-%5BWeb%5D?node-id=818%3A3890) * [Quote Post](https://www.figma.com/file/oYPYya9Z4G5wqgLvdKDbOB/Activity-Post-revised-%5BWeb%5D?node-id=818%3A3934) ## Personas <!--- Who does this user impact and why (optional) ---> ## Experiments <!--- Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined. ---> ## Acceptance Criteria - [ ] Social interactions should never be positioned out of place - [ ] The positioning of the boosted content should conform with the designs indicated above. - [ ] Boosted videos should autoplay - [ ] Resolve horizontal scroll bar issue for quite posts ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments <details><summary>Original Issue by @markryansallee </summary> ### Summary <!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Cleaning up a few issues with the v2 Boost rotator to unblock the production experiment of Activities v2. ## What needs to be done Issues with Boosts blocking the launch of the experiment: - Visual of the "Boosted Post" label + arrow button controls at the top of the rotator - The rotator doesn't deal well with boosted posts that are very tall. Some screenshots below as examples. - The rotator shows horizontal scroll bars for quote posts - Videos don't autoplay ### Steps to reproduce (How one can reproduce the issue - this is very important) ### Platform information - Windows + Chrome - MacOS + Chrome ### What is the current *bug* behavior? (What actually happens) ### What is the expected *correct* behavior? (What you should see instead) ### Relevant logs and/or screenshots <details><summary>Examples of tall posts getting cut off</summary>  - Bottom of the engagement bar is cut off.   - Media is cut off, no engagement bar appears </details> </details>

2022-06-28 15:17:14.837

(bug) Verify your email address emails broken on Hotmail and Outlook

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Emails prompting users to verify their email are broken in outlook and hotmail, like so:  and it points to `https://` link ### Steps to reproduce 1. Create account or request verify email 2. Look at the email in outlook or hotmail ### Platform information Tested on: - Thunderbird 91.10.0 (64-bit) - Microsoft® Outlook® for Microsoft 365 MSO (Version 2205 Build 16.0.15225.20278) 64-bit ### What is the current *bug* behavior? (What actually happens) ### What is the expected *correct* behavior? (What you should see instead) ### Relevant logs and/or screenshots (Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.) ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-06-23 18:37:26.754

Minds videos don't load when embedded

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Minds videos embedded on Corbett Report website do not load / are not playable. ### Steps to reproduce - Log out of Minds - [Visit this page on Corbett Report website](https://www.corbettreport.com/category/videos/page/4/). - Scroll the page to see posts with video embeds. - Observe the posts with Minds videos embedded: - Episode 415 - The Global Digital ID Prison - Interview 1708 – New World Next Week with James Evan Pilato - The Future of Censorship (video) - Try to play the video ---- - Log into Minds - [Visit this page on Corbett Report website](https://www.corbettreport.com/category/videos/page/4/). - Scroll the page to see posts with video embeds. - Observe the posts with Minds videos embedded: - Episode 415 - The Global Digital ID Prison - Interview 1708 – New World Next Week with James Evan Pilato - The Future of Censorship (video) - Try to play the video ### Platform information MacOS + Chrome ### What is the current *bug* behavior? While logged out of Minds: The video frame is not loaded in completely (it looks mostly blank, aside from the title). The video is not playable. --- While logged into Minds: The video frame loads in the Minds UI (navigation, avatar, alert bar). ### What is the expected *correct* behavior? Whether logged in or logged out: The video embed should load entirely, including a thumbnail image and play button. Video is playable. ### Relevant logs and/or screenshots   ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-06-21 22:04:11.270

Add in-feed notices to Discovery feed

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Enable onboarding experiments with the Discovery > Top feed by bringing Newfeed features targeted at new users to the Discovery feed. ## What needs to be done Enable all in-feed notices to appear on the Discovery > Top feed, by the same logic with which they can currently appear on the Newsfeed. For reference, [this is the order in which activity posts are expected to appear](https://docs.google.com/spreadsheets/d/1FHWiKdYobssgXQt8Cc6l3IyiFwjWnf2_jCc-ObHUsuM/edit#gid=0) (same as Newsfeed). ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No Design ## Personas This change is targeted at new Minds users who are curious about the network and want to connect with people with similar interests. ## Experiments While this change is related to enabling experiments, it is not an experiment itself -- this can be rolled out to 100% of the audience. ## Acceptance Criteria - [ ] Given an in-feed notice appears on the Newsfeed, and I have not yet dismissed the notice or otherwise completed the criteria that dismiss it, when I visit the Discovery feed, then the same in-feed notice is presented in the same position. ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-06-21 22:00:08.125

Land newly-registered users on Discovery

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal We want to test a hypothesis for increasing short-term retention: Landing newly-registered users on Discovery feed will be more effective at (1) connecting users to channels with content they're interested in, and (2) as a result, increasing short-term retention. ## What needs to be done When a new user completes the registration process, land the user on the Discovery/Top feed instead of the Newsfeed. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No design. ## Personas This change is targeted at new Minds users who are curious about the network and want to connect with people with similar interests. ## Experiments This change should be implemented as an experiment, measuring: - % of new users who have followed a channel - Avg. # of channels followed by new users - Content engagement rate on a new user's first session - 3 day retention ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Given I've not already signed up for a Minds account, and I've started the signup process, when I complete the signup process by verifying my email address, then I am brought to the Discovery > Top feed, and the interests tag selector modal appears. ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-06-21 21:59:44.822

Update interest tag options presented during onboarding

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal (1) Increase the % of new users with interest tags relevant to their interests, (2) connect new users to channels creating content related to their interests, and (3) be able to analyze new user retention by differentiated interest segments. ## What needs to be done During onboarding, new users are presented a modal of interest tags to select from. That list includes (in order): - Art - Music - Myphoto - Photography - Crypto - Nature - Outdoors - Technology - Poetry - Travel - News - Journalism - Sports - Minds - Blockchain Update the list to include these tags instead (in order): - Animals - Anime - Art - Comedy - Crypto - Food - Freedom - Gaming - Literature - Memes - Movies - Music - Nature - NSFW - News - Outdoors - Photography - Politics - Religion - Sports - Technology - Travel ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No design ## Personas This change is targeted at new Minds users who are curious about the network and want to connect with people with similar interests. ## Experiments This change should be delivered as an experiment, measuring for impact on: - Avg. # of interest tags selected by new users - Content engagement rate on a new user's first session - 3 day retention ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [x] Change the tags - [x] Run as experiment - [x] Bonus if you can make configurable ## Definition of Ready Checklist - [x] Definition Of Done (DoD) - [x] Acceptance criteria - [x] Weighted - [x] QA - [x] UX/Design - [x] Personas - [x] Experiments

2022-06-20 07:42:20.306

(bug) Emails not arriving

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary When asking for password reset and verification emails, nothing arrives to the mailbox. 2FA emails work. ### Steps to reproduce #### Password reset 1. Go to incognito 2. ask to reset password on Minds login screen 3. Wait for email that will not come #### Verification email 1. Create a new account 2. Click re-send verification email 3. notice message on the bottom:  ### Platform information Win10, Brave ### What is the current *bug* behavior? Emails are not arriving, possibly because of rate limit? ### What is the expected *correct* behavior? Emails arriving in the outlined cases (password reset, verification) ### Relevant logs and/or screenshots (Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.) ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-06-17 09:19:12.770

Investigate Ruby Exchange https://ruby.exchange/

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Improve UX around token bridging ## What needs to be done Establish what would be needed for us to get ourselves on the Ruby IMA bridge https://ruby.exchange/ Explore the same for liquidity pool ## QA Test ruby bridge (actually already done this) ## UX/Design N/A ## Personas End users ## Experiments N/A ## Acceptance Criteria - [ ] Get a list of steps for listing ## Definition of Ready Checklist - [x] Definition Of Done (DoD) - [x] Acceptance criteria - [ ] Weighted - [x] QA - [x] UX/Design - [x] Personas - [x] Experiments

2022-06-17 09:01:46.623

Unable to login on minds.com/login page with 2FA: Second Attempt

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary The minds.com/login page throws an error (`Sorry, there was an error. Please try again.`) when logging in with an account that has app-based 2FA enabled. ### Steps to reproduce - Visit minds.com/login while not logged in. - Attempt to log in with an account that has app-based 2FA enabled. ### Platform information - MacOS + Chrome ### What is the current *bug* behavior? - After inputting username+password and submitting, an error message is displayed. ### What is the expected *correct* behavior? - After inputting user+password and submitted, a 2FA code input is displayed. ### Relevant logs and/or screenshots  ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-06-17 02:00:49.159

Disabling notification categories does not suppress notifications

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Disabling notification categories at https://www.minds.com/settings/account/push-notifications does not appear to suppress related notifications. ### Steps to reproduce - Navigation to Push Notifications settings (https://www.minds.com/settings/account/push-notifications) - Disable a category, e.g. `Votes` - Use another account to vote on one of your posts ### Platform information - MacOS + Chrome - iPhone - Android app ### What is the current *bug* behavior? - A push notification appears on my browser + mobile device ### What is the expected *correct* behavior? - No push notifications should be sent for categories the user has disabled ### Relevant logs and/or screenshots (Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.) ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-06-16 23:04:15.897

Unable to login on minds.com/login page with 2FA

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary The minds.com/login page throws an error (`Sorry, there was an error. Please try again.`) when logging in with an account that has app-based 2FA enabled. ### Steps to reproduce - Visit minds.com/login while not logged in. - Attempt to log in with an account that has app-based 2FA enabled. ### Platform information - MacOS + Chrome ### What is the current *bug* behavior? - After inputting username+password and submitting, an error message is displayed. ### What is the expected *correct* behavior? - After inputting user+password and submitted, a 2FA code input is displayed. ### Relevant logs and/or screenshots  ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-06-15 20:29:25.402

Inconsistent capitalization on Push Notifications settings screen

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary The options on the Push Notifications screen are inconsistently capitalized in the mobile app. ### Steps to reproduce - Open the mobile app - Navigate to Settings > Account > Notifications > Push - Scroll down to the bottom of the list ### Platform information - iOS app ### What is the current *bug* behavior? The following menu items read: - chats - groups - wires - reports - Top posts from my network - community_updates ### What is the expected *correct* behavior? The following menu items should read: - Chats - Groups - Pay - Reports - Top Posts - Community Updates ### Relevant logs and/or screenshots  ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-06-15 16:33:03.838

NSFW posts appearing in Discovery / Tasman recs

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Posts marked as NSFW are appearing in Discovery feeds of users who have NSFW content disabled. ### Steps to reproduce - Log into Minds - Make sure your `Always show NSFW content` setting is disabled: https://www.minds.com/settings/account/nsfw-content - Visit https://www.minds.com/discovery/top ### Platform information All ### What is the current *bug* behavior? Posts marked as NSFW appear in the Discovery feeds for users with `Always show NSFW content` disabled. ### What is the expected *correct* behavior? NSFW content should not appear in the Discovery feeds for users with `Always show NSFW content` disabled. ### Relevant logs and/or screenshots  ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-06-14 21:41:10.666

Top post notification does not open to content

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary When tapping a top post notification, the Minds app is launched but the user is not brought to the promoted content. ### Steps to reproduce - Receive a top post notification - Tap the notification ### Platform information - iPhone + latest test build ### What is the current *bug* behavior? - The app is opened - The user is brought to the last screen they viewed in the app ### What is the expected *correct* behavior? - The app is opened - The user is brought to the single activity post view that matches the promoted content ### Relevant logs and/or screenshots (Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.) ### Possible fixes ...

2022-06-14 21:40:48.013

Top post notification has no title

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary As [spec'd](https://gitlab.com/minds/mobile-native/-/issues/4289) and built, top post notifications are sometimes sent without titles. The appearance of these notifications is not ideal. ### Steps to reproduce Receive a top post notification for a media post (image or video) ### Platform information - iOS ### What is the current *bug* behavior? - The notification appears with `[Display name / @username] posted [an image / a video]` in the body of the notification, but no title ### What is the expected *correct* behavior? - The notification appears with `[Display name / @username] posted [an image / a video]` in the title of the notification, with no body ### Relevant logs and/or screenshots (Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.) ### Possible fixes If no title, then do not provide in the payload - https://gitlab.com/minds/engine/-/blob/master/Core/Notifications/Push/Services/ApnsService.php#L19

2022-06-14 21:38:16.393

Record referrer data when push notification is used to launch the app

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal We want to be able to measure the impact of mobile app push notifications -- including activity notifications, top post notifications, and ad-hoc notifications. ## What needs to be done If the notifications get clicked and launch the app, we should record referrer data to the screen view so that screen view data can be sliced by referrer, e.g. - UTM source: `minds` - UTM medium: `push-notification` - UTM campaign: `ad-hoc` / `top-post` / `activity` User data should be anonymized. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No design ## Personas This change impacts Minds data team ## Experiments No experiment ## Acceptance Criteria - [ ] ... ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-06-14 21:37:19.489

Top post push notifications sometimes repeat

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary The top post push notification may sometimes send a notification for the same piece of content on consecutive days. ### Steps to reproduce - Get a top post notification, but don't view the activity post it promotes - Wait 24 hours ### Platform information - iPhone + latest test build ### What is the current *bug* behavior? - If the previously-promoted post is still your top post, you'll get a notification for the same post again ### What is the expected *correct* behavior? - If the previously-promoted post is still your top post, you'll get a notification for a different top post ### Relevant logs and/or screenshots (Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.) ### Possible fixes - Make top post query only include posts less than 24 hours old

2022-06-10 17:51:36.637

Referred channels not appearing on Referrals screen

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary If I share my referral link with someone who already has a `referrer` cookie, and then that user signs up, the newly-registered channel does not appear on my [referrals screen](https://www.minds.com/settings/other/referrals). ### Steps to reproduce These steps require two users / mimicking two users via separate browser sessions. As User B... - Open an incognito window - Navigate to a minds.com channel page (e.g. https://www.minds.com/airicmusic/) that does not belong to User A As User A... - Navigate to minds.com/settings/other/referrals - Copy the referral link (e.g. https://www.minds.com/register?referrer=mellamomrs) - Share the link with User B As User B... - Follow User A's referral link - Sign up for a Minds account As User A... - Refresh the Referrals page ### Platform information - MacOS + Chrome ### What is the current *bug* behavior? - The newly-registered account does NOT appear on the Referrals page ### What is the expected *correct* behavior? - The newly-registered account DOES appear on the Referrals page ### Relevant logs and/or screenshots This was reported by user [Airic (airicmusic)](https://www.minds.com/airicmusic/), who reported helping a friend register the follow account using Airic's referral code. - https://www.minds.com/drsebison/ ### Possible fixes I propose that we overwrite the `referral` cookie when a user visits a referral link (query parameter). - Given I am NOT a registered Minds user, - and I have a `referral` cookie from a prior visit to Minds, - when I navigate to Minds via a referral link, - then my `referrer` cookie is overwritten with the GUID of the user referenced in the referral link.

2022-06-10 06:12:30.087

(bug) Number of notifications stuck

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Some people complain about number of their notifications being stuck (also people in comments mention this issue): - CensorshipSucks - https://www.minds.com/newsfeed/1381700651850928133 - Dinshale_Piranha - https://www.minds.com/newsfeed/1380929515328376839 - Dannica (don't have post for hers) - AdamMisner - https://www.minds.com/newsfeed/1379763306679504901 ### Steps to reproduce Unknown ### Platform information - Censorshipsucks - Desktop, Windows and Chrome ### What is the current *bug* behavior? Number notification is being stuck on a number, and doesn't update. ### What is the expected *correct* behavior? Should either: - Not show count. - Not show the count of notifications that aren't there. ### Relevant logs and/or screenshots (Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.) ### Possible fixes Remove count?

2022-06-08 21:10:34.728

Create sitewide banner to promote Minds Festival of Ideas

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Sell tickets to Minds Festival of Ideas. ## What needs to be done Create a simple banner element that displays on every page of Minds, to both registered and unregistered users, and clicks through to where users can buy tickets. - Text: Minds Festival of Ideas in NYC on June 25. Tickets on sale now! - CTA: Buy Tickets - Link: https://www.ticketmaster.com/event/3B005CB2CF161F8D?utm_source=minds&utm_medium=banner&utm_campaign=festival ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design  ## Personas Everyone on Minds ## Experiments No experiment ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] A banner element appears on every page of Minds with the copy defined above. - [ ] The banner clicks through to the link defined above. - [ ] The banner is dismissable and stays dismissed for the duration of the user's session. ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-06-08 19:25:17.191

Report Queue not Loading

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal <!--- Clearly outline the goal of the issue and why we are doing it ---> Fix the admin report queue so that it doesn't load so slowly. https://sentry.io/organizations/minds-inc/issues/3329347389/?query=is%3Aunresolved ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> The admin queue loads very slowly, sometimes not loading at all. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design <!--- Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged. ---> ## Personas <!--- Who does this user impact and why (optional) ---> ## Experiments <!--- Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined. ---> ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] ... ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-06-07 21:06:40.328

Unread notifications email links to broken page

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary The `You have unread notifications` email links to a minds.com URL that doesn't work. https://mobile.minds.com/notifications/v3 ### Steps to reproduce - Receive a `You have unread notifications` email - Click the `View all notifications` button at the bottom of the email ### Platform information - Tested on MacOS + Chrome ### What is the current *bug* behavior? - The minds.com page partially loads, but the content doesn't fill out ### What is the expected *correct* behavior? - The user is brought to a page with all of their notifications ### Relevant logs and/or screenshots  ### Possible fixes Replacing `mobile` `mobile.minds.com` with `www` (`www.minds.com`) appears to load as expected.

2022-06-07 18:56:26.703

Backend support for displaying channel subscriber relationships

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Unblock two frontend tasks related to presenting relevant subscription relationships. - https://gitlab.com/minds/minds/-/issues/3012 - https://gitlab.com/minds/mobile-native/-/issues/4313  ## What needs to be done Create backend support to return data that enables the frontend tickets listed above. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No design. ## Personas - Minds dev team ## Experiments No experiement ## Acceptance Criteria - [ ] There is a backend service that can support the tickets linked above. - [ ] Return a list of channels that subscribe to the channel in question, that I am also subscribed to. ie. mutual subscribers - [ ] Create a mechanism to keep cassandra friends table in sync with new vitess table - [ ] Spec tests - [ ] If no matches found, return 200 with an empty array of users. ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-06-03 14:29:40.523

Prompt with confirm box before acting on boost

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal <!--- Clearly outline the goal of the issue and why we are doing it ---> The goal is to eliminate finger slip and double-tap errors in the admin boost queue. ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> Force a confirm box before accepting or rejecting a boost: ## QA Test confirm box when accepting/rejecting a boost ## UX/Design A simple alert like  ## Personas Admins, to aid in the prevention of slips. ## Experiments N/A ## Acceptance Criteria - [ ] Boosts shouldn't be able to go through without confirming in a confirm box popup. ## Definition of Ready Checklist - [x] Definition Of Done (DoD) - [x] Acceptance criteria - [ ] Weighted - [x] QA - [x] UX/Design - [x] Personas - [x] Experiments

2022-06-01 16:20:23.707

Backend support for activity posts with multiple media attachments

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Support activity posts with multiple images to enable content creators to create content they expect to create on social media. ## What needs to be done Set up backend to support a new activity post type that contains multiple images. Some assumptions we can make: - A post can have multiple images (1-4). - All upvotes / engagements on images within the post are attributed to the post -- in other words, the activity post has one set of engagements; we do not store engagements separately for each image within the post. Activity: ``` ->custom_type = 'batch'; ->custom_data = [ [ // image one 'thumbnail_src' => < source to thumbnail 1> ], [ // image two 'thumbnail_src' => < source to thumbnail 2> ] ] ``` Album: ``` // TODO: ``` ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design Front end design of the multi-image posts is still in progress. Michael and/or Ryan can walk through in-progress designs if necessary. ## Personas - Core Minds creators ## Experiments No experiment ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [x] The backend supports a new activity post with multiple images - [x] Agreement on data structure - [x] Proof of concept of working ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-05-31 23:41:37.617

In-feed notice: Minds event

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Communicate the Minds New York event to all active users on the site, and give them the chance to find and more and buy tickets. ## What needs to be done Create an in-feed notice with low priority that appears for all users, given they haven't already dismissed it. Note: This in-feed notice is a bit different than others in that (1) the only condition for it to appear is that the user hasn't already dismissed it, (2) it effectively has an expiration date on it (we don't need to run it after the event), (3) we will likely want to replace it with another notice with updated messaging as we get closer to the event (e.g. `Learn how to live stream the event`). Just some things to consider for the execution. | Notice | Description | Dismissable | Position | Sticky | Display priority | Conditions | Primary action | |-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------|--------|------------------|------------------------------------------------|------------------------------------------------------------------------------------------------------------------| | Join us in NYC! | Come see Timcast, Cornel West, James O'Keefe, Coleman Hughes, Blaire White, Daryl Davis, Seth Dillon, Destiny, Ben Burgis, Bill Ottman, Zuby and more, live in New York on June 25. | Yes | In-feed | No | 5 | User has not previously dismissed this notice. | Learn more (link to: https://www.minds.com/minds/blog/minds-the-beacon-theatre-june-25-2022-1371588535462662152) | ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No new design. ## Personas This is targeted at core Minds users who may be interested in attending our live event. ## Experiments No experiment. ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Given a user is not eligible to see any of the other in-feed notices, and the user has not already dismissed the event promo notice, when the user visits the Newsfeed, they'll be presented the event promo in-feed notice - [ ] The notice can be clicked on to learn more about the event - [ ] The notice can be dismissed (via x button) and won't re-appear for that login session ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-05-25 18:44:35.810

Change email schedules

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal When a user signs up for a new account, we automate some emails to onboard them into different features on Minds. One is the `Get paid for your posts on Minds` email, which is sent a day after they sign up. However, we're testing a change to when users are able to join events, a change that puts a 3-day account age requirement ahead of joining rewards. The goal is to keep the email messaging consistent with the site messaging. ## What needs to be done Change the timing of the `Get paid` email to be sent 3 days after they've signed up. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No design changes. ## Personas This impacts new users who may be interested in Rewards. ## Experiments This change blocks another experiment, but otherwise no experiment. ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Change Bring your Friends email to be on day 1 - [ ] The `Get paid for your posts` email is sent to new users 3 days after they sign up ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-05-24 09:03:17.305

Conditional 2FA required modal title

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Changing title in email code confirmation modal from 2FA Required in the modal to Confirm Your Email would make more sense ## What needs to be done Change title if the user does NOT have an email confirmed in the session service (or email confirmation service?) to 'Very email' ## QA Check modal title is appropriate before and after email confirmation. ## UX/Design N/A ## Personas Onboarding users ## Experiments Ties into email code experiment but is not a standalone experiment. ## Acceptance Criteria - [ ] Change title and other relevant copy dependant on whether session is confirmed - [ ] Unit tests ## Definition of Ready Checklist - [x] Definition Of Done (DoD) - [x] Acceptance criteria - [ ] Weighted - [x] QA - [x] UX/Design - [x] Personas - [x] Experiments

2022-05-20 00:43:27.726

Browser notifications prompt follow-up

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Following up the recent browser notifications prompt change (https://gitlab.com/minds/minds/-/issues/3111) with small changes to reduce user confusion. - More clearly communicate the distinction between push notifications the user is enabling and the notifications they're currently reading - Don't display the prompt for users on browsers that aren't compatible with the feature. ## What needs to be done Change the copy that appears in the component to `Enable push notifications for this device` Display the prompt only for browsers that support our push notifications. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No design (just copy change described above). ## Personas Core users ## Experiments No experiment. ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Change the copy that appears in the component to `Enable push notifications for this device` - [ ] Double check display the prompt only for browsers that support our push notifications. (Do not sure for Brave). ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-05-19 23:33:31.095

Automate post-signup survey for lapsed users

<!---Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Get a consistent flow of feedback from users who sign up for Minds ## What needs to be done Automate an email to go out to users who sign up for Minds accounts, 7 days after registration. The email should link users to a survey where they can provide feedback that we can use to better understand how to serve new users coming to Minds. Match the email design linked below. - Email subject: What do you think of Minds? - Preview text: Positive or negative, we'd love your feedback.͏‌ - CTA: Quick Survey - CTA link: https://mindsdotcom.typeform.com/to/n6Sj3qsg#segment=0 - Headline: What do you think? - Body copy: > Hey @username! Thanks for joining Minds to help us elevate the discourse through Internet freedom. > > Whether positive or negative, we'd love hear your feedback about your experience on Minds so far. It will only take a few moments, and the information you provide will help improve our service. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design - [Litmus designs](https://litmus.com/pub/eb83d00) - Screenshot below for easy reference -- but if different from the Litmus link above, use the Litmus link as source of truth. - [Download Email Assets](/uploads/cb744a1876d13bb3e6291f5d5c45dbb1/First_impressions_questionnaire__lapsed_users_.zip)  ## Personas - Users who signed up for Minds but didn't end up sticking around; curious users ## Experiments No experiment ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Given a user has signed up for Minds and verified their email address, when 7 days have passed, then the user receives an email prompting them to complete a survey - [ ] The email includes a CTA link to the Typeform survey linked above ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-05-19 21:26:52.327

In-feed notices: Join rewards flow

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/doc s/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal - Make the flow for onboarding into Rewards program accessible on mobile web - Increase the % of authentic new users who join rewards - Decrease the % of inauthentic new users who join rewards ## What needs to be done 1. Create 3x new in-feed notices that advance the user through the rewards onboarding process. 2. Remove the `Complete to earn tokens` component from the sidebar | Notice | Description | Dismissable | Position | Sticky | Display priority | Conditions | Primary action | |------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------|--------|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------| | Who is @username? | Let the Minds community know who you are by decking out your channel page. This step is required to join the token rewards program. | Yes | In-feed | No | 2.2 | User has not uploaded avatar, banner, and/or added a bio | Set up my channel (launches channel setup modal) | | You're invited! Join rewards | Verify your uniqueness to get started earning token rewards for engagement on your content. | Yes | In-feed | No | 2.3 | User has already: (1) Verified their email, (2) selected interest tags, (3) set up channel with a name, avatar, and bio, (4) made at least one post, and (5) their account is at least 3 days old. | Verify uniqueness (launches Phone Verification > Connect to Wallet modal) | | Connect a crypto wallet | To earn tokens and access the decentralized web, connect Minds to your crypto wallet. This step is required to join the token rewards program. | Yes | In-feed | No | 2.4 | User has satisfied all requirements for being invited to rewards, and has verified their uniqueness. | Connect wallet (launches Connect Wallet modal) | ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design This should use the existing component for in-feed notices. ## Personas - New users - Content creators who will benefit from rewards ## Experiments We should deploy this change via an experiment, with: - (a) the control variant, in which `Complete to earn tokens` is in the sidebar and no new in-feed notices, and - (b) the test variant with `Complete to earn tokens` removed form the sidebar and the new in-feed notices introduced. ## Acceptance Criteria - [ ] Backend API that returns the display logic for in feed notices - [ ] The in-feed notices described above appear in the Newsfeed under the conditions described - [ ] Each notice launches the appropriate modal that the user can complete - [ ] When a modal is completed, the in-feed notice is removed from the Newsfeed ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [x] Acceptance criteria - [ ] Weighted - [ ] QA - [x] UX/Design - [x] Personas - [x] Experiments

2022-05-18 23:22:19.498

Add notification setting for Community Updates

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Give users control over whether or not they receive ad-hoc push notifications via our new ad-hoc tool ## What needs to be done Add a setting to the existing settings screen for `Community updates`. Default the setting to on. The setting determines whether or not the user receives ad-hoc push notifications. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No new designs -- this should use the same component design for existing notification settings. ## Personas Core users. ## Experiments No experiment ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] A new `Community updates` option is added to the Settings > Notifications screen - [ ] Add to https://gitlab.com/minds/engine/-/blob/master/Core/Notification/Settings/PushSettings.php#L35 - [ ] The setting defaults to `on`. - [ ] Given the user has notifications enabled, and the setting for `Community updates` is ON, when a notification is sent through the new ad-hoc tool, then the user does receive the notification. - [ ] Given the user has notifications enabled, and the setting for `Community updates` is OFF, when a notification is sent through the new ad-hoc tool, then the user does NOT receive the notification. - [ ] Admin system push notifications to respect the flag - [ ] Added by Ben: Notif added in https://gitlab.com/minds/engine/-/merge_requests/1030 should be respected ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-05-17 21:48:00.472

Measure click events for Channel feed controls

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Goal is for the team to understand how often users engage with the feed controls on Channel pages, including the Type control and the Date control.  ## What needs to be done Add click refs to the feed control menu items so that our click event system measures these clicks. | Feed control | Suggested ref value | |------------------|--------------------------| | Type: All | feedcontrol-type-all | | Type: Images | feedcontrol-type-images | | Type: Videos | feedcontrol-type-videos | | Type: Blogs | feedcontrol-type-blogs | | Date: All time | feedcontrol-date-alltime | | Date: Date range | feedcontrol-date-range | ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No design implications. ## Personas This change is for product analytic use. ## Experiments No experiments. ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Feed controls on channel pages have click ref attributes - [ ] Existing click measurement picks up clicks on the feed controls outlined above - [ ] Click events are matched to anonymized user IDs ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-05-10 22:47:43.227

Fire analytics event when a user reaches the end of a feed

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal We want to understand how often users reach the end of feeds, and in what context they reach the end of feeds so that we can identify and prioritize solutions ## What needs to be done Fire an analytics event when a user reaches a "Nothing more to load" message in a feed. This can happen in: - Newsfeed - Channel feed - Discovery feed - Search feed - Group feed - (and other places) The event should pass context that allows us to discern: - Where did the user encounter the end of a feed? Which page / type of feed? - Which platform was the user on? - How many posts were they served before seeing the end of the feed? ### The refactor Deprecate the use of 'click_event'. Replace this with a new event called 'generic_event". | name | type | example | | ------ | ------ | ------ | | event_type | string | eg. 'click', 'view' | | event_ref | string | eg. 'topbar-link' | ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No design requirements for this. ## Personas This change impacts the internal Minds team (Data team and Product Management). ## Experiments No experiment for this. ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] On any given feed, when a user encounters a "Nothing more to load" message, an event is fired - [ ] The event passes sufficient context to answer questions identified above - [ ] Introduce a new 'generic_event' schema and send events when viewed (must be on screen) - [ ] Refactor instances of 'click_event' to use the new 'generic_event' schema - [ ] The data can be analyzed in Superset ## Definition of Ready Checklist - [x] Definition Of Done (DoD) - [x] Acceptance criteria - [x] Weighted - [x] QA - [x] UX/Design - [x] Personas - [x] Experiments

2022-05-09 14:03:02.372

Implement media engagement metrics (mobile)

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal We're defining a general content engagement metric that counts interactions with media posts. We need to be able to measure when these interactions happen. ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> Create new analytics events that fire when a user interacts with media in the following ways: - [ ] Clicks to unmute an autoplay video ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No design changes. ## Personas Minds staff and data team. ## Experiments No experiment needed for these changes. ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Analytics events fire each time one of the above-listed actions is performed - [ ] Events are related to the activity post IDs that the user is interacting with - [ ] Events are matched to anonymized IDs of the users performing the engagement - [ ] Use the 'click_event' schema that we use on the frontend ## Definition of Ready Checklist - [x] Definition Of Done (DoD) - [x] Acceptance criteria - [x] Weighted - [ ] QA - [x] UX/Design - [x] Personas - [x] Experiments

2022-05-04 17:28:02.240

Email 2FA modal generates confusing messages

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary The email 2FA modal on web generates some confusing messages, in two scenarios: 1. When the user clicks `Resend` button, then a toaster is displayed with the message `TwoFactor is required` 2. When closing the 2FA modal, then a toaster is displayed with the message `TypeError: cannot read properties fo undefined (reading 'status') ### Steps to reproduce Issue #1: 1. Log into an account that does NOT have app-based 2FA configured 2. Navigate to Account > Password screen (https://www.minds.com/settings/account/password) on web 3. Start to change the password by filling in your current password + specifying a new one 4. Click "Update Password" to generate the email 2FA modal 5. Click the `Resend` button. ---- Issue \#2: 1. Log into an account that does NOT have app-based 2FA configured 2. Navigate to Account > Email Address (https://www.minds.com/settings/account/email-address) on web 3. Change the email to anything else => fill in your password 4. When the email 2FA modal pops up, dismiss it 5. Notice the toast error that says `TypeError: Cannot read properties of undefined (reading 'status')` (img 2) ### Platform information MacOS + Chrome ### What is the current *bug* behavior? Issue #1: - A new verification email is sent, and the modal flashes, and the toaster message `TwoFactor is required` is displayed ### What is the expected *correct* behavior? ~- A new verification email is sent and the toaster message communicates that the email was sent.~ Handling in https://gitlab.com/minds/front/-/issues/5512 - this is a wider issue than just the error message being incorrect. Expected behavior - Get rid of superfluous "TwoFactor required" message (as discussed in sprint planning) - Fix other error dev error message mentioned above ### Relevant logs and/or screenshots Clicking `Resend` generates `TwoFactor is required` toaster message.  Closing the modal generates this toaster message.  ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-05-04 10:20:30.761

New email verification templates for code/link email verifications

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal <!--- Clearly outline the goal of the issue and why we are doing it ---> Update the visual presentation of Minds email communications to (1) appear more consistently across multiple email clients, and (2) appear more credible. ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> We're starting with the new template rollout by implementing it for email verification messages. Create a new email template for code-based email verifications, that uses the copy defined below and the email HTML layout linked in the Design section. - **Subject (code ver):** 000000 is your verification code for Minds - **Email preview (code ver):** Verify your email address with Minds. - **E-mail copy (code ver):** Enter this verification code on Minds to complete your registration. --- - **Subject (link ver):** Verify your email address - **Email preview (link ver):** One click to complete your registration on Minds. - **E-mail copy (link ver):** Click the button below to complete your registration. - **CTA (link ver):** Verify ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design Please find attached two email templates relating to email verifications. These templates have been tested using Litmus, are fully responsive. Existing template -> https://gitlab.com/minds/engine/-/blob/master/Core/Email/V2/Common/default.tpl ### Assets * [Preview - Verify Link](https://litmus.com/pub/f277e9c) * [Preview - Verify Code](https://litmus.com/pub/9836287) * [Verify__Link.zip](/uploads/2a03a77c14235ac038a5764c98f826c3/Verify__Link___1_.zip) * [Verify__Code.zip](/uploads/54a98f55c13364a15327514714134143/Verify__Code___1_.zip) ## Personas All new users ## Experiments We should test the impact of switching to Codes for verification -- e.g. to measure do more or fewer or the same percentage of users complete verification. I believe this experiment will be handled with the front end component of this update, and that we don't need a separate test for this email component. ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Code-based verification emails use the newly-defined template - [ ] The email layout looks good in all major email clients -- some variance is expected, but they should not look broken ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-05-03 22:25:01.318

Measure browser push notification clicks

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal We need to understand the value of browser push notifications, both to users and to Minds. ## What needs to be done Enable the measurement push notification clicks. Given the assumption that clicking a push notification opens a web URL, a possible solution is adding `utm` parameters to URLs for push notifications. Consider using `onClick` from the service worker to avoid utm codes. Use existing snowplow click event. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No design requirements. ## Personas This primarily impacts Minds staff and data team. ## Experiments No experiments associated with this change. ## Acceptance Criteria - [ ] In Superset, we're able to understand what volume of pageviews and sessions were initiated via browser push notification. ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [x] Acceptance criteria - [ ] Weighted - [ ] QA - [x] UX/Design - [x] Personas - [x] Experiments

2022-05-03 22:10:06.778

Request notifications permission from Notifications dropdown

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Increase the % of users who opt into browser-based push notifications. ## What needs to be done Add a button to the Notifications dropdown that allows the user to enable notifications for the current device. The button will request notifications permissions from the browser. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design - [Notification request design](https://www.figma.com/file/FiOiKZkuObKfZbHrWwe0pU/Notifications-%5BWeb%5D?node-id=101%3A4080)  ## Personas - All active users ## Experiments This feature does not need an experiment. ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [x] Given the user has not already enabled or blocked browser notifications for Minds, when the user clicks the Notifications bell and the Notifications dropdown appears, then the user sees a button to enable push notifications for the current device. - [x] Given the user has not already enabled or blocked browser notifications for Minds, when the user clicks the button, then a browser-level prompt appears that asks the user to enable or block notifications for Minds.com. - [x] Given the user HAS already blocked browser notifications for Minds, when the user clicks the button then display a toaster message to communicate "Your browser blocked Minds notifications. Change site settings in your browser to allow and try again." - [x] When the user allows notifications permissions for Minds, then Minds enables push notifications for the device they're on. - [x] Given notifications are enabled for the current device, when viewing the notifications settings screen (https://www.minds.com/settings/account/push-notifications), then the button under the `Push Notifications` heading is a button to disable notifications. ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [x] Acceptance criteria - [ ] Weighted - [ ] QA - [x] UX/Design - [x] Personas - [x] Experiments

2022-05-03 07:42:50.015

Create Experiment::<Scope> labels.

## Goal Quickly identify tickets that require an experiment from the Sprint board. ## What needs to be done Create a Experiment::<Scope> labels as below: - Experiment::Required - Experiment::Disabled - Experiment::Configured - Experiment::InProgress ## QA N/A ## UX/Design N/A ## Personas N/A ## Experiments N/A ## Acceptance Criteria - [ ] Labels created and assigned to the relevant tickets ## Definition of Ready Checklist - [X] Definition Of Done (DoD) - [X] Acceptance criteria - [X] Weighted - [X] QA - [X] UX/Design - [X] Personas - [X] Experiments

2022-05-03 07:36:40.021

Update sandbox helm charts for FE/BE to use staging image instead of production

## Goal Improve testing environments to avoid issues when deploying to sandbox during MRs. ## What needs to be done Update helm charts for FE and BE to pull image from staging/latest if no branch exists. ## QA Check that the correct image is being applied in sandbox. ## UX/Design N/A ## Personas N/A ## Experiments N/A ## Acceptance Criteria If FE or BE branch does not exist then the relative sandbox image must be applied from Staging/Latest image. ## Definition of Ready Checklist - [X] Definition Of Done (DoD) - [X] Acceptance criteria - [X] Weighted - [X] QA - [X] UX/Design - [X] Personas - [X] Experiments

2022-04-29 22:46:02.385

Implement media engagement metrics

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal We're defining a general content engagement metric that counts interactions with media posts. We need to be able to measure when these interactions happen. ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> Create new analytics events that fire when a user interacts with media in the following ways: - [x] Clicks an image or video to initiate a large modal view - [x] Clicks to unmute an autoplay video (first time only) ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No design changes. ## Personas Minds staff and data team. ## Experiments No experiment needed for these changes. ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Analytics events fire each time one of the above-listed actions is performed - [ ] Events are related to the activity post IDs that the user is interacting with - [ ] Events are matched to anonymized IDs of the users performing the engagement ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-04-22 14:51:22.299

Update report categories (web)

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal <!--- Clearly outline the goal of the issue and why we are doing it ---> The goal is to streamline the report modal by clarifying categories and removing duplicate and/or unused entries. ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> Report categories should be updated to reflect the chart in the following section. Below is a list of changes: **Text-only changes** 1. Change 'pedophilia' to 'sexualization of minors' 2. Change 'Encourages or incites violence' to 'Incitement to violence' 3. Change 'Impersonates' to 'Impersonation' 4. Change 'Copyright' to 'Intellectual Property Violation' 5. Change 'Token manipulation' to 'Inauthentic engagement' 6. Change "Sex trafficking" to "Trafficking" **Removals** Remove the following categories: 1. Trademark infringement (because it is merged with IP violation) 2. Incorrect use of hashtags (because it does nothing) **Modifications** Under 'Intellectual Property Violations' (formerly 'Copyright') we need to link to the Zendesk DMCA form instead of saying to email to copyright@minds.com. https://support.minds.com/hc/en-us/requests/new?ticket_form_id=360003221852  ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> Minimal QA: make sure reporting under the new labels generates the correct report. Check emails. ## UX/Design <!--- Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged. ---> ... ## Personas <!--- Who does this user impact and why ---> This change impacts typical Minds users who make reports. ## Experiments <!--- Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined. ---> No experiments are needed. ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Labels are correctly changed for users on the report modal - [ ] Labels are correctly changed for admins in the report queue - [ ] Labels are correct in emails ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-04-21 21:45:03.345

Minds URLs often time out before share metadata is returned

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary When sharing minds.com URLs on third party sites that read open graph tags and other metadata to generate URL previews, the minds.com URL often times out. ### Steps to reproduce - [Check a minds.com URL on Schema.org's validator](https://validator.schema.org/#url=http%3A%2F%2Fdebug.iframely.com%2F%3Furi%3Dhttps%253A%252F%252Fwww.minds.com%252Fnewsfeed%252F1362763459632042002) - [Check a minds.com URL on Iframely's debugger](http://debug.iframely.com/?uri=https%3A%2F%2Fwww.minds.com%2Fnewsfeed%2F1362763459632042002) ### Platform information - MacOS + Chrome ### What is the current *bug* behavior? - Validators (as linked above) often return only partial metadata results - Third party sites like Twitter often generate incomplete previews of minds.com URLs ### What is the expected *correct* behavior? - Validators reliably read all relevant metadata - Third party sites like Twitter reliably generate complete previews ### Relevant logs and/or screenshots Iframely with partial metadata returned:  Iframely with complete metadata returned:  Note that in the second screenshot, oEmbed and Open Graph tabs appear, and the GIF media on the page is played. ### Possible fixes I don't have a fix in mind, but guess that it's related to client-side rendering of pages. The initial document we serve from the server contains only partial metadata -- the rest of the metadata, including open graph tags, is rendered client side, which may get delayed / may happen too slowly for whatever timeout standards these sites use.

2022-04-21 21:14:02.840

Small update to minds.com homepage title

<!--- Please read this! The Defintion of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal <!--- Clearly outline the goal of the issue and why we are doing it ---> Improve the appearance of Minds homepage when shared in other apps, to better drive clickthroughs and growth. ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> Bill requested a small update to the Current text: > Minds: The Alternative Social Network New text: > Minds ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> - Validating the document tags match above can be done before release, but testing on Twitter will likely have to happen post release ## UX/Design <!--- Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged. ---> None needed ## Personas <!--- Who does this user impact and why ---> Users not already on Minds; users who have friends on Minds; users who see Minds referenced on social media sites. ## Experiments <!--- Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined. ---> This change should not be deployed as an experiment. ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] The following fields match the text spec'd above: - [ ] `title` tag - [ ] `og:title` meta tag - [ ] When sharing the page on Twitter, the text spec'd above appears in the Twitter embed - [ ] Ping @markryansallee when deployed ## Definition of Ready Checklist - [x] Definition Of Done (DoD) - [x] Acceptance criteria - [ ] Weighted - [x] QA - [x] UX/Design - [x] Personas - [x] Experiments

2022-04-21 18:39:01.507

Apply has-seen ranking to Discovery:Top feed

<!--- Please read this! The Defintion of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal <!--- Clearly outline the goal of the issue and why we are doing it ---> Increase the user engagement rate with the Discovery:Top feed on Minds by ensuring that users see fresh content every time they visit them. ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> Apply the same has-seen ranking filter that we use on the Newsfeed:Top feed to our Discovery:Top feed. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ... ## UX/Design <!--- Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged. ---> No visual changes required. ## Personas <!--- Who does this user impact and why ---> Everyone, especially Core users who revisit the same feeds frequently. ## Experiments <!--- Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined. ---> We should deploy this as an experiment to understand the impact. Measure: - Upvotes - Comments - Reminds - Time on site - Sessions per user ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Given the user has previously viewed Post A on the Discovery:Top feed, - when the user re-visits (reloads) the Discovery:Top feed, - then Post A is ranked lower than posts that the user has not already seen. ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [x] Acceptance criteria - [ ] Weighted - [ ] QA - [x] UX/Design - [x] Personas - [x] Experiments

2022-04-20 21:22:58.769

In-feed notice: Update your interests tags

## Goal - Increase the % of active users who have relevant interest tags selected. - Given the recommendations algorithm Tasman is working on, this will improve both (1) the predictiveness of the recommendations, and (2) the ability to reach users with the recommendations. ## What needs to be done Using the in-feed notices component we created, make a new notice that prompts users to update their interest tags, given the user matches conditions specified below. Clicking the modal will launch the existing Content Settings modal, allowing the user to select their interest tags, save, and close the modal to continue using the Newsfeed. ## Experiments This does not need to be deployed via experiment. ### Dev notes Discovery hashtags api endpoint includes all tag information. ## Acceptance - [ ] Create a new in-feed notice that, given the correct conditions described below, can appear in the Newsfeed. - [ ] The notice will prompt users to update their interest tags. - [ ] The prompt will launch the Content Settings modal that lets users set their preferences. - [ ] The prompt is dismissable. - [ ] The prompt should show **only** to users who have not got any tags selected  ### Conditions - User has not already selected interest tags - User HAS selected interest tags, but has not updated them recently (~60 days). | Notice | Description | Dismissable | Position | Sticky | Display priority | Conditions | Primary action | |---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------|--------|------------------|---------------------------------------------------------------------------------------------|---------------------------------------------------------------------------| | Update your preferences | Updating your interest tags improves your experience on Minds, and makes it easier to discover creators and content you haven't found yet. | Yes | In-feed | No | 2.1 | User has not selected tags, OR user has not recently (in last ~60 days) updated their tags. | Select interest tags | ## Definition of Ready Checklist - [x] Definition Of Done (DoD) - [x] Acceptance criteria - [x] Weighted - [ ] QA - [x] UX/Design - [x] Personas - [x] Experiments

2022-04-20 17:16:10.451

Channel recommendations click to "This channel doesn't appear to exist"

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary On a Channel page, after subscribing to user `vigilantfox`, the recommended channels that appeared all clicked to `This channel doesn't appear to exist` pages. ### Steps to reproduce - Navigate to `vigitlantfox`'s channel page https://www.minds.com/vigilantfox/ - Subscribe to `vigilantfox` - Observe the recommended channels that appear - Click the usernames of the recommended channels (e.g. [`weplenty`](https://www.minds.com/weplenty/), [`Gracedd`](https://www.minds.com/Gracedd/)) ### Platform information - MacOS + Chrome ### What is the current *bug* behavior? - The component is recommending channels that don't exist ### What is the expected *correct* behavior? - The component should recommend channels that do exist ### Relevant logs and/or screenshots  ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)

2022-04-08 10:24:14.038

Develop refined and consistent dropdown menu

There seems to be multiple variations of the dropdown menu through the web app. Styles differ from instance to instance as shown below.  See [updated designs](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=1179%3A15815) including both light and dark modes. ## Design Notes * Material icons are optional * The hover colour is the border colour * Include a simple transition on hover of 150ms * Would be nice to quickly fade in/out the menu as it is mounted/unmounted ## Acceptance Criteria - [ ] Create/Update storybook component - [ ] Remove any legacy components and refactor their references - [ ] Provide steps in MR of every component that has been changed to assist with QA

2022-04-08 03:52:54.990

Use verification codes rather than clickable links for email verifications

This issue represents the backend component of https://gitlab.com/minds/minds/-/issues/3055 To incorporate email verification into the onboarding flow, Mark proposes switching to a verification code system. There will be front end changes required to deliver the change to users. Mark suggested making the change available with a feature flag for validation in local/staging environments.

2022-04-05 17:10:05.389

Channel recommendations include channels that have blocked you

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Users have reported that the channel recommendations they get include channels that have blocked them. https://www.minds.com/newsfeed/1355657502728916998  ### Steps to reproduce Use 3x accounts. - Account A: Subscribe to Account B. - Account B: Block Account C. - Account C: Subscribe to Account A. - Account C: Navigate to channel recommendations: https://www.minds.com/discovery/suggestions/user ### Platform information - MacOS + Chrome ### What is the current *bug* behavior? - Account B appears in the channel recommendations for Account C. ### What is the expected *correct* behavior? - Channel recommendations does not suggest channels that have blocked you. ### Relevant logs and/or screenshots   ## Acceptance criteria - [ ] Do **NOT** include as part of the ACL. Include at the API level in a filter only.

2022-04-05 15:20:04.574

Language sidebar prompt, Layout issue

<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate. ---> ### Summary The language change prompt in the sidebar can break the layout if the language name string is long (see screenshot). ### Steps to reproduce - Set your browser language to something other than English - Set your Minds language to English - Navigate to the Newsfeed ### Platform information - MacOS + Chrome ### What is the current *bug* behavior? - The button breaks out of the boundaries of the sidebar component ### What is the expected *correct* behavior? - The button fits inside the layout ### Relevant logs and/or screenshots  ### Possible fixes A. Allow the string to wrap to a second line B. Reduce font size for the string / overflow with ellipses in case it's still long C. Change the button copy to just "Change Language"

2022-03-25 21:08:56.570

Experiment: Change name of Discovery to Explore

<!--- Please read this! The Defintion of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal <!--- Clearly outline the goal of the issue and why we are doing it ---> Change the Navigation menu item of Discovery to Explore to see if we can increase traffic to the page ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> Change the navigation menu name ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ... ## UX/Design <!--- Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged. ---> Change: On web, change the text of the `Discovery` navigation item to `Explore`.  ## Personas <!--- Who does this user impact and why ---> ... ## Experiment Hypothesis: By changing the name of the Discovery item in the nav bar, we can increase usage of the Discovery / Top page. <!-- Describe the change you'd like to test, and your hypothesis for its positive impact --> ## Measures ### Improvement category This experiment aims to improve: - Increase the number of users who view the Discovery feed <!-- - User growth - Retention - Team velocity - Spam impact - Minds revenue - Creator revenue - Boost value --> ### Direct measure The primary metric we expect to improve with this change: - Page / Screen views of /discovery/top Additional metrics we want to watch: - Upvotes - Reminds - Comments Segment by: - Newly registered users - Already-active users ### Counter metric To ensure we're not over-optimizing for one metric, we'll also look at impacts on this counter metric: - None ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Change the text from Discovery to Explore - [ ] Introduce a new experiment and have setup on growthbook ## Definition of Ready Checklist - [x] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [x] UX/Design - [ ] Personas - [ ] Experiments

2022-03-24 22:28:40.748

Standardize sidebar components for feeds

To make the site more predictable and enable better A-B test controls, we should standardize the components that appear for logged-in users in the sidebar of feeds including: - Newsfeed - Discovery feeds - Search feeds This table outlines the different sidebar components, which appear in which feed *currently*, and which should appear in the new shared, standardized layout. Numbers represent the order of appearance, from top to bottom. | Component | Newsfeed | Discovery | Standardized | |------------------------------------|----------|-----------|--------------| | Complete to earn tokens | 1 | | 1 | | The community-owned social network | | 1 | | | Boost (channel) | 2 | | 3 | | Trending tags | 3 | 2 | 2 | | Suggested channels | | | | | Boost (post) | 4 | | 4 | | Boost (channel) | 5 | | 5 | | Boost (channel) | 6 | | 6 | ## Acceptance - [ ] As a logged-in user, when viewing the Newsfeed, Discovery feeds, or Search feeds on a desktop browser, the sidebar displays the same components, in the same order. - [ ] The contents of `Suggested channels` and `Trending tags` components are contextually matched to the feed they appear against.

2022-03-24 21:58:24.077

Let users hide in-feed components (Channel Recommendations, Highlights)

We should add the option for users to temporarily hide components that appear in feeds, including Channel Recommendations and Highlights. ## Acceptance - [ ] When a user encounters a hideable in-feed component, they have an interface that lets them choose to hide the component. - [ ] If the user chooses to hide the component, the component disappears from the page. - [ ] Every time the user visits a feed during their logged in session, the in-feed channel recommendations component does not appear. - [ ] If the user chooses to hide in-feed channel recommendations, this DOES NOT impact their appearance in dynamic contexts such as when it appears after clicking the subscribe button. ## Design notes **Important: See related menu refactor task here -> https://gitlab.com/minds/minds/-/issues/3058** - [Recommended channel design - ellipsis](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=333%3A2374) and [Active menu](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=1179%3A16526) - Language TBC. I see @markryansallee specified `Remove fro Newsfeed`, designs however state `Remove from Feed` which may be seen as more general and usable on channels, or elsewhere (e.g. discovery)

2022-03-24 21:22:13.671

Measure signup attempts

<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Enable the product dev team to understand what % of signup attempts are completed, in order to measure the impact of future changes to the signup process. ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> Fire a new event when a signup is attempted. - [ ] When the signup modal is displayed - [ ] When a user visits the minds.com/register page ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design No design ## Personas This impacts the Minds product dev team. ## Experiments No experiment. ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Register a 'view' generic event for the register form - [ ] Ensure the register modal fires a `signup start` event - [ ] Ensure minds.com/register fires a `signup start` event - [ ] Create Growthbook metric for 'register form view' that is Binomial - [ ] In Growthbook, we can apply a `Signup completion rate` metric to understand the impacts of changes to the site. ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments

2022-03-21 16:49:08.042

Users are clicking expired email verification links

### Target problem A high percentage of users who create accounts on Minds don't use the app after 2 hours. Tasman has identified a common pattern with these users: - They haven't verified their email address - They have multiple events showing them clicking the "Resend" button on email verification ### Hypothesis - Verification emails end up in the user's spam folder and get missed - If a user clicks "Resend" and later finds the emails in their spam folder, they may follow a verification link in an older verification email -- which will have expired and give them an error. - [ ] Re-using the same verification link rather than generating a new one every time the user clicks "resend," will result in a higher % of users who register. OR not expiring previous verification links after a new one is sent will have the same effect. ### What is the primary metric that this change is aimed to improve? Daily registrations (email verifications) / Daily signups (new accounts created), can be measured in the [Growth Dashboard](https://analytics.minds.com/superset/dashboard/32/?native_filters=%28NATIVE_FILTER-jhvp9Gs1E%3A%28__cache%3A%28label%3AAuthentic%2CvalidateMessage%3A%21f%2CvalidateStatus%3A%21f%2Cvalue%3A%21%28Authentic%29%29%2CextraFormData%3A%28filters%3A%21%28%28col%3Aaccount_type%2Cop%3AIN%2Cval%3A%21%28Authentic%29%29%29%29%2CfilterState%3A%28label%3AAuthentic%2CvalidateMessage%3A%21f%2CvalidateStatus%3A%21f%2Cvalue%3A%21%28Authentic%29%29%2Cid%3ANATIVE_FILTER-jhvp9Gs1E%2CownState%3A%28%29%29%29). ### What is the current state of this metric, and what is the improvement goal? Currently conversion is ~30%; 90%+ seems like a realistic goal for an action with such strong intent as signup. ### Size estimate (Size estimate -- from Design + Dev -- required to deliver this change. Is just an estimate) ### Acceptance - [ ] If the user generates multiple verification emails via the "Resend" button, following the `Verify Address` button in any email will verify the user's address. - [ ] Keep links valid for 24 hours

2022-03-21 16:27:03.920

Ad-hoc push notifications tool / interface

### Target problem Most Minds app users do not get frequent push notifications because they don't get daily engagement on their content. Because many are not reminded of Minds through notifications, they forget to check into the app daily. ### Hypothesis By sending more regular general push notifications (e.g. Watch Minds on Joe Rogan), we can remind many users to check into Minds daily. ### What is the primary metric that this change is aimed to improve? DAU, Check-ins ### What counter metric will ensure that an increase in the primary metric is a positive for the product? % of users with push notifications enabled / Minds has access to send them notifications ### Size estimate (Size estimate -- from Design + Dev -- required to deliver this change. Is just an estimate) ### Acceptance Criteria - API endpoint (restricted to only admins) to trigger ad-hoc push notifications - API to support basic reporting of notification - CLI for testing and/or manual triggers - Abstraction of sender lists for future targeting support. Initial implementation to go to all devices - Backend runner to subscribe to events - Fields to support Title, Message, Link/URI - Database to store (timestamp, author, title, body, uri, counter, status) - Frontend to live in admin panel