idproject
int64 7.76k
28.8M
| issuekey
int64 675k
128M
| created
stringlengths 19
32
| title
stringlengths 4
226
| description
stringlengths 2
154k
⌀ | storypoints
float64 0
300
⌀ |
|---|---|---|---|---|---|
10,171,263 | 95,528,523 |
2021-10-16 13:36:58.875
|
Old account validation issue
|
| 2 |
10,171,263 | 97,494,876 |
2021-10-14 14:39:34.694
|
"api/v3/oauth/token" should not return a valid session if the user is banned
|
Currently, when an account is banned, they will be able to log into the app and get past the auth state. But when they enter the app they can't do anything. And when the app is restarted, they will go back to the auth page.
## What should happen
- Given a user is banned, an error should be shown on the login screen.
- Given a user is banned and they're logged in, an error should be shown to them to let them know they've been banned and they should be navigated to the login screen.
| 1 |
10,171,263 | 94,957,709 |
2021-10-06 13:48:19.979
|
Create a Recommendations module that is expandable
|
- [x] Create a module that can return entities based on a 'placement' variable
- [x] api/v3/recommendations controller
- [x] Spec tests
## Recommendations algorithms
- [x] use Suggestions for 'suggested-channels' algorithm
- [x] Create 'wider-network' recommendations algorithm
- [ ] Create 'inferred' recommendations algorithm
## Vision for the module
We want to create a module that can be easily expanded as we learn more about our data and usage patterns of the site. For example we want to be able to support multiple answers such as 'posts that by subscriptions have voted on' but also 'top posts my subscriptions have made'.
The API should be able to dynamically determine what algorithms or queries to return based on the `location` that is provided. This will allow us to easily change the recommendations and run experiments from a single place. The frontend only needs to support a simple component that can render the entities.
### Example API Call
#### GET `api/v3/recommendations/?location=feed-sidebar`
RESPONSE:
```json
{
"query": "wider-network",
"entities": [ ],
}
```
```json
{
"query": "inferred",
"entities": [ ],
}
```
```json
{
"query": "favourite-subscribed-posts",
"entities": [ ],
}
```
### Example queries
#### Wider network
This will return entities from my wider network (ie. content that my subscribers have interacted with.
#### Inferred
This will return entities based on content that I have interacted
| 20 |
10,171,263 | 23,758,703 |
2019-08-14 01:23:06.806
|
(feature) Extend the individual entities to return the permissions object on activities
|
When we get a specific entity, we need to include its permissions so the front end can parse its flags
| 3 |
10,171,263 | 23,758,676 |
2019-08-14 01:19:29.098
|
(feature) Extend feeds to return the permissions objects with their results
|
Whenever we return a feed, we have the list of entities we need to permit.
We can implement the new permissions as middleware and return the permissions blob in the export
| 8 |
10,171,263 | 23,758,574 |
2019-08-14 01:10:25.788
|
(feature) Prevent editing of entities on the backend
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 8 |
10,171,263 | 23,758,561 |
2019-08-14 01:08:41.426
|
(feature) Prune entities denied by permissions from from the api responses.
|
When a user marks a channel closed, the feeds need to return their entities through the Permissions object
Any entity that does not have the View permission must be removed.
The ACL permissions check must also make sure the individual channels are blocked
| 8 |
10,171,263 | 23,758,467 |
2019-08-14 01:01:05.224
|
Re-index closed channels in the feed
|
- [ ] Move user mode change to own endpoint
- [ ] Delegate should trigger index of all entities (copy from delete flag part)
- [ ] Introduce a central entities/owner propagator.
| 3 |
10,171,263 | 23,753,381 |
2019-08-13 19:40:49.500
|
(bug): Fix notifications for sandboxes
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 3 |
10,171,263 | 23,745,517 |
2019-08-13 14:45:09.948
|
(feat): Increase pinned posts cap to 12 for Pro channels
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 2 |
10,171,263 | 23,675,098 |
2019-08-11 16:47:30.295
|
Set default license for media
|
Users should be able to set a default license on their media.
| 4 |
10,171,263 | 23,582,860 |
2019-08-07 17:17:12.738
|
(feat): Settings to allow forcing dark/light scheme
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 2 |
10,171,263 | 23,553,454 |
2019-08-06 20:41:29.234
|
(feat): Logging in/signing up via Pro Domain should auto-subscribe the new user to that channel, if not already
| null | 2 |
10,171,263 | 23,552,883 |
2019-08-06 20:03:04.014
|
(feat): Pro channel endpoint to filter by hashtag and/or query
|
To be used by hashtag and search listings
| 3 |
10,171,263 | 23,552,722 |
2019-08-06 19:53:03.298
|
(feat): Pro Settings tab for categories (hashtags)
|
Structure should be `{ tag: string, label: string }`. When normalizing, if no label, it should use `'#' . $entry['tag']`
| 2 |
10,171,263 | 23,447,939 |
2019-08-02 17:08:13.705
|
Re-index all autosuggested users with new analyzer to support numbers
|
<!---
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
It seems that usernames that are numbers, or begin with numbers, do not appear in search.
REF: https://www.minds.com/newsfeed/1003716877810827264
### Steps to reproduce
Search "1085243" in the top search bar. Observe ES does not find the user.
### Platform information
Cross-platform
### What is the current *bug* behavior?
ElasticSearch is not weighting numerical names appropriately.
### What is the expected *correct* behavior?
The name should appear when typed in.
### Relevant logs and/or screenshots
### Possible fixes
I'm presuming something needs tweaking at an ElasticSearch level.
| 4 |
10,171,263 | 23,409,227 |
2019-08-01 17:00:33.687
|
(feat): investigate how we can support transparent images for the logo
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 2 |
10,171,263 | 23,394,370 |
2019-08-01 13:22:20.237
|
(feat): Footer item settings
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 2 |
10,171,263 | 23,356,209 |
2019-07-31 15:54:58.605
|
Boosts from blocked users are being shown
|
<!---
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 user 'A' blocks user 'B', user 'A' is being served the boosts from user 'B'.
### Steps to reproduce
1. Block a user
2. Go to Newsfeed
3. Boosts from that user persist
### What is the expected *correct* behavior?
Boosts should be blocked too.
### Relevant logs and/or screenshots
https://www.minds.com/newsfeed/1002258011014168576
https://www.minds.com/newsfeed/1031185109487849472
| 3 |
10,171,263 | 23,329,906 |
2019-07-31 02:16:25.865
|
(chore): Resolve !235 feedback (I)
| null | 5 |
10,171,263 | 23,328,594 |
2019-07-30 23:15:25.009
|
(fix): Campaigns entities should not be bypassing ACL
| null | 2 |
10,171,263 | 23,327,607 |
2019-07-30 21:38:35.726
|
(feature) extend the front end to handle infinite feeds for groups
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 5 |
10,171,263 | 23,327,587 |
2019-07-30 21:37:13.866
|
(feature) Extend the front end to handle infinite feeds for the newsfeed
| null | 2 |
10,171,263 | 23,327,568 |
2019-07-30 21:35:43.222
|
(feature) Extend the limit on group items to support infinite (just like a user's own feed)
|
Here's the feedback from the squad leaders on the current situation
Emi: There's a 150 posts hard limit on feeds right now.
Emi: We should workaround something for user's own feeds
Emi: because it seems that people like to scroll to the bottom of their own channel
Mark Harding: own channels is infinite now, newsfeed should be able to copy that logic easily
Emi: ah!, but I think they're mostly complaining about that for their own feeds and groups
Let's verify that there's more than a 150 posts on a user's own channel and then apply those changes to the back end
| 1 |
10,171,263 | 23,327,540 |
2019-07-30 21:33:41.838
|
(feature) Extend the limit on newsfeed items to support infinite (just like a user's own feed)
|
Here's the feedback from the squad leaders on the current situation
Emi: There's a 150 posts hard limit on feeds right now.
Emi: We should workaround something for user's own feeds
Emi: because it seems that people like to scroll to the bottom of their own channel
Mark Harding: own channels is infinite now, newsfeed should be able to copy that logic easily
Emi: ah!, but I think they're mostly complaining about that for their own feeds and groups
Let's verify that there's more than a 150 posts on a user's own channel and then apply those changes to the back end
| 10 |
10,171,263 | 23,326,880 |
2019-07-30 20:53:05.209
|
(refactor): Feeds should have a upper @timestamp bound to avoid showing scheduled posts
| null | 8 |
10,171,263 | 23,326,854 |
2019-07-30 20:52:29.987
|
(refactor): Blogs, images and videos should inherit time_created from it's parent activity.
| null | 5 |
10,171,263 | 23,326,799 |
2019-07-30 20:51:32.536
|
(refactor): time_created can be passed from client when creating/editing
|
If less than 5 minutes, it should be set to time(). If more than 3 months it should throw an exception. time_sent will be time().
| 4 |
10,171,263 | 23,326,743 |
2019-07-30 20:50:18.117
|
(feat): Add time_sent to Activity/Blog/Image/Video.
| null | 4 |
10,171,263 | 23,325,157 |
2019-07-30 19:39:35.752
|
(fix): Ensure /fetch doesn't serve revoked/rejected/completed boosts (basic/campaigns)
| null | 3 |
10,171,263 | 23,325,079 |
2019-07-30 19:38:38.113
|
(feat): Payments delegate onConfirm should check all other payments to ensure budget covers the whole campaign
| null | 5 |
10,171,263 | 23,324,971 |
2019-07-30 19:37:36.270
|
(feat): Validate all payments on validatePayments method at Payment delegate
| null | 5 |
10,171,263 | 23,324,917 |
2019-07-30 19:37:01.276
|
(fix): Payment delegate onUpdate should act agains campaign (not campaignRef) with new payments merged in
| null | 5 |
10,171,263 | 23,324,796 |
2019-07-30 19:35:32.547
|
(chore): Check engine date validation logic
|
Creation: start cannot be in the past; end cannot be more than 1 month from start
Updating:
- If pending/created: start cannot be in the past; end cannot be more than 1 month from start
- If already running: start cannot be changed; end cannot be more than 1 month from start
| 4 |
10,171,263 | 23,324,699 |
2019-07-30 19:32:26.003
|
(feat): Implement lifecycle notifications to campaign owners
|
On creation, payment confirmation/failure, cancel, reject and completion
| 3 |
10,171,263 | 23,324,687 |
2019-07-30 19:31:28.470
|
Implement daily fulfillment warning calculation (scheduled task)
| null | 8 |
10,171,263 | 23,278,569 |
2019-07-29 19:49:13.226
|
(fix): Delay when reading campaigns from elasticsearch
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 4 |
10,171,263 | 23,271,689 |
2019-07-29 15:56:18.255
|
(bug): Group chat stuck loading
|
<!---
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
Group chats are not loading. Happens in canary and non-canary.
### Steps to reproduce
1. Open a group
2. See its not loading
### Platform information
Reproduced on Chrome / Ubuntu and MacOS.
### What is the current *bug* behavior?
Group chat does not load.
### What is the expected *correct* behavior?
Group chat should load.
### Relevant logs and/or screenshots
```
"StaticInjectorError[l -> l]:
StaticInjectorError(Platform: core)[l -> l]:
NullInjectorError: No provider for l!"
```
### Possible fixes
I see references to the CDN in the logs, need to further investigate.
| 1 |
10,171,263 | 23,269,018 |
2019-07-29 15:06:14.708
|
(fix): implement type filtering on Boost\Campaigns\ElasticRepository
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 1 |
10,171,263 | 23,173,308 |
2019-07-25 22:00:23.385
|
Container endpoint should support sorting algorithms
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 2 |
10,171,263 | 23,173,278 |
2019-07-25 21:58:36.614
|
(feat): Endpoint to return groups owned by a user
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 2 |
10,171,263 | 23,173,115 |
2019-07-25 21:54:07.037
|
(feat): Support uploading transparent images to be used as logo
|
try and upload an unlisted image, and grab the /master version
| 3 |
10,171,263 | 23,166,803 |
2019-07-25 17:23:33.577
|
(feat): Pro settings
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 4 |
10,171,263 | 23,161,015 |
2019-07-25 14:03:56.192
|
(feat): new v2/feeds/channel endpoint
|
Will try to load the channel's content from top. If that feed is empty, it will load latest.
| 3 |
10,171,263 | 23,131,895 |
2019-07-24 20:14:35.414
|
(fix): Campaign not starting as soon as payment is confirmed
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 2 |
10,171,263 | 23,128,042 |
2019-07-24 17:38:22.693
|
Divert embeded youtube videos to the modal
|
- [ ] Avoid boost rotator glitch by launching youtube videos inside the modal
- [ ] Ensure it is still only 2 clicks. When the modal launches the iframe should be ready. (Do not use autoplay though as this causes issues with metrics).
- [ ] E2E test
| 2 |
10,171,263 | 23,120,642 |
2019-07-24 15:08:39.101
|
(chore) Refactors to support PHP 7.3
|
If you upgrade to php@7.2, phpspec will start failing because Minds\Entities\Object is now a reserved word. It won't even compile.
There are various additional errors that need resolving to upgrade to PHP 7.3...
* Use of `continue` in `case` statements that need replacing with either `break` or `continue 2`
* method signatures of classes that are extending an abstract class where the new method signatures do not match the method signatures of the abstract
| 2 |
10,171,263 | 23,115,980 |
2019-07-24 12:54:04.295
|
(chore): Enable boost/fetch/campaigns offset cache [after initial testing is done]
| null | 1 |
10,171,263 | 23,115,735 |
2019-07-24 12:46:14.389
|
(fix): Avoid saving "impressions_met" to ElasticSearch on every impression
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 2 |
10,171,263 | 23,115,677 |
2019-07-24 12:44:00.854
|
(fix): Refund payments fractions are rounded down
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 3 |
10,171,263 | 23,095,853 |
2019-07-23 21:24:47.324
|
(chore) Fixes for *lots* of blocking and non-blocking errors in dev environment
|
Too many to list them all, going to commit each individually with a description of what it's fixing.
| 2 |
10,171,263 | 23,091,922 |
2019-07-23 17:52:10.369
|
(feat): elasticsearch script for boost views prorating
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 10 |
10,171,263 | 26,162,926 |
2019-07-22 17:32:39.124
|
Moderation queue number incorrect & posts duplicating.
|
<!---
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 you are a moderator of a closed group, when you've approved all of the posts, you will likely see one or two still remaining, that you are unable to approve, as they are not in the queue. You will also see that some posts that you have already approved, are duplicate in the feed, one approved entity, one unapproved, with nothing in the moderation queue.
### Steps to reproduce
Requires that you are a group moderator of a closed group.
### Platform information
Cross-platform web
### What is the current *bug* behavior?
Queue will show posts awaiting approval that are not
### What is the expected *correct* behavior?
Queue should show empty if there are no posts to approve, furthermore posts should not be getting duplicated.
### Relevant logs and/or screenshots
Video at this link
https://www.minds.com/newsfeed/999958056778829824
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
| 1 |
10,171,263 | 23,056,272 |
2019-07-22 16:30:00.810
|
(fix): api/v2/entities returns error 500 on boost campaigns branch
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 2 |
10,171,263 | 23,009,419 |
2019-07-19 20:19:41.648
|
(bug): Plus not working locally
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 2 |
10,171,263 | 23,000,359 |
2019-07-19 13:42:56.516
|
(fix): fixes for boost campaigns
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 5 |
10,171,263 | 22,999,783 |
2019-07-19 13:20:01.695
|
(bug) endpoint api/v2/entities is not returning description for H&S group
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 2 |
10,171,263 | 22,974,972 |
2019-07-18 17:44:18.326
|
(feat): Change runners to facilitate new Minds Plus features
|
Preparing the runners for the change in Minds Plus for https://gitlab.com/minds/engine/issues/578
| 3 |
10,171,263 | 22,970,724 |
2019-07-18 15:10:22.156
|
(feat): adapt v2/boost/fetch/campaigns with new code from v2/boost/feeds
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 3 |
10,171,263 | 22,969,928 |
2019-07-18 14:44:53.416
|
(feat): Handle session cookies on Pro domains
| null | 5 |
10,171,263 | 22,969,901 |
2019-07-18 14:44:02.857
|
(refactor): Update Router CORS to support main minds domain, plus the current (sub)domain if Pro.
| null | 8 |
10,171,263 | 22,969,865 |
2019-07-18 14:43:05.897
|
(feat): Core Module for Pro metadata and customization values.
|
Repository table dynamic data serialized with json_encode. User GUID should be the primary key. Materialized view with domain as key for lookups.
| 4 |
10,171,263 | 22,969,750 |
2019-07-18 14:39:24.913
|
(feat): User entity flag for Pro
|
Timestamp to be compared with time(). Create helper methods.
| 2 |
10,171,263 | 22,966,338 |
2019-07-18 13:08:23.831
|
(bug) gathering-heatbeat markers arrive at the client with an unsafe integer value for user_guid
|
gathering-heartbeat markers are received with unsafe integer values where guid entities are sent as strings
```json
{
"user_guid":994952798468575247,
"entity_type":"group",
"entity_guid":"997822291385520137",
"marker":"gathering-heartbeat",
"updated_timestamp":1563367071,
"disabled":false,
"read_timestamp":null
}
```
This gives unexpected results if the value is use in Javascript
| 1 |
10,171,263 | 22,912,881 |
2019-07-17 09:01:43.513
|
(feat): Sending a daily notification about the total rewarded tokens in the previous day and allow the user to click and see the breakdown.
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 10 |
10,171,263 | 22,846,866 |
2019-07-16 16:31:25.374
|
(bug): notifications guid field is null
|
Endpoint /api/v1/notifications/...
| 2 |
10,171,263 | 22,808,736 |
2019-07-15 15:16:18.794
|
(test): Engine spec tests
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 2 |
10,171,263 | 22,743,484 |
2019-07-12 16:58:05.178
|
(chore) refactor activity links into a Propagate action
|
We're doing a lot of this.
https://gitlab.com/minds/engine/blob/master/Core/Feeds/Firehose/Manager.php#L106
`foreach ($this->db->getRow('activity:entitylink:'.$entity->getGUID()) as $parentGuid => $ts) {`
Because blogs contain links to activities when they get published. Images and videos contain multiple links to activities (one image to many activities). Yet, we have properties like NSFW, NSFW_LOCK, allow_comments ... etc that need to be propagated up and down the chain
So, when an owner or admin changes a property that applies to parents or their children, we need to create an action that applies those changes up and down the chain.
There's a question of source of truth. If there is a collision between a flag, who should win - the parent object or the object receiving the change?
Part of this card will be figuring out what flags need to be set and how they should be propagated.
Ideally, @markeharding wants them all to be activities with the attachments just inheriting the activities permissions, so we might want to take the opportunity to bring all our entities under the same banner. The activity has the permissions, the images, videos and blogs would just inherit their parent's permissions.
Looping in @markeharding @edgebal and @gthouret for their thoughts on how to roll this out.
| 10 |
10,171,263 | 22,707,889 |
2019-07-11 15:55:20.819
|
(refactor): boost campaigns rating should be calculated via nsfw
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 1 |
10,171,263 | 22,676,918 |
2019-07-10 17:33:07.211
|
(feat): Implement refunds [BC]
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 8 |
10,171,263 | 22,676,686 |
2019-07-10 17:19:59.997
|
(feat): Boost campaigns metrics and impressions
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 6 |
10,171,263 | 22,645,731 |
2019-07-09 19:52:27.018
|
(feat): Test notification for completed referral
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 5 |
10,171,263 | 22,604,489 |
2019-07-08 15:13:01.990
|
Backend for accepting subscription requests
|
Create an api for requesting subscriptions to a channel
---------
**GET** `/api/v2/subscriptions/incoming`
> Gets a list of all pending subscription requests
**PUT** `/api/v2/subscriptions/outgoing/{{channel_guid}}`
> Creates a new subscription request for a user
> Sends out a push notification to the channel owner that a new subscription request has been created
**DELETE** `/api/v2/subscriptions/outgoing/{{channel_guid}}`
> Deletes a subscription request made
**PUT** `/api/v2/subscriptions/incoming/{{channel_guid}}/accept`
> Accepts a new subscription request for a user, assigns them the subscriber role for that channel guid
**PUT** `/api/v2/subscriptions/incoming/{{channel_guid}}/decline`
> Denies a new subscription request
| 3 |
10,171,263 | 22,604,198 |
2019-07-08 15:05:49.506
|
(feature) Limit the feeds for channels to subscribers only
|
When a user marks their channel as closed, we must update the feeds to only show to subscribers.
All posts in the feed will need to be marked with open and closed
Changing a channel's open or closed endpoint will need to reindex the channel
When a user requests a channel, we will need to provide a list of all channels they are subscribed too
We will need to exclude any entity which belongs to a closed channel that they do not subscribe too
| 15 |
10,171,263 | 22,603,819 |
2019-07-08 14:53:52.971
|
(feat) Implement api for marking channels closed or open
|
Under the permissions module, extend the manager to be able to mark entities closed or open.
api/v2/permissions/channels/{guid} with { open, moderated, closed }
Set an attribute on the entity itself
The rbac permissions system will use this flag to determine whether or not subscribers and views can see and interact with this post
| 5 |
10,171,263 | 22,603,724 |
2019-07-08 14:51:08.746
|
(feat) Implement delete flag with the new permissions scheme
|
Since our delete permissions are combined with editing permissions, this is an excellent place to start and role out the new RBAC permissions scheme.
Wherever we check for delete permissions, use the new role based stuff to calculate. When we look up an entitie's ownership, use RBAC to assign owner permissions. This will only have to get overridden by the admin roles and the group ownership roles
| 5 |
10,171,263 | 22,603,600 |
2019-07-08 14:47:15.231
|
(feat) Implement Zend RBAC framework for managing role based permissions
|
In the Permissions Module, create a Roles namespace
Create roles for:
Admin
Moderator (user community folks with moderation privileges)
Owner (can own channels, groups or entities)
Subscriber (can subscribe to groups or channels)
Blacklisted (cannot see or interact with content)
Viewer (default permissions)
Track entity to role relationships
Admins are global, they have full permissions
Moderators are global, but they have limited permissions
Owners are associated to channels, groups or entities and have administrative privileges over things they own
Subscribers get permissions controlled by the owner
Permissions that can be assigned by roles (will grow over time)
canView
canDelete
canComment
canTag
canEdit
canBlacklist
canBlock
TBD: flesh out individual permissions
Create admin endpoints under
/api/v2/permissions/users/{user guid}
GET Gets the user's permissions object, all roles, subscriptions,
| 20 |
10,171,263 | 22,608,137 |
2019-07-07 19:54:34.333
|
(bug): User images missing
|
<!---
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
https://www.minds.com/newsfeed/994094451015606272
A users images are not appearing correctly on the sidebar on a users profile, and in the images.
### Steps to reproduce
1. Visit https://www.minds.com/QuiteJane
2. Look at images (there should be many)
Note that the first time I did this, I could see all of her images fine. After going back and forth a few times, all dispeared.
### Platform information
Cross platform on web only. (tested Android S7 edge on v3.7.2)
### What is the current *bug* behavior?
The images are not there.
### What is the expected *correct* behavior?
Her images should be visible.
### Relevant logs and/or screenshots
# The first attempt:
# After clicking around, they disappeared.
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
| 5 |
10,171,263 | 22,551,287 |
2019-07-05 14:54:51.908
|
(feat): v2/boost/fetch/campaign that returns boosts' and campaigns' urns && ownerGuid
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 5 |
10,171,263 | 22,551,157 |
2019-07-05 14:51:35.104
|
(bug): 500 error on editing blog activities text in newsfeed
|
<!---
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
Changes to the activity of a blog are not saving. Checking the dev tools reveals a 500 error is at fault.
### Steps to reproduce
1. Post a blog.
2. Try to edit the test on your wall.
### Platform information
Reproduced Chromium / Manjaro
### What is the current *bug* behavior?
Changes do not save.
### What is the expected *correct* behavior?
Changes should save.
### Relevant logs and/or screenshots
)
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
| 1 |
10,171,263 | 22,551,004 |
2019-07-05 14:45:08.404
|
(feat): Offchain 3 pending boost limit.
|
Pending merge of https://gitlab.com/minds/engine/merge_requests/251 to avoid conflict
Chats with @IanCrossland and @javanick suggested that we put a pending boost limit of 3 boosts, to stop users spamming the queue with 1 token boosts, and also so that people cannot attempt to spam the network to gain overall control over the content being displayed.
| 5 |
10,171,263 | 22,533,278 |
2019-07-04 19:57:51.079
|
(feat): If state decline expected, trigger event to send notification or email
| null | 7 |
10,171,263 | 22,533,236 |
2019-07-04 19:55:02.706
|
(feat): On user state state change, send a notification and notify of new reward multiplier
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 5 |
10,171,263 | 22,533,221 |
2019-07-04 19:54:01.023
|
(feat): Denormalize the user state on to entities
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 2 |
10,171,263 | 22,533,210 |
2019-07-04 19:53:19.183
|
(feat): Rewards issuance to pull in user state
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 5 |
10,171,263 | 22,489,431 |
2019-07-03 16:27:02.213
|
(feat): Make notifications fire on referral
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 5 |
10,171,263 | 22,489,404 |
2019-07-03 16:25:03.483
|
(feat): Create referrals notification delegate
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 3 |
10,171,263 | 22,489,363 |
2019-07-03 16:21:41.812
|
(feat): Add a notification view for referrals
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 3 |
10,171,263 | 22,482,568 |
2019-07-03 13:25:49.047
|
(chore): Review Ban Snapshot on sandbox (!247)
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 2 |
10,171,263 | 22,481,082 |
2019-07-03 12:41:10.050
|
(feat): Retry queue for ES indexing
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 6 |
10,171,263 | 22,479,737 |
2019-07-03 12:05:14.125
|
(feat): disable VPN restriction for staging server
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 3 |
10,171,263 | 22,478,851 |
2019-07-03 11:31:20.932
|
(feat): Backend - Yearly tier for Minds Plus Initial Endpoint and changes
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 10 |
10,171,263 | 22,478,744 |
2019-07-03 11:26:26.862
|
(feat): Introduce new Messenger table (remove from entities_by_time)
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 10 |
10,171,263 | 22,477,543 |
2019-07-03 10:31:24.288
|
(qa): Webhooks fire on successful payments
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 5 |
10,171,263 | 22,477,499 |
2019-07-03 10:29:20.939
|
(feat): Change 'wire' emails to respect currency
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 10 |
10,171,263 | 22,477,305 |
2019-07-03 10:20:59.555
|
(feat): Reintroduce stripe connect API's
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 10 |
10,171,263 | 22,462,989 |
2019-07-02 22:44:20.944
|
(feat): Queue runner that triggers campaign completion
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 4 |
10,171,263 | 22,462,974 |
2019-07-02 22:43:13.180
|
(feat): CLI Controller that triggers campaign start
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 4 |
10,171,263 | 22,453,673 |
2019-07-02 16:48:22.764
|
(feat) implement fetch from in feeds
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 3 |
10,171,263 | 22,450,359 |
2019-07-02 14:58:46.362
|
(refactor): Hashtags module to use Cassandra. Deprecate CockroachDB.
|
Is this a bug? Make sure to use the Bug template above and be as detailed in your report as possible.
| 10 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.