Spam isn't so much an economics problem as a "some people are just dicks" problem
That statement is accurate only for those who believe that spam is sent out to piss you off. [...] Spam is a product that people are willing to pay for.
You and the GP are both correct -- the dicks are (also) to be found among those who are willing to pay. Yeah I know there's a double entendre there, but I'm just using the GP's wording here. What I mean is that spam wouldn't be so much of a problem if it wasn't profitable. Hence, part of the blame lies with the very, very few recipients who choose to become customers; they may not realise that in doing so they are pissing off the rest of us (on the other hand, if they do realise but just don't care, that's another issue and more difficult to deal with).
AC, go read Eastern Standard Tribe. Go on, I'll wait. http://craphound.com/est/Cory_Doctorow_-_Eastern_Standard_Tribe.txt Done? Good. Nice read, isn't it? Anyway, note how your post is exactly what they did 'at the pike'. And yet, Big Media was still involved. Like nature, I'm afraid capitalism "will always find a way" (hoping I won't get sued by Spielberg for that).
Because, obviously, you can't invent something old. (You can, however, patent it...)
Seriously though, it does seem to be duplicated functionality, but you can also view it as extracting this font-related feature and making it available without needing full SVG support. Also, it probably allows rendering on a per-glyph basis rather than regarding the entire page as an SVG image... but now I'm just guessing.
Yes, exactly. My old 6310 and 6310i required charging every 7-10 days, tops. But those had small monochrome screens and weren't able to run all sorts of apps apart from some Java applets (to say nothing of pda-like features).
I wonder if there's a market for a battery-friendly *monochrome* Android-based pda-cum-phone?
Yes, it will be 'harder' to code for a *class* of devices rather than targeting a single model, but not necessarily harder than you choose to make it yourself.
If you want to code a game for the PS3, you know *exactly* what the hardware is -- but it'll be limited to that, and X-Box owners can't play along unless you port your game.
If you make a website, by simply sticking to the standard, you can support *any* browser out there.
Similarly, in Android, the OS framework is going to give you a lot of assistance, for instance with laying out the screen (for whatever dimensions, aspect ratio, resolution, colour depth), and features relying on model-specific features will degrade gracefully (a Galaxy doesn't crash because you ask it to turn on its (nonexistent) notification LED).
The problem, as evidenced with the somewhat painful browser example, is whether or not device manufacturers will in fact build their devices to spec -- and there is talk that HTC has pulled a classic "IE" by misinterpreting the compass sensor, causing other manufacturers to have to make the same misinterpretation or supply incorrect readings to the OS. (rolleyes)
So what? If we'd all rush to buy electric cars, would it matter that we wouldn't *all* be rushing for the EV-1? Wouldn't it, in fact, be better if we had dozens or more options to choose from -- any electrical vehicle is going to "promote the cause", as it were.
Regarding speed, you will find Android on the slow side as well, especially if you let your SMS app become bogged down with hundreds of old messages (to show previous chat log), and when your calendar and phone book get lots of entries. I'm not saying it takes *several* seconds, but it's a damn cry from being instantaneous.
Regarding battery life, expect one full working day, or two whole days TOPS, from *any* modern device.
If you want fortnight-long battery life, grab a Psion Series5 MX Pro and have it refurbished (yes, I'm being serious). If you want instant application starts, grab either that or a Palm Treo and have that refurbished. For *phone* capability, forget the Psion, that's "just" a pda (in quotes because it's a damn proper one).
Do NOT expect an Android device to be a pda. It's a smartphone.
I understand your point. Although, I've never seen a d4 where there's only one number per side. If "1" points downward (and isn't shown to a viewer), then what's your roll?
d4's are no problem, regardless of type. The #3 surface, for instance, will list "1", "2", and "4" in *some* (basically unimportant) configuration, finding the missing number, which yields the roll, is then just a matter of deduction.
The main issue is whether or not the system can read the numbers/pips, or if you need specially marked/equipped dice.
Computer types are so used to thinking about eventualities, undesirable consequences, dangling IF conditions, and protecting against them that they fall into doing so in personal life as well.
Amen. I know this one is definitely something many programmers' minds obsess about. For some of us, probably to the point where it affects our daily lives.
Every now and then, I spend a sleepless night failing to dream up solutions for dreamt-up horror scenarios (not volcanic zombie outbreaks at the town hall, just normal everyday decision events gone horribly wrong, Elm Street style). Or just slaving over some fscked up code that won't compile -- even though I'm perfectly aware that the root cause is that I'm having a nightmare, and it would probably help to wake up (if I could just get it to compile first...).
Put another (less technical) way, one's resume should be presented as an outline, so that authors may supply a full bio while enabling readers to dig down into points of interest from a short overview.
Slashdot Mirror
Spam isn't so much an economics problem as a "some people are just dicks" problem
That statement is accurate only for those who believe that spam is sent out to piss you off. [...] Spam is a product that people are willing to pay for.
You and the GP are both correct -- the dicks are (also) to be found among those who are willing to pay. Yeah I know there's a double entendre there, but I'm just using the GP's wording here. What I mean is that spam wouldn't be so much of a problem if it wasn't profitable. Hence, part of the blame lies with the very, very few recipients who choose to become customers; they may not realise that in doing so they are pissing off the rest of us (on the other hand, if they do realise but just don't care, that's another issue and more difficult to deal with).
...bad preview, I meant "General rule > manual fixes"...
Why oh why is it so hard to include an automatic URL converter into slashcode, at least for links in the summaries?
You'd think that, since slashcode can intelligently decide to show the domain in brackets, that it could also apply that nyud suffix...
<your entire post, basically>
AC, go read Eastern Standard Tribe. Go on, I'll wait.
http://craphound.com/est/Cory_Doctorow_-_Eastern_Standard_Tribe.txt
Done? Good. Nice read, isn't it? Anyway, note how your post is exactly what they did 'at the pike'. And yet, Big Media was still involved. Like nature, I'm afraid capitalism "will always find a way" (hoping I won't get sued by Spielberg for that).
Whoa, Illinois only has one single person who is over 18, and not a felon, and will potentially vote for this politician?
Time to get the hell out of Illinois -- regardless if you're the one, the politician, or one of the rest! :-p
Why are they inventing something new?
Because, obviously, you can't invent something old. (You can, however, patent it...)
Seriously though, it does seem to be duplicated functionality, but you can also view it as extracting this font-related feature and making it available without needing full SVG support. Also, it probably allows rendering on a per-glyph basis rather than regarding the entire page as an SVG image ... but now I'm just guessing.
I think it was all about money. At the advent of Wireless networking, AES would've been expensive to implement.
802.11b predates AES by quite a few years.
Well, there you go, then. That would make it rather expensive.
By the way, if anyone's interested in time travel, meet me at the mall last Thursday.
Well you could, you know, remove said electronics from said ass before servicing. Just a thought...
Or coconuts. (Swallows)
So you're saying this isn't really a test for Mars, it's for the 'B' ark?
If you ever find yourself on the 'launchpad', as it were, do ask around for any Arthurs or Fords among the crew. And bring a towel.
Oh, I thought he meant the beard.
Yes, exactly. My old 6310 and 6310i required charging every 7-10 days, tops. But those had small monochrome screens and weren't able to run all sorts of apps apart from some Java applets (to say nothing of pda-like features).
I wonder if there's a market for a battery-friendly *monochrome* Android-based pda-cum-phone?
Yes, it will be 'harder' to code for a *class* of devices rather than targeting a single model, but not necessarily harder than you choose to make it yourself.
If you want to code a game for the PS3, you know *exactly* what the hardware is -- but it'll be limited to that, and X-Box owners can't play along unless you port your game.
If you make a website, by simply sticking to the standard, you can support *any* browser out there.
Similarly, in Android, the OS framework is going to give you a lot of assistance, for instance with laying out the screen (for whatever dimensions, aspect ratio, resolution, colour depth), and features relying on model-specific features will degrade gracefully (a Galaxy doesn't crash because you ask it to turn on its (nonexistent) notification LED).
The problem, as evidenced with the somewhat painful browser example, is whether or not device manufacturers will in fact build their devices to spec -- and there is talk that HTC has pulled a classic "IE" by misinterpreting the compass sensor, causing other manufacturers to have to make the same misinterpretation or supply incorrect readings to the OS. (rolleyes)
So what? If we'd all rush to buy electric cars, would it matter that we wouldn't *all* be rushing for the EV-1? Wouldn't it, in fact, be better if we had dozens or more options to choose from -- any electrical vehicle is going to "promote the cause", as it were.
Regarding speed, you will find Android on the slow side as well, especially if you let your SMS app become bogged down with hundreds of old messages (to show previous chat log), and when your calendar and phone book get lots of entries. I'm not saying it takes *several* seconds, but it's a damn cry from being instantaneous.
Regarding battery life, expect one full working day, or two whole days TOPS, from *any* modern device.
If you want fortnight-long battery life, grab a Psion Series5 MX Pro and have it refurbished (yes, I'm being serious). If you want instant application starts, grab either that or a Palm Treo and have that refurbished. For *phone* capability, forget the Psion, that's "just" a pda (in quotes because it's a damn proper one).
Do NOT expect an Android device to be a pda. It's a smartphone.
The camera in my Galaxy is actually surprisingly good. However (and unsurprisingly), it doesn't have red-eye reduction and such photography modes.
But, I hear there's a lot of that going 'round at the moment...
Granted, "pentagonal trapezohedron" is not the most easily remembered word!
I understand your point. Although, I've never seen a d4 where there's only one number per side. If "1" points downward (and isn't shown to a viewer), then what's your roll?
d4's are no problem, regardless of type. The #3 surface, for instance, will list "1", "2", and "4" in *some* (basically unimportant) configuration, finding the missing number, which yields the roll, is then just a matter of deduction.
The main issue is whether or not the system can read the numbers/pips, or if you need specially marked/equipped dice.
summon your inner Clippy.
Shudder! Begone, thou evil spirit!
Aww fudgit...
"We need more people like you to explain people like us to people like them."
And I mean it sincerely, not to be all funny.
We need more people like to explain people like us to people like them.
Thanks man.
Computer types are so used to thinking about eventualities, undesirable consequences, dangling IF conditions, and protecting against them that they fall into doing so in personal life as well.
Amen. I know this one is definitely something many programmers' minds obsess about. For some of us, probably to the point where it affects our daily lives.
Every now and then, I spend a sleepless night failing to dream up solutions for dreamt-up horror scenarios (not volcanic zombie outbreaks at the town hall, just normal everyday decision events gone horribly wrong, Elm Street style). Or just slaving over some fscked up code that won't compile -- even though I'm perfectly aware that the root cause is that I'm having a nightmare, and it would probably help to wake up (if I could just get it to compile first...).
Put another (less technical) way, one's resume should be presented as an outline, so that authors may supply a full bio while enabling readers to dig down into points of interest from a short overview.