As for taxes, people on Mann get screwed over on prices - everything from groceries to petrol is more expensive than the north of England since it has to be shipped in. The tax breaks for residents are less than for corporations too, without the corporate breaks I think there would be less work there in general. Might get rid of the southern English bankers that all moved there in the 2000s if they removed so many incentives so it wouldn't be a complete loss ;-)

A lot of Java programs ship jar files in their source tarballs, it has traditionally been a lot of work for Debian devs to pick these apart. Similarly, many "things" (programs or web services) that use javascript libraries often ship minified versions of common stuff like jquery rather than use the system version. It's quite a mess. I think a lot of it stems from the fact that traditionally these sorts of libraries (jars, javascript) have not been well packaged or even packaged at all. The program authors are making life easier for the majority by shipping all the deps together. It's not good for distros, but I can see the advantage.

I think subversion has a nice work around for this - they include a script to download the dependencies if you need them, otherwise the default is to link vs system deps.

I wouldn't worry about it - the clones will probably not go anywhere and just die off, abandoned. True they don't link back to your now-canonical repo. As viraptor said, maybe contact the users. They might prefer to fork your repo now it's on github.

Mozilla currently don't provide a dev build for Android, just regular and beta versions https://play.google.com/store/apps/developer?id=Mozilla

The security problem that this "fixes" is not really an issue on Android due to Android's own app sandboxing, so maybe the Android build will allow unsigned extensions? It's not mentioned in the FAQ.

First, it uses CMake to build - for a long time Google projects had seemed pretty anti-CMake (for example using gyp, plain Makefiles or autotools) so it's nice to see them using CMake. IMO it's the best build tool, though all build tools generate various levels of hate :-)

Second it's another Google project that generates good developer docs from source code using doxygen and markdown. These docs look good on github directly (https://github.com/google/flatbuffers/tree/master/docs/sourc...) as they are markdown, and even better on the dedicated site where they have custom css.

If I were to write a C++ library, I'd definitely copy these 2 approaches.

However, the podcast feed is impossible to find now if you didn't have it before. Previously I think it was on every podcast post as an RSS link. Now the individual tag RSS links all point to the main feed, rather than to a per-tag feed.

e.g. http://blog.stackoverflow.com/category/podcasts/feed/ still works if you know it, but going to https://blog.stackexchange.com/tags/podcasts/ gives you an RSS link to just "/feed/".

This is probably not a good place for bug reports :-S

It's harder to explain than to use actually. Ah! there's a bit of a wrinkle with gerrit in that it uses a local hook to insert an ID into commits, so rebasing or cherry picking knows which commit to reference. But that might be optional, it'd be like cherry-picking a pull request, I think github doesn't close the original in that case? Not sure on that though.

The new sets do have a few weird "only for that set" bricks, like batman helicopter blades or weird rubber Jedi hair pieces, but generally everything still fits together with everything else. I will say that there does seem to be a high percentage of small round 1x1 transparent studs. Every set seems to come with loads of 'em.

It works here with Firefox+noscript, but in w3m it messes up when you read an article and forces you to a "need JS" page. I might have added some other hack somewhere in FFx ages ago to get groups working that I've forgotten about.

I can see why Google specify this since a store filled with spammy apps wrapping popular sites would be bad for everyone. But this puts the kibosh on privacy-focused apps like Tinfoil for Facebook or the Twitter equivalent, and bloat-reducing apps like the OP's. I imagine that these have yet to be suspended simply because nobody at Google has noticed them.

Here is an explanation from the mailing list, so at least Mozilla are aware of the issue. https://groups.google.com/forum/?_escaped_fragment_=msg/mozi...

> The reason for this is because gecko determines how the user interface > (implemented in the gaia layer) actually behaves. There may be bugs in future > versions of gecko that break parts of the UI, and the carriers/manufacturers > understandably don't want to just push these updates without verifying them > first.

It's an easy fix, just add the line, otherwise 0755 scripts with no #! do execute using the current shell.