Judge: Produce the contents of your IMs from Jan 2006-Mar 2007 Orclevegam: Here you go Judge: These are encrypted Orclevegam: So? Judge: 5 years in the slammer!
I dunno, man, one of the first things in my iptables rules is to drop all packets for/from the internal network which appear on the external interface.
I'll bet a LOT of routers are built the same way.
Re:National Standards Bodies
on
RTF Vs. OOXML
·
· Score: 1
> I think ISO needs to start with itself and standardise how national bodies work.
Wow, I think that might be the most insightful comment I've read on slashdot all year!
I suspect that the behaviour you're describing is only for the case when multiple deliveries occur via a single SMTP transaction (i.e. multiple RCPT TO commands before DATA) rather than the general case of messages-which-happen-to-be-identical, which is what the OP was positing.
Either that, or when the sending system sends the same message in multiple transactions (i.e. poor mailer, or a mailer interrupted by a 452 response code) and the messages have the same Message ID header.0
That said, the original poster makes an assumption that identical-looking messages are likely to be indistinguishable, which they in fact are not, unless generated by a non-compliant mailer and probably get received by a non-compliant mailer. Message ID must vary from message-to-message, and the Date and Received-By: headers are extremely likely to vary from message-to-message.
So, the OP then faces a HUGE search problem which will only "hit" when the sending MTA, and probably the receiving MTA, are non-comformant. This is unlikely to occur with any great frequency, making that search heuristic non-productive. He'd get better lucky archiving large message fragments as some huffman-coding variant (and surely much better could be done with a little thought).
1. Release geek-oriented product nobody's ever heard of 2. Make it very obvious it's based on GNU/Linux 3. "Accidentally" screw up the GPL code release 4. Wait for Slashdot Story 5. Fix GPL code release 6. Trigger Slashdot follow-up story 5. Free advertising sells lots of product 6. Profit!
> People with two extra fingers on each hand can get it OVER 9000!
Yeah, I guess 16383 is over 9000.
You could actually get up to 4095 with 10 fingers, though, you just have use the front/back of each hand as a bit. Hey, and if you use upsidedown/right side up as a bit, that gets you to 16383. And, if you use bent vs. straight fingers, that gets you all the way to 65535.
But you'd look like a dancing retard if you counted really fast.
Second, if you 10 GB of email in your IMAP account, you don't have to download it all to read just one message that arrived 9GB ago. This is a really big deal on services where you're paying by the byte.
And finally, you can read your email from multiple sources, have folders that match up and read flags that persist.
- I hope you're not e to the x, because I'd like to integrate you!
- Let's experimentally determine the dot product of i and pi!
- I'm a square. Why don't you complete me?
- Let's do some log-a-rhytms!
Okay, that's all I can make up on the spur of the moment.
Re:Well it's about fucking time
on
Free IMAP On Gmail
·
· Score: 2, Informative
I dunno. POP3 and IMAP4 are both serious enhancements to the MUA experience.
I'd peg UUCP as 1.0 -- straight copying of files and appending to a mailbox on the machine where the mail was read. Mail path directed by sender through well-known hosts.
1.5 would add SMTP, and the ability to deliver over TCP/IP using berkeley name resolution (DNS) without the need for well-known hosts. Mail is still read on the machine it is delivered to.
2.0 seriously enhances the user experience, by allowing the user to retrieve e-mail from a central repository (mail server) to be read by a (potentially offline) MUA via POP2. 2.1 would be POP3, 2.2 would be IMAP, 2.2.3 would be IMAP4.
Slashdot Mirror
..and furthermore, you can fire without cause for up to 90 days after the initial hire.
So whoever was feeding this guy info is full of shit.
> It's as offensive to me as a white guy speaking "black" to a black
;)
> coworker out of the blue and just as effective.
Cue June Cleaver: "Excuse me, miss? I speak jive."
LOL!
You only need login/passwd authentication to RELAY through Gmail.
Otherwise, only Gmail users could get Gmail Email.
> Drivers were asked to travel at 30 kmph
Man, they drive fast in Japan!!
In the US, I have seen freeways posted with speeds as low as 55 mph! That's 545 times slower!
> Wasn't there a similar situation where MS crippled Netscape
> so people would be more likely to use Internet Explorer?
You mean the one where IE4 did a better job implementing W3C DOM and CSS specs than Navigator 4 did?
Whoops!
> each ones sucks more than the one before until it gets "re-imagined" into a new series
You know, that sounds an awful lot like what happened with MS-DOS.
The only exception I can think is that 3.3 was a clear improvement over 3.2.
Maybe point-revs don't count.
Judge: Produce the contents of your IMs from Jan 2006-Mar 2007
Orclevegam: Here you go
Judge: These are encrypted
Orclevegam: So?
Judge: 5 years in the slammer!
I dunno, man, one of the first things in my iptables rules is to drop all packets for/from the internal network which appear on the external interface.
I'll bet a LOT of routers are built the same way.
> I think ISO needs to start with itself and standardise how national bodies work.
Wow, I think that might be the most insightful comment I've read on slashdot all year!
Wes
That sounds about right.
I seem to recall liquid crystal displays replacing LEDs in watches and calculators in the 1970s.
Actually, LEDs and those super-cool bluish neon tube thingies. Not nixies, the little ones. What the hell were they called?
I suspect that the behaviour you're describing is only for the case when multiple deliveries occur via a single SMTP transaction (i.e. multiple RCPT TO commands before DATA) rather than the general case of messages-which-happen-to-be-identical, which is what the OP was positing.
Either that, or when the sending system sends the same message in multiple transactions (i.e. poor mailer, or a mailer interrupted by a 452 response code) and the messages have the same Message ID header.0
That said, the original poster makes an assumption that identical-looking messages are likely to be indistinguishable, which they in fact are not, unless generated by a non-compliant mailer and probably get received by a non-compliant mailer. Message ID must vary from message-to-message, and the Date and Received-By: headers are extremely likely to vary from message-to-message.
So, the OP then faces a HUGE search problem which will only "hit" when the sending MTA, and probably the receiving MTA, are non-comformant. This is unlikely to occur with any great frequency, making that search heuristic non-productive. He'd get better lucky archiving large message fragments as some huffman-coding variant (and surely much better could be done with a little thought).
No. Desktop machines are too big become bricks. They are only potential cinder blocks.
Also, Tablet PCs with corrupt Windows installations will henceforth be referred to as "paving stones".
You had large files?
In my day, files were 2GB or less!
1. Release geek-oriented product nobody's ever heard of
2. Make it very obvious it's based on GNU/Linux
3. "Accidentally" screw up the GPL code release
4. Wait for Slashdot Story
5. Fix GPL code release
6. Trigger Slashdot follow-up story
5. Free advertising sells lots of product
6. Profit!
Thanks. I was beginning to think NOBODY online today understood a modern(ish!) VM subsystem.
The rest probably got distracted looking at the dirty pages.
Well then you just need a better weapon, like an FN P90. And a big magazine.
Duh.
> People with two extra fingers on each hand can get it OVER 9000!
Yeah, I guess 16383 is over 9000.
You could actually get up to 4095 with 10 fingers, though, you just have use the front/back of each hand as a bit. Hey, and if you use upsidedown/right side up as a bit, that gets you to 16383. And, if you use bent vs. straight fingers, that gets you all the way to 65535.
But you'd look like a dancing retard if you counted really fast.
Bah.
The road is long, with many a winding turn.. that leads to who knows where. I mean, to the MAFIAA actually winning that.
Well, first off IMAP has folders.
Second, if you 10 GB of email in your IMAP account, you don't have to download it all to read just one message that arrived 9GB ago. This is a really big deal on services where you're paying by the byte.
And finally, you can read your email from multiple sources, have folders that match up and read flags that persist.
Math pick up lines? Oh, that sounds like fun!
- I hope you're not e to the x, because I'd like to integrate you!
- Let's experimentally determine the dot product of i and pi!
- I'm a square. Why don't you complete me?
- Let's do some log-a-rhytms!
Okay, that's all I can make up on the spur of the moment.
Especially if you program in LOGO!
I dunno. POP3 and IMAP4 are both serious enhancements to the MUA experience.
:)
I'd peg UUCP as 1.0 -- straight copying of files and appending to a mailbox on the machine where the mail was read. Mail path directed by sender through well-known hosts.
1.5 would add SMTP, and the ability to deliver over TCP/IP using berkeley name resolution (DNS) without the need for well-known hosts. Mail is still read on the machine it is delivered to.
2.0 seriously enhances the user experience, by allowing the user to retrieve e-mail from a central repository (mail server) to be read by a (potentially offline) MUA via POP2. 2.1 would be POP3, 2.2 would be IMAP, 2.2.3 would be IMAP4.
IMNSHO.
What falls faster -- a pound of bricks or a kilogram of feathers?
I was thinking that maybe the Widow Patch was to help you through withdrawing from your widow.
Presumably they're loaded with baby oil or something.
Would they HAVE any users if their PageRank was a little lower?
Or - if a web page is put up on a server, and nobody is there to surf it -- does it make an impression?