Author Topic: [WEBSITE v2] MusicBee website and forum redesign  (Read 645391 times)

AvikB

  • Sr. Member
  • ****
  • Posts: 946
is the ADD-ONS page fully functional now?
- "Submit your Add-on" http://test.getmusicbee.com/kb/?code=102#dashboard_submit opens a blank page for me
when ever the url is kb/?code=xxx means something is wrong. And in your case you are not logged in. I haven't build the error page yet. But when it is complete it should show you the error.

- What did you have in mind for "Misc" (i know its for Miscellaneous but not sure what would go in there
Anything that does not fit in other category. I am not add-on developer myself so i don't know what kind of add-on you can build. But it is good have a category that allow other things besides plugin, skin, theater mode, visualizer.

I do have few thing in mind. like maybe language files, equaliser, icons, DSP etc.

- Also would anyone volunteer to create the text for "How to Install Add-Ons" ?
I am planning to do the site specific wikia content. things like, dashboard options, how to upload/submit add-ons, installing things. etc.

for the main home page, overall its great. The only thing I spotted was "Go to Quality Guide". I am happy if someone volunteers to write something generic for this section but its not really something i want to advertise for MusicBee ie. imply that it somehow produces better quality music. Saying that i am fine with the rest of the "Sound Quality Matters" section.
well i will talk about this with psychoadept, and will come up with the content. so don't worry.

AvikB

  • Sr. Member
  • ****
  • Posts: 946
filter for the tab you have selected  I would have noticed the tabs if the results were immediately under them.
I have added selected tab filtering. It should only show the result from the selected tab. Also to make things a bit more clear when a user now make searches a Search tab will be highlighted instead of category tabs, this will make things a bit more clear. Currently it also shows highlight search tab for tags, which will be fixed in future updates.

I will add additional control for searches if needed.

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34985
a couple of bugs with the submit add-ons:
- it doesnt remember the version you enter
- entering this for a thumbnail
http://getmusicbee.com/images/skin_preview/albums_tracks/Beer%20Skin%20(Album%20and%20Track).jpg
results in
http://getmusicbee.com/images/skin_preview/albums_tracks/Beer%20Skin%20(Album%20

if the following is not ready for testing then let me know and i will stop:
also the website control center formatting is not working well - i can post a screenshot if needed
Add a new version! in the same panel returns an error code
Last Edit: March 31, 2016, 07:56:13 PM by Steven

AvikB

  • Sr. Member
  • ****
  • Posts: 946
a couple of bugs with the submit add-ons:
- it doesnt remember the version you enter
Ah it seems i messed the html little bit :P, it should be fixed now. update pushed.

- entering this for a thumbnail
http://getmusicbee.com/images/skin_preview/albums_tracks/Beer%20Skin%20(Album%20and%20Track).jpg
results in
http://getmusicbee.com/images/skin_preview/albums_tracks/Beer%20Skin%20(Album%20
i have made some changes to allow large urls for database. BUT it still won't show on addon page as the url contains brackets. I am looking into this issue.

AvikB

  • Sr. Member
  • ****
  • Posts: 946
if the following is not ready for testing then let me know and i will stop:
also the website control center formatting is not working well - i can post a screenshot if needed
Add a new version! in the same panel returns an error code
yes as i mentioned above the control center will be removed and will be added to dashboard.


Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34985

hiccup

  • Hero Member
  • *****
  • Posts: 9133
This is a thought about the proposed system to approve Add-ons before they will be published.

A possible problem I see with that implementation is that it is not certain that every posted add-on can, and will be evaluated by a moderator. This could be because the mod(s) don't own a required hardware device, or might simply not be interested or motivated to install that particular plugin to test it.
But I support and understand the idea behind it, this trying to prevent malicious or nonsense postings of add-ons.

I suggest another approach for this.

Make it mandatory to post an introductory- and explanatory post, including the download link in the forum.
Implement a standard delay of e.g. 48 hours before an added plugin is visible for normal users.
That will give it a valid period for the plugin to be screened at least a little bit with the help and feedback from the community.

If after these 48 hours passed, the plugin has not been reported to be malicious or nonsense, nor by forum posts, nor by a report to the mods, it will become visible in the download area automatically.

The worst that might happen, is that a malicious/nonsense add-on is posted, that it is not responded to by anyone in these 48 hours, and gets published automatically.

I have another suggestion that might help to cover that (rather unlikely) possibility, namely by giving each and every published add-on a visual indicator (I can't find the right word, 'stamp?') naming it 'unverified', just explaining that it has not yet been tested for functionality or viruses.

The mods will be able to see a list of yet unverified add-ons, and can remove that 'unverified tag' either by own assessment, by responses from forum members, or after  personal note or request from the creator of that add-on. It would also allow for bypassing the 48hours waiting time.

I believe such a system would also be much easier for the mods to handle than trying out and test all add-ons by themselves.

AvikB

  • Sr. Member
  • ****
  • Posts: 946
A possible problem I see with that implementation is that it is not certain that every posted add-on can, and will be evaluated by a moderator. This could be because the mod(s) don't own a required hardware device, or might simply not be interested or motivated to install that particular plugin to test it.
But I support and understand the idea behind it, this trying to prevent malicious or nonsense postings of add-ons.
The verification is to prevent spams, and also floodgate. i do trust the community for providing quality addons without malicious intent. But ofc, humans are complicated and it is not easy to trust them by nature.

I suggest another approach for this.

Make it mandatory to post an introductory- and explanatory post, including the download link in the forum.
Don't you think that is a bit of stretch! And besides it will require a human to verify the forum post. I have made support/discussion link mandatory for addons that are beta. but to make it fully mandatory might be too much. ofc if others agrees i will make the changes otherwise i would prefer not to.

Implement a standard delay of e.g. 48 hours before an added plugin is visible for normal users.
That will give it a valid period for the plugin to be screened at least a little bit with the help and feedback from the community.

If after these 48 hours passed, the plugin has not been reported to be malicious or nonsense, nor by forum posts, nor by a report to the mods, it will become visible in the download area automatically.

The worst that might happen, is that a malicious/nonsense add-on is posted, that it is not responded to by anyone in these 48 hours, and gets published automatically.

I have another suggestion that might help to cover that (rather unlikely) possibility, namely by giving each and every published add-on a visual indicator (I can't find the right word, 'stamp?') naming it 'unverified', just explaining that it has not yet been tested for functionality or viruses.
Currently unverified add-ons are completely invisible to users BUT they can still access them if they got direct link.

All non-verified addon will show warning. They are invisible but if someone visit them by direct links the addon page will show warning.


If an addon is rejected the download link won't show. only the warning message. Members can re-submit rejected add-ons for re-verification.


and if an addon is soft deleted(mods can only soft delete, only admin can permanently delete them or they will be automatically deleted in a week/days by server) they will throws a red error. admin/mod will be able to undelete as well.


The mods will be able to see a list of yet unverified add-ons, and can remove that 'unverified tag' either by own assessment, by responses from forum members, or after  personal note or request from the creator of that add-on. It would also allow for bypassing the 48hours waiting time.

I believe such a system would also be much easier for the mods to handle than trying out and test all add-ons by themselves.
mods/admin can see non verified addons and approve them, soft delete, reject them.


You can currently sort YOUR OWN SUBMITTED addons by status


 I am also working on moderator and admin center now, it will bring some extra features for mods as well. Viewing all deleted, rejected, waiting for approval is also coming for mods as well.

I like the idea of involving community to vote for safe and unsafe addons. It sounds like steam greenlight. :)
But ofc it can also have some negative effect aswell, like users reporting an safe addon as virus just for fun or maybe their shitty antivirus said so. or maybe spam addons got accepted because mods were not online for 48hours or so.

AvikB

  • Sr. Member
  • ****
  • Posts: 946
Also if needed i can implement disqus comment. ofc someone need to mod them as well. :S

hiccup

  • Hero Member
  • *****
  • Posts: 9133
Also if needed i can implement disqus comment. ofc someone need to mod them as well. :S

Then we would have three locations for discussions at the forum, at the wikia, and at your add-ons pages.
Probably not a good idea...

hiccup

  • Hero Member
  • *****
  • Posts: 9133
A possible problem I see with that implementation is that it is not certain that every posted add-on can, and will be evaluated by a moderator. This could be because the mod(s) don't own a required hardware device, or might simply not be interested or motivated to install that particular plugin to test it.
But I support and understand the idea behind it, this trying to prevent malicious or nonsense postings of add-ons.
The verification is to prevent spams, and also floodgate. i do trust the community for providing quality addons without malicious intent. But ofc, humans are complicated and it is not easy to trust them by nature.

I suggest another approach for this.

Make it mandatory to post an introductory- and explanatory post, including the download link in the forum.
Don't you think that is a bit of stretch! And besides it will require a human to verify the forum post. I have made support/discussion link mandatory for addons that are beta. but to make it fully mandatory might be too much. ofc if others agrees i will make the changes otherwise i would prefer not to.

Implement a standard delay of e.g. 48 hours before an added plugin is visible for normal users.
That will give it a valid period for the plugin to be screened at least a little bit with the help and feedback from the community.

If after these 48 hours passed, the plugin has not been reported to be malicious or nonsense, nor by forum posts, nor by a report to the mods, it will become visible in the download area automatically.

The worst that might happen, is that a malicious/nonsense add-on is posted, that it is not responded to by anyone in these 48 hours, and gets published automatically.

I have another suggestion that might help to cover that (rather unlikely) possibility, namely by giving each and every published add-on a visual indicator (I can't find the right word, 'stamp?') naming it 'unverified', just explaining that it has not yet been tested for functionality or viruses.
Currently unverified add-ons are completely invisible to users BUT they can still access them if they got direct link.

All non-verified addon will show warning. They are invisible but if someone visit them by direct links the addon page will show warning.

If an addon is rejected the download link won't show. only the warning message. Members can re-submit rejected add-ons for re-verification.

and if an addon is soft deleted(mods can only soft delete, only admin can permanently delete them or they will be automatically deleted in a week/days by server) they will throws a red error. admin/mod will be able to undelete as well.

The mods will be able to see a list of yet unverified add-ons, and can remove that 'unverified tag' either by own assessment, by responses from forum members, or after  personal note or request from the creator of that add-on. It would also allow for bypassing the 48hours waiting time.

I believe such a system would also be much easier for the mods to handle than trying out and test all add-ons by themselves.
mods/admin can see non verified addons and approve them, soft delete, reject them.

You can currently sort YOUR OWN SUBMITTED addons by status

 I am also working on moderator and admin center now, it will bring some extra features for mods as well. Viewing all deleted, rejected, waiting for approval is also coming for mods as well.

I like the idea of involving community to vote for safe and unsafe addons. It sounds like steam greenlight. :)
But ofc it can also have some negative effect aswell, like users reporting an safe addon as virus just for fun or maybe their shitty antivirus said so. or maybe spam addons got accepted because mods were not online for 48hours or so.

It is just a thought, coming up after the notion this 'approval' dashboard might be some overkill for MB, and be needing a bit too much mod-interaction.
But it seems you are thinking this over very seriously, so let's just wait and see how this plays out in the real world later.

boroda

  • Hero Member
  • *****
  • Posts: 5249
actually during several years there were no malicious addons published, so i wouldn't care too much about this.

hiccup

  • Hero Member
  • *****
  • Posts: 9133
actually during several years there were no malicious addons published, so i wouldn't care too much about this.

You are right, but I am a bit worried about spam-bots getting more and more advanced.
They already started to enter the gates of the new forum, and I was wondering if something similar might happen with posting files, instead of just texts.

Last year something like this actually happened with the fake (and malicious) MusicBee app on Microsofts' own Store website.

AvikB

  • Sr. Member
  • ****
  • Posts: 946
It is just a thought, coming up after the notion this 'approval' dashboard might be some overkill for MB, and be needing a bit too much mod-interaction.
But it seems you are thinking this over very seriously, so let's just wait and see how this plays out in the real world later.
I don't think it is too much of overkill. It is pretty simple. Three actions, approve, delete and reject.
all of them are one click solution. No complicated checkboxes or so.