The bees coat the plastic with their own wax, thus sealing the cells. When you harvest, the cells are split releasing the honey. Honey contact with plastic is minimal and only happens during harvest.
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
iOS has had per-app data counters for a very long time. (settings:cellular -- see the number under the app name? see the toggle to the right? see the "System Services" at the bottom?) Granted, *you* have to reset it every month.
Compared to??? The person who threw it away either didn't know Sears would replace it, or was simply too lazy to take it back. Doesn't matter how it broke, who owns it, or who returns it; when it's presented to them, it gets replaced. We're paying for quality that doesn't break in the first place, and when you do manage to break it (arc the tip off a screwdriver, snap off a ratchet using a 6ft pipe...) they replace it, no questions asked.
I want my cables to work, thanks.
It's simply too easy these days to go on the internet and find a dozen sources that sell boxes of various cables for peanuts. The appeal of RS was being able to get odd electronic parts immediately. These days, they barely have anything -- and 95% of it is available everywhere.
I think that's all about costs. Notice how everything is being done at M5 (and the completely over-the-top gratuitous shots of the M5 sign) now. The show used to have it's own shop.
Really? A boiled peanut is a Boiled. Peanut. (still in the shell. vs. the common tin can of shelled, roasted crap from Planters.)
a) sizeof(some pointer) will not tell you the size of what it points to
b) the error here is allocating space for 3 things and putting 4 in it. It doesn't matter what function you call if you tell it to copy sizeof(void *) too much.
The error is a simple mistake due to unnecessarily complex code.
... until their metasploit code is published and everyone can see how to use this error. All it takes is one example; ONE person figures out how to trigger shellcode, and it's game over. No matter how complex the situation, an exploit is an exploit. It doesn't matter if it takes 87 steps to set off a nuke, if you know those steps and complete them - *boom*.
Either you write very little code, very simple code, or no one is closely inspecting your code. People make mistakes - period.
This glibc error was a simple mistake... count 3 things, put 4 in there. But yes, if their code weren't in such a f'ing complicated mess (have these fools never head of stuct) this mistake would be harder to make.
Police who commit misconduct of any kind is are the extreme minority.
That we hear about in the national news... we aren't made aware of every bullet fired by officers (there's supposed to be paperwork when they discharge their weapon(s)) or their every infraction
That's a weak deterrent at best. First, criminals are rather stupid. Second, the smarter ones will find an easier target, the dumber ones get more firepower.
BONUS: then it becomes the FBI's problem, not yours.
Or, perhaps, and I'm just puttin' it out there... they use the app themselves. A good sniping position is only good until you're spotted.
Actually, it's usually safer for all if the cops don't show up during the bank heist. That's how hostages get taken and people get shot/stabbed/etc. Plus, if they "get away", it's instantly the FBI's problem. (also, with technology what it is today, few ever totally get away with it.)
And they aren't "patrolling" if they're just sitting there. In legal terms, that's "standing" for us Joe Citizens.