Slashdot is powered by your submissions, so send in your scoop


Forgot your password?

Comment Re:Returns? (Score 1) 102

Previously it was a stand-alone app that would act as a proxy and filter out ads from all traffic. That was yanked from the store since it "interfered with operations of other apps". To some extent, that's a fair accusation.

Now, a FF plugin affecting only FF or a standalone browser are okay by this criterion, so it's "back" in this form.

Comment BlinkyTape or a similar LED installation (Score 3, Interesting) 133

You could look into LED decoration. For example, BlinkyTape - a LED strip with an attached Arduino-compatible controller.

It can be just decoration, or you can use it for light painting.

Of course, you can build your own LED-based contraption.

Comment A gem from the discussion (Score 2) 324

I fully support this proposal. In addition to APIs, I'd like to propose prohibiting caching any resources loaded over insecure HTTP, regardless of Cache-Control header, in Phase 2.N. The reasons are:
1) MITM can pollute users' HTTP cache, by modifying some JavaScript files with a long time cache control max-age.
2) It won't break any websites, just some performance penalty for them.
3) Many website operators and users avoid using HTTPS, since they believe HTTPS is much slower than plaintext HTTP. After deprecating HTTP cache, this argument will be more wrong.

I'm sure the users will appreciate the extra traffic!

I can see 1 being a thing, but 2 is a penalty for the end-user on metered connections, and 3 is an argument for "Mozilla is much slower than [insert browser here]".

FORTUNE'S FUN FACTS TO KNOW AND TELL: A firefly is not a fly, but a beetle.