While I like the idea of its behavioral detection of tracking cookies, and its stats panel is informative, my ultimate problem is that it allows the cookies to be set in the first place. 99.9% of the cookies shoved at my browser are entirely, provably unnecessary -- the page displays the same regardless. As such, my philosophy is that they should never be accepted in the first place, even temporarily.
The cookie request is also a waste of bandwidth. If you're going to display the same page either way, why clog the pipe with a cookie that you're manifestly not doing anything meaningful with?
Set your cookies to request always and prepare for > 30 of them: [
A mere thirty? Lucky you. That's easily manageable; just lean on the ESC key for a few seconds. I've visited sites that tried assaulting me with nearly a thousand for a single page.
Moreover, the allegation that enabling the feature destabilized the browser is pharmaceutically pure bullshit. I've been using the feature since its inception, and have Firefox windows open and running for days at a time without ill effect.
Contrariwise, I just went to check my cookie store, and found a bunch of new, unapproved, unwelcome, provably unnecessary cookies have appeared in just the week since I moved from v43 to v44. Deleting them after the fact is not a solution. Once set, tracking can take place immediately. The damage has already been done.
The proffered reasons for the change are easily shown to be false, so I do not hold out any hope that Mozilla management will have a change of heart on this matter and reinstate the long-standing feature.
Would anyone care to recommend a cookie management add-on?
Current blades are trucked in one piece (per blade) which is impressive to see. Three of them were parked on I-5 outside of Patterson, California a few months ago. There are a lot of net videos and photos which convey the scale.
Even at the current size they can't get through many highway interchanges and local intersections. The larger ones won't be able to ship in one piece at all.
NASA Wind Turbines approached this scale in the '80's. Unfortunately, this was a previously-unexplored area of aerodynamics for NASA, and they had mechanical stress and noise problems (including subsonics) and were all demolished. I think there was one near Vallejo, CA being taken down when I got to Pixar in '87, and one in Boone, NC, which famously rattled windows and doors.
The art has since improved. I took a ride to the top of the turbine at Grouse Mountain, that was fun! That's the only one I have heard of where you can actually get to see it from the top.
This is starting out with the wrong assumptions.
Design a brick system that can be produced with 3-D printers, and will hold together when fabricated within the tolerances of an SLA printer. Forget FDM, it's too low precision and SLA is already achieving an equal or lower cost of manufacture compared with FDM.
LEGO is manufactured to astonishingly high precision, but I am not convinced that this is the only way to make a brick system.
Honestly, given Slashdot's history of trolling -- goatse, gnaa, penis bird, systemd [
You left out Hot Grits and Natalie Portman.
But yes, "performance art" has been a part of Slashdot's history for a very long time.
Life would be so much easier if we could just look at the source code. -- Dave Olson