That's a great idea if the injected ads are exactly the same length and always get put in the same place. If you have a 30 second ad in one download and 40s in another, 10 seconds of legitimate podcast audio gets interpreted as an advertisement.

It works even if they don't, you just need a more intense algorithm to do similarity matching across all offsets.

With maximally repeated sequences, you can https://ieeexplore.ieee.org/abstract/document/6012115

You "just" need to find all the common segments between different downloads; those are very likely to be the actual content, and not differing ads. Naturally this doesn't work very well if the pool of ads is low and you get repeats.

Not to mention all of the extra analytics that it collects and submits to a google analytics account

> automagically have the user who posted it add a thumbs up to the original issue.

I was astonished that they didn't do this when they introduced the emoji reactions feature.

Part of the problem is deciding what the +1 should be attached to. Some people comment +1 just because they want to see a PR merged. Some +1s are intended to be associated with a specific comment.

But there's other systems for that; what you're describing are 'bumps' that have been in forums and such for forever now, and I'm sure that e.g. an upvote system (or sort by +1 reactions) would replace that system.

I think it could be done on a per repository basis, like, basic behaviour rules just like at forums and other such communities. It's then up to the maintainer / moderators / whatever to allow or disallow +1-style comments, and what the 'punishment' would be. They could then also tweak a setting that auto hides comments if they're shorter than X characters.

You can sort by reactions on the issues list, if that’s what you meant.

Is there a way to migrate a repo from Bitbucket Server into gitlab preserving pull request history?

There is a lack of APIs from bucket to allow that kind of operation. You should consider the lockin each platform have, before jumping in

Wow, you really need to be in less slack teams...

That memory footprint is inexcusable even if he were literally on one thousand Slack teams. Functionally, Slack is more or less a shiny wrapper on IRC, and you can run dozens of IRC channels in a few megabytes, if that.

That's no excuse for 17GB of memory usage...

Did you know that Slack itself is also written in PHP?

https://twitter.com/SlackHQ/status/426469205005705217

Note that this tweet clarifies that P stands for PHP and not Python or Perl: https://twitter.com/SlackHQ/status/499432194398756864

I once got a spam message like this about a repository that i _starred_. I made no commits, opened no issues, just starred!

> This article originally appeared as a guest post on Auth0’s blog.

um...

That blurb was added later.

The site lets you download the app, run the app, log in to GitHub, and _THEN_ asks you for a beta invite code. There's almost no info about it on it's homepage, so why post the link at all?

Came here to say this. I'm rather annoyed at the bait-and-switch here.

Flask-RESTful currently has its own serializer module, but we have plans to deprecate it in the future and replace it with Marshmallow[1]

[1]: https://github.com/flask-restful/flask-restful/issues/335

I'm developing a system that, among other things, could be an even more minimalist alternative to Marshmallow [0]. I actually haven't seen Marshmallow until now, it looks very nice.

[0] http://teleport-json.org/