There's just too much volume to track all the content everywhere. That's why they install keyloggers that look for users hitting the Cancel button on posts over a certain length. If people are having second thoughts about something then you know it's the juicy stuff.
I'm imagining a high tech looking front room and lab with a hidden door that leads to a crematorium. You could do it for the bargain rate of $20k per pop (less than the $37k listed in the article) and it would, for all intents and purposes, be the same.
Relationship between bluetooth hosts and bluetooth peripherals is 1:many. Not many:many. One computer, multiple devices (a headset, a mouse, a keyboard). But one device (say a mouse) can only connect to one computer at a time (typically).
Also, getting phones and tablets to output audio to more than one output device isn't easy to configure.
Also, and this one is a bit fuzzier but I seem to recall having trouble using older bluetooth headsets to listen to music on my Blackberry (back when Blackberrys were the thing you had). There are separate standards for bidirectional (headphone and mic) and stereo (A2DP or something). Maybe that's better now. I dunno.
Oh geez that seems like a horrible idea. Seems better to get rid of daylight savings and deal with the fact that light is different at different times of the year.
I could imagine it being more useful as browser based apps become heavier and heavier, you could selectively disable features as the battery gets eaten away. Also, as the mobile world shifts from apps to responsive web pages, you can do the same.
On the other hand, one could argue that the user might want to be in control of how much power a page uses anyhow, so you might as well supply the option. But then one option might be 'go full out when there's lots of juice, drop down a little bit when we're running out'.
I wonder how long you could get an old school Nokia phone (thing monochrome display with only characters) to last these days if you replaced the battery with the exact same weight of current battery technology.
Or, take one of the earlier (say 80286) laptops and do the same.
On the one hand, you are right - as battery technology has improved, we've only increased how much power these devices use. On the other hand, these devices are infinitely more useful than what we had back then and the tradeoff is certainly worthwhile.
It depends... sometimes customers would probably come back and order later. Sometimes they might order somewhere else that is available. Or sometimes they might use the extra time to ponder whether they really need the item and ultimately might decide not to buy it.
If you read the summary this seems to be more related to trademarks than it is to patents.
These seems to be mostly to do with a corps ability to plan marketing material for a product before launching it and still having it be a surprise. Seems reasonable to me, especially for things such as 'Siri' or 'Apple Watch'. Makes things a bit more concrete in a legal sense as well since you don't have some trademark argument in the event somebody tries to swoop in and take it - you haven't registered your intent months before in the other jurisdiction. In the meantime you get your product ready to ship and send it out the door. You get your marketing surprise with your fancy reveal. In the event somebody leaks it you don't have to worry about rushing off to file it.
Seems almost like this should be built into the trademark filing process - the ability to register intent to use a mark and keep it secret for some amount of time (say 3 months or 6 months).
On the other hand, it probably doesn't look good from a legal perspective if you signed a contract with your content providers to stop people from watching from other regions, and then you didn't do due diligence to enforce it, had you agreed to do that.
I was hopeful that Netflix wouldn't really work that hard to enforce this, but it seems that they have. If they are being contractually compelled to do this, and they have agreed to enforce it, then it would be a bad idea to not really do it.
It is likely better for their business to make the content available to all the folks in the US who are within the allowable region and block others, than to not have the content at all and lose all of the US subscribers.
My digitizer did stop working... a while after the screen cracked a little bit I got a new phone and wasn't as careful with guarding the old phone from the little one. The LCD display still works great but the digitizer stopped working.
Looks like they erroneously added www. to the front. They have a wildcard cert for *.slashdot.org but the www.build does not match (wildcards only go one level in domain certs). If you remove the www. from the beginning of the link it works fine. Might explain why it works on the other person's phone as well - mobile version might link differently.
The summary says: "As for whether or not this method will make its way to store shelves, it won't in the near future." This indicates that milk treated using this process is not available on store shelves. But then the summary says: "The product is currently being distributed." So I'm curious as to who they are distributing this milk to and what is being done with it?
You could do your scouting at night to determine where traffic lights are. Probably would make the problem much easier. Though probably is much easier to just make the system work better.
What can happen is including npm install as part of your deployment process. Depending on how tightly you specify your dependencies this could result in packages getting updated to versions that have not been tested with your code by simply redeploying (or maybe somebody has put this in as part of the flex up process, so you end up with new app servers with slightly different code than older app servers.
There are many ways to solve this, but it can get overlooked until you get bitten in the ass and deploy code that isn't what you thought you were because some package dev somewhere released a package upgrade.
Ah, I didn't look that closely to see that. On the other hand, I still wouldn't consider them 'astoundingly efficient' as the headline claims. This article discusses a design for a 97.09% efficient inverter. (I admit at this point I'm beginning to be argumentative, but I still think the headline should have been astoundingly dense inverters, though my theory is that slashdot injects in intentional errors to drive comments and traffics from those who like to nitpick submissions).
Slashdot Mirror
There's just too much volume to track all the content everywhere. That's why they install keyloggers that look for users hitting the Cancel button on posts over a certain length. If people are having second thoughts about something then you know it's the juicy stuff.
It happens all the time because if you've modded a thread the only way to post without reversing the mod is to do so as AC.
They did this with John Wayne too. He's not dead. He's frozen. He's gonna be pissed when they thaw him out.
Yeh... I came here wondering if that would be a clever way to achieve Physician assisted suicide.
I'm imagining a high tech looking front room and lab with a hidden door that leads to a crematorium. You could do it for the bargain rate of $20k per pop (less than the $37k listed in the article) and it would, for all intents and purposes, be the same.
So who got cheated?
Relationship between bluetooth hosts and bluetooth peripherals is 1:many. Not many:many. One computer, multiple devices (a headset, a mouse, a keyboard). But one device (say a mouse) can only connect to one computer at a time (typically).
Also, getting phones and tablets to output audio to more than one output device isn't easy to configure.
Also, and this one is a bit fuzzier but I seem to recall having trouble using older bluetooth headsets to listen to music on my Blackberry (back when Blackberrys were the thing you had). There are separate standards for bidirectional (headphone and mic) and stereo (A2DP or something). Maybe that's better now. I dunno.
Oh geez that seems like a horrible idea. Seems better to get rid of daylight savings and deal with the fact that light is different at different times of the year.
I could imagine it being more useful as browser based apps become heavier and heavier, you could selectively disable features as the battery gets eaten away. Also, as the mobile world shifts from apps to responsive web pages, you can do the same.
On the other hand, one could argue that the user might want to be in control of how much power a page uses anyhow, so you might as well supply the option. But then one option might be 'go full out when there's lots of juice, drop down a little bit when we're running out'.
It does and it doesn't.
I wonder how long you could get an old school Nokia phone (thing monochrome display with only characters) to last these days if you replaced the battery with the exact same weight of current battery technology.
Or, take one of the earlier (say 80286) laptops and do the same.
On the one hand, you are right - as battery technology has improved, we've only increased how much power these devices use. On the other hand, these devices are infinitely more useful than what we had back then and the tradeoff is certainly worthwhile.
It depends... sometimes customers would probably come back and order later. Sometimes they might order somewhere else that is available. Or sometimes they might use the extra time to ponder whether they really need the item and ultimately might decide not to buy it.
If you read the summary this seems to be more related to trademarks than it is to patents.
These seems to be mostly to do with a corps ability to plan marketing material for a product before launching it and still having it be a surprise. Seems reasonable to me, especially for things such as 'Siri' or 'Apple Watch'. Makes things a bit more concrete in a legal sense as well since you don't have some trademark argument in the event somebody tries to swoop in and take it - you haven't registered your intent months before in the other jurisdiction. In the meantime you get your product ready to ship and send it out the door. You get your marketing surprise with your fancy reveal. In the event somebody leaks it you don't have to worry about rushing off to file it.
Seems almost like this should be built into the trademark filing process - the ability to register intent to use a mark and keep it secret for some amount of time (say 3 months or 6 months).
On the other hand, it probably doesn't look good from a legal perspective if you signed a contract with your content providers to stop people from watching from other regions, and then you didn't do due diligence to enforce it, had you agreed to do that.
I was hopeful that Netflix wouldn't really work that hard to enforce this, but it seems that they have. If they are being contractually compelled to do this, and they have agreed to enforce it, then it would be a bad idea to not really do it.
It is likely better for their business to make the content available to all the folks in the US who are within the allowable region and block others, than to not have the content at all and lose all of the US subscribers.
My digitizer did stop working... a while after the screen cracked a little bit I got a new phone and wasn't as careful with guarding the old phone from the little one. The LCD display still works great but the digitizer stopped working.
Not sure I would consider that LG's fault though.
Is that a typo or is there really 2000 times the cache?
No, wildcard certs only go one level (See http://www.ietf.org/rfc/rfc281...).
Looks like they erroneously added www. to the front. They have a wildcard cert for *.slashdot.org but the www.build does not match (wildcards only go one level in domain certs). If you remove the www. from the beginning of the link it works fine. Might explain why it works on the other person's phone as well - mobile version might link differently.
The summary says: "As for whether or not this method will make its way to store shelves, it won't in the near future." This indicates that milk treated using this process is not available on store shelves. But then the summary says: "The product is currently being distributed." So I'm curious as to who they are distributing this milk to and what is being done with it?
>> You are well aware that Aluminum foil only amplifies your brain waves to be spied on by the government.
That is a lie spread by the government to get us to stop wearing our hats.
You could do your scouting at night to determine where traffic lights are. Probably would make the problem much easier. Though probably is much easier to just make the system work better.
Should be "It measures 10.4mm thin."
Right... because you can reasonably run a multi-core Intel CPU in an application like this. Power usage is probably a much more significant factor.
What can happen is including npm install as part of your deployment process. Depending on how tightly you specify your dependencies this could result in packages getting updated to versions that have not been tested with your code by simply redeploying (or maybe somebody has put this in as part of the flex up process, so you end up with new app servers with slightly different code than older app servers.
There are many ways to solve this, but it can get overlooked until you get bitten in the ass and deploy code that isn't what you thought you were because some package dev somewhere released a package upgrade.
There's no point learning to code until PHP 6 is released.
Ah, I didn't look that closely to see that. On the other hand, I still wouldn't consider them 'astoundingly efficient' as the headline claims. This article discusses a design for a 97.09% efficient inverter. (I admit at this point I'm beginning to be argumentative, but I still think the headline should have been astoundingly dense inverters, though my theory is that slashdot injects in intentional errors to drive comments and traffics from those who like to nitpick submissions).