Re: [Mixxx-devel] Fwd: forum spam

[Sean M. Pappalardo - D.J. Pegasus]

On 07/11/2017 03:37 PM, Aaron Phillips wrote:
> Works for me - we can always revert back to quarantining new users'
> posts again if we get to the stage we were at earlier this year.

Okay, done. Let's see how it goes.

Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist



smime.p7s
Description: S/MIME Cryptographic Signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] Fwd: forum spam

[Aaron Phillips]

Works for me - we can always revert back to quarantining new users' posts
again if we get to the stage we were at earlier this year.

On 11 July 2017 at 23:28, Sean M. Pappalardo - D.J. Pegasus <
spappala...@mixxx.org> wrote:

>
>
> On 07/11/2017 02:48 PM, Aaron Phillips wrote:
> > There is still the occasional post that gets
> > disapproved because it's spam but mostly all of the 'held' posts have
> > been genuine and approved.
>
> I wonder then if we should stop holding new-user posts for approval. The
> few that are spam would be flagged by users and removed when we get the
> chance. This is preferable to delaying legitimate new users' posts,
> especially if that's the majority of them now. Thoughts?
>
> Sincerely,
> Sean M. Pappalardo
> "D.J. Pegasus"
> Mixxx Developer - Controller Specialist
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] Fwd: forum spam

[Sean M. Pappalardo - D.J. Pegasus]

On 07/11/2017 02:48 PM, Aaron Phillips wrote:
> There is still the occasional post that gets
> disapproved because it's spam but mostly all of the 'held' posts have
> been genuine and approved.

I wonder then if we should stop holding new-user posts for approval. The
few that are spam would be flagged by users and removed when we get the
chance. This is preferable to delaying legitimate new users' posts,
especially if that's the majority of them now. Thoughts?

Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist



smime.p7s
Description: S/MIME Cryptographic Signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] Fwd: forum spam

[Aaron Phillips]

Hi all,

Just a quick note to say I am away from home for the next three weeks in a
place I am unlikely to get much internet access, so moderating the forum
will mostly not be possible for me. I would be grateful if other people
with moderation/admin rights on the forum wouldn't mind keeping an eye on
the posts and authorising the new user ones while I'm away - I'll be back
to normal access from 3 Aug.

The spam problem is mostly non-existent now so thanks for addressing this a
few months ago. There is still the occasional post that gets disapproved
because it's spam but mostly all of the 'held' posts have been genuine and
approved.

Many thanks,

Aaron (pi r squared)

On 6 March 2017 at 23:26, Aaron Phillips  wrote:

> Thank you for this, Sean. Hopefully this should contribute hugely towards
> ridding the forums of unsolicited and unwanted messages.
>
> Cheers,
>
> Aaron.
>
> On 6 March 2017 at 22:12, Sean M. Pappalardo - D.J. Pegasus <
> spappala...@mixxx.org> wrote:
>
>> Hello.
>>
>> (Whoops, I forgot to reply to the list!)
>>
>> I have enabled blacklist checking for all users rather than just
>> guests on the forums. Let's see if that helps, or just annoys legitimate
>> users.
>>
>> I also changed the human challenge to use reCAPTCHA. (It was using a
>> basic question before.)
>>
>> While at it, I pruned (deleted) any users with zero posts that haven't
>> logged in in months just to keep things neat and tidy and free up user
>> names. (Thousands were removed!)
>>
>> On 03/06/2017 11:21 AM, Aaron Phillips wrote:
>> > 1) new users' posts are quarantined.
>>
>> This is now enabled. They will see "This message has been submitted
>> successfully, but it will need to be approved by a moderator before it
>> is publicly viewable. You will be notified when your post has been
>> approved."
>>
>> Until that approval happens, their posts will go into the moderator
>> queue. (There's no auto-approve option.)
>>
>>
>> Sincerely,
>> Sean M. Pappalardo
>> "D.J. Pegasus"
>> Mixxx Developer - Controller Specialist
>>
>>
>> 
>> --
>> Announcing the Oxford Dictionaries API! The API offers world-renowned
>> dictionary content that is easy and intuitive to access. Sign up for an
>> account today to start using our lexical data to power your apps and
>> projects. Get started today and enter our developer competition.
>> http://sdm.link/oxford
>> ___
>> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
>> http://mixxx.org
>>
>>
>> Mixxx-devel mailing list
>> Mixxx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>>
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] feature request: Analysis progress

[Uwe Klotz]

I cannot confirm your bug report. Both the analysis progress per track and 
the remaining tracks scheduled for analysis are shown in the UI and updated 
properly in all views. I'm also not able to reproduce any UI freezes during 
batch analysis of mutliple tracks. The analysis is performed in a separate 
(single) thread.


Are you sure that those issues are not caused by your custom build? Please 
test a clean master build and report bugs if you still experience some.


Kind regards, Uwe

On 11.07.2017 02:47, Waylon Robertson wrote:

When doing track analysis via the 'analysis' panel, selecting tracks
and 'Analysis', there is no progress information.

Straight after clicking Analysis, it adds the tracks to the analysis,
and the ui freezes until all the analysis is scheduled, or whatever.
Then it does the Analysis, the ui is then somewhat responsive. There
is, howver, no progress numbers. the only evidence of it working,is
the bpm's changing.

There used to be a done/total to do, counter. doesn't appear anymore.

I make a feature request, that all phases should show progress.

I have no idea how to do a feature request.

Waylon

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] feature request: Analysis progress

[Josep Maria Antolin]

I guess the recent changes to the single-threaded analysis related to the
improvements to database access might have caused it.

The way that part is updating is by signals, and there are several jumps
(from analizer to analyzer queue, from queue to library and from library to
the bar where the button is).
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] Merge library redesign with multitrack analysis

[Josep Maria Antolin]

​Hello.

The multithreaded analysis branch is currently behind the changes. The main
problems are the changes related to the database access, that has been
changed to make it more robust on master.

I am not currently updating it, although I offered myself to help migrating
it, once uwe klotz got ready.

There might be also some small changes here and there on signals and
components that might have changed since, but overall, I don't think there
should be too much work, once the database changes are solved.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Re: [Mixxx-devel] Proper way to update PR's

[Josep Maria Antolin]

Hello.

I believe that you are not getting the correct answer because the question
is not clear.

What I think that you want to do is get your copy up to date, being it a
branch or master.  There is this github page that you should read, although
I will explain it here too:
https://help.github.com/articles/syncing-a-fork/


Having "upstream" as the mixxx repository
Having a fork of master on your github repository
Having branches on your github repository:

First, ensure that your local clone of your repository knows where the
mixxx repository is. To do so, look here:
https://help.github.com/articles/configuring-a-remote-for-a-fork

Then the procedure is:

$ git fetch upstream
$ git checkout master
$ git merge upstream/master

The first command tells git to go and look on the repository configured as
upstream (which you should have configured as I've told above... You can
choose a different name).
The second command tells git to change your working copy to the master.
The third command tells git to merge what is on upstream/master ( which is
supposed to be mixxx master), with your working copy (which is supposed to
be your master).

Depending on the changes, this can be a fast-forward, or you might need to
solve conflicts.

Conflicts are solved by manually editing the files, and once the conflict
has been resolved, git add it  ( This is explained here:
https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/
)


Once you have your master merged, you should push it to github. If you
needed to solve conflicts, you willl need to make a commit too.

($ git commit -m "merge to get up to date")
$ git push


Now, in order to update your branches, you can do so from your master
branch.

$ git checkout my-other-branch
$ git merge master
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel