On the matter of "undocumented tricks", I had a problem last year that was preventing me from getting inbound e-mail (the spammers had no problem, of course) because of DNS server configuration. When you register a domain, you have to provide two or more authoritative server addresses for the registrar database. These addresses also require a domain name for no good reason I can see other than for documentation purposes. (How are you supposed to look up ns1.example.com via DNS when you still need the IP address of its authoritative server? That's why the IP address is in that database.).
It so happens that some DNS servers will reject your authoritative server if the server domain name from the registrar database is not in your zone file. In other words, when looking up, say, www.example.com, after getting the DNS server IP address of ns1.example.com from the registrar database, they then take the server name from the registrar database (ns1.example.com) and fail if that doesn't resolve. To make things more fun, add in anycast DNS, where some of the servers do this, and some don't (or maybe there are delays between the initial lookup and server name lookup), and you have no idea which one you got for any given lookup. The result is that if you repeatedly look up your domain name on (say) AT&T's anycast DNS servers, sometimes you'll get your IP address, and sometimes you won't. Google's DNS works fine all the time, but you can't require the rest of the world to use that. And some mail servers will queue your mail for 24 hours (!) if the DNS lookup fails.
tl;dr: the registrar database domain names of your DNS servers should be in your zone files, or else
The reason is because the PTR record basically depends on the provider of the IP address space, and their cluefulness and willingness to maintain PTR records. You either have to have them add your PTR record to their authoritative in-addr.arpa DNS server, or get them to assign authority to your own DNS server. The latter is (AFAIK) difficult because you can't do binary masks on decimal numbers in zone files, so if you have a zone that isn't a/24 (or/16), your ISP has to about the same amount of work as if they were doing it for you. And some providers are too clueless to set up PTR records at all, period.
In my case, I run a web server, e-mail, and authoritative DNS from my fixed-IP DSL at home. (I do have PTR records, but nobody would know to use my DNS server for in-addr.arpa.) Because I understand this and other problems, I have my mail server send outbound mail up to my ISP's outbound mail server. And then I send outbound mail from my laptop to the ISP's server anyhow, because the ISP supports a username/password, so I can still send mail when not at home without setting up my server as an open relay or setting it up for authentication (or having to change my e-mail client configuration). In extreme cases, I can SSH tunnel to my home system and send mail out that way, but I haven't done that in a long time.
So it requires a combination of an IP provider who is either clueless ("regulator bodies"? Government is a fine source of cluelessness), unwilling, or too much trouble to work with, plus the sender not having (or more likely not knowing to use) an upstream e-mail server.
Have you ever taken a hard drive apart? There's a couple of real nice rare earth magnets in there for the voice coil, less than 3 inches from the heads, and maybe an inch from the platters. It would take one hell of a magnet to equal that strength at any distance, much less exceed it. It takes a lot of magnetism to flip the fields in those platters. The heads can provide that strength, just over a very small area.
TxTag in Texas is an RFID sticker that operates at highway speeds. Plus, they also have license plate cameras so that they don't have to hire actual toll collectors (at least in the Austin area) for people without the tags. In particular, one stretch of a toll road added a couple of years ago didn't even have room for a toll plaza... then they realized that pay-by-mail worked well enough to get rid of the humans elsewhere.
The best part is that TxTag was designed to be compatible with various older toll tag systems around the state. My tag is valid for all (with a few obscure exceptions) toll roads statewide.
(This notifies drivers that their battery is still good, unlike the silent second-generation version, which informs them of a dead battery by sending a ticket in the mail.)
I followed the link and the word "battery" was nowhere. The problem was entirely a database problem. Is submitter trolling or just completely stupid?
I know that current generation TxTag toll tags in Texas are RFID stickers, and of course they won't beep. Is submitter really sure that the current generation I-Pass tags use batteries?
As for the camera, a patent is not a statement of what is actually going to be implemented, or even what is feasible to implement. I can't see why anyone would want to do it, other than nosiness on the part of the gummint, or under-the-table deals from someone wanting to sell them, especially when it is clear that a battery is no longer needed for toll tag transponders. 1) a camera would take a lot more power than a transponder, are they expecting people to hook it up to the lighter plug? 2) how exactly do they plan to get the data from the camera to Big Brother, especially on battery power? That's a lot of data, and a lot of battery drain.
The Dutch were notorious for abusing Usenet binaries. They would post floods (ignoring upload limits in group rules, such as uploading whole TV seasons all at once), post off-topic binaries (such as US cartoons in anime groups), post passworded archive binaries, and worst of all, they had warez-exchange programs using Usenet as a file transfer protocol that meant they didn't have to care, much less know, what Usenet was. Basically, they used alt.binaries.* as their own personal file dump. And their news admins didn't care.
I'm not surprised that Rule #1 and Rule #2 were broken over there. Nor am I sympathetic about this situation.
And cancel messages? Gimme a break. Once the net.kooks learned that they could forge cancels to wipe anything they didn't agree with, larger NSPs simply ignored cancels wholesale. That was in the mid '90s or so.
Seamonkey is the original Mozilla browser without all the Firefox crap thrown in. (At some point they felt the need to rename it from Mozilla, but I can't remember why.)
No Microsoft code, no trendy crap like ribbon bars, runs Ad Block Plus.
My MBP is now old enough that AppleCare has expired, but I just got a plain old DRAM module from Fry's to upgrade it from 2 gigs to 5 gigs. I only had to look up which PC#### spec it used.
and there aren't enough of them to justify keeping Concorde in the air,
The original problem was that it was deemed too noisy to land at inland airports (such as Dulles), so they lost a good chunk of the potential market. But there apparently were enough to keep Concorde in the air once they realized they could raise their prices significantly without affecting ridership. The speed was value enough for a limited class of customers to pay fares that could keep it going.
Then one plane had a problem on takeoff ("luckily" enough on a chartered plane full of tourists rather than the usual VIPs and celebs), and they decided that it wasn't worth the trouble to continue to keep them running. (Never mind that IIRC it was caused by junk on the runway.)
But there surely won't be enough now to justify the R&D costs of a whole new SST.
Slashdot Mirror
I'm waiting for LuchaLibreOffice Online. Or would that be LuchaOfficeLibre?
Sorry, this is Slashdot. We use automotive analogies here. Does it have anything to do with melting ice on bridges?
It also needs a "MOOOOOM! BRING ME MORE DORITIOS!" option. (Think of Eric Cartman playing WoW.)
CSB
On the matter of "undocumented tricks", I had a problem last year that was preventing me from getting inbound e-mail (the spammers had no problem, of course) because of DNS server configuration. When you register a domain, you have to provide two or more authoritative server addresses for the registrar database. These addresses also require a domain name for no good reason I can see other than for documentation purposes. (How are you supposed to look up ns1.example.com via DNS when you still need the IP address of its authoritative server? That's why the IP address is in that database.).
It so happens that some DNS servers will reject your authoritative server if the server domain name from the registrar database is not in your zone file. In other words, when looking up, say, www.example.com, after getting the DNS server IP address of ns1.example.com from the registrar database, they then take the server name from the registrar database (ns1.example.com) and fail if that doesn't resolve. To make things more fun, add in anycast DNS, where some of the servers do this, and some don't (or maybe there are delays between the initial lookup and server name lookup), and you have no idea which one you got for any given lookup. The result is that if you repeatedly look up your domain name on (say) AT&T's anycast DNS servers, sometimes you'll get your IP address, and sometimes you won't. Google's DNS works fine all the time, but you can't require the rest of the world to use that. And some mail servers will queue your mail for 24 hours (!) if the DNS lookup fails.
tl;dr: the registrar database domain names of your DNS servers should be in your zone files, or else
The reason is because the PTR record basically depends on the provider of the IP address space, and their cluefulness and willingness to maintain PTR records. You either have to have them add your PTR record to their authoritative in-addr.arpa DNS server, or get them to assign authority to your own DNS server. The latter is (AFAIK) difficult because you can't do binary masks on decimal numbers in zone files, so if you have a zone that isn't a /24 (or /16), your ISP has to about the same amount of work as if they were doing it for you. And some providers are too clueless to set up PTR records at all, period.
In my case, I run a web server, e-mail, and authoritative DNS from my fixed-IP DSL at home. (I do have PTR records, but nobody would know to use my DNS server for in-addr.arpa.) Because I understand this and other problems, I have my mail server send outbound mail up to my ISP's outbound mail server. And then I send outbound mail from my laptop to the ISP's server anyhow, because the ISP supports a username/password, so I can still send mail when not at home without setting up my server as an open relay or setting it up for authentication (or having to change my e-mail client configuration). In extreme cases, I can SSH tunnel to my home system and send mail out that way, but I haven't done that in a long time.
So it requires a combination of an IP provider who is either clueless ("regulator bodies"? Government is a fine source of cluelessness), unwilling, or too much trouble to work with, plus the sender not having (or more likely not knowing to use) an upstream e-mail server.
So is this a chance to get DBAs onto the B-Ark?
3. 'Prior fart' used to nullify 2.
Ewwwww, who prior farted?
I don't know, but it already plays Doom!
But can emacs do this? I mean "yet", of course.
By your command, Number Six
I am not a number, I am a free Cylon!
It'll probably be like that episode of American Dad.
Have you ever taken a hard drive apart? There's a couple of real nice rare earth magnets in there for the voice coil, less than 3 inches from the heads, and maybe an inch from the platters. It would take one hell of a magnet to equal that strength at any distance, much less exceed it. It takes a lot of magnetism to flip the fields in those platters. The heads can provide that strength, just over a very small area.
TxTag in Texas is an RFID sticker that operates at highway speeds. Plus, they also have license plate cameras so that they don't have to hire actual toll collectors (at least in the Austin area) for people without the tags. In particular, one stretch of a toll road added a couple of years ago didn't even have room for a toll plaza... then they realized that pay-by-mail worked well enough to get rid of the humans elsewhere.
The best part is that TxTag was designed to be compatible with various older toll tag systems around the state. My tag is valid for all (with a few obscure exceptions) toll roads statewide.
(This notifies drivers that their battery is still good, unlike the silent second-generation version, which informs them of a dead battery by sending a ticket in the mail.)
I followed the link and the word "battery" was nowhere. The problem was entirely a database problem. Is submitter trolling or just completely stupid?
I know that current generation TxTag toll tags in Texas are RFID stickers, and of course they won't beep. Is submitter really sure that the current generation I-Pass tags use batteries?
As for the camera, a patent is not a statement of what is actually going to be implemented, or even what is feasible to implement. I can't see why anyone would want to do it, other than nosiness on the part of the gummint, or under-the-table deals from someone wanting to sell them, especially when it is clear that a battery is no longer needed for toll tag transponders. 1) a camera would take a lot more power than a transponder, are they expecting people to hook it up to the lighter plug? 2) how exactly do they plan to get the data from the camera to Big Brother, especially on battery power? That's a lot of data, and a lot of battery drain.
If you're so worried about Microsoft code, why would you be running Windows at all? I know there isn't any in my OS X.
You make a grown man cry...
Don't you mean iColi?
The Dutch were notorious for abusing Usenet binaries. They would post floods (ignoring upload limits in group rules, such as uploading whole TV seasons all at once), post off-topic binaries (such as US cartoons in anime groups), post passworded archive binaries, and worst of all, they had warez-exchange programs using Usenet as a file transfer protocol that meant they didn't have to care, much less know, what Usenet was. Basically, they used alt.binaries.* as their own personal file dump. And their news admins didn't care.
I'm not surprised that Rule #1 and Rule #2 were broken over there. Nor am I sympathetic about this situation.
And cancel messages? Gimme a break. Once the net.kooks learned that they could forge cancels to wipe anything they didn't agree with, larger NSPs simply ignored cancels wholesale. That was in the mid '90s or so.
Seamonkey is the original Mozilla browser without all the Firefox crap thrown in. (At some point they felt the need to rename it from Mozilla, but I can't remember why.)
No Microsoft code, no trendy crap like ribbon bars, runs Ad Block Plus.
Try Seamonkey instead. It's still an old-school browser, and as a Mozilla product, it's been benefiting from the good parts of Firefox.
Just got 3.6.23 today. I guess it wasn't.
However, 9/11/2001 happened
Wow, it's been so long, I forgot about that being when Concorde really got grounded.
[Citation needed]
My MBP is now old enough that AppleCare has expired, but I just got a plain old DRAM module from Fry's to upgrade it from 2 gigs to 5 gigs. I only had to look up which PC#### spec it used.
and there aren't enough of them to justify keeping Concorde in the air,
The original problem was that it was deemed too noisy to land at inland airports (such as Dulles), so they lost a good chunk of the potential market. But there apparently were enough to keep Concorde in the air once they realized they could raise their prices significantly without affecting ridership. The speed was value enough for a limited class of customers to pay fares that could keep it going.
Then one plane had a problem on takeoff ("luckily" enough on a chartered plane full of tourists rather than the usual VIPs and celebs), and they decided that it wasn't worth the trouble to continue to keep them running. (Never mind that IIRC it was caused by junk on the runway.)
But there surely won't be enough now to justify the R&D costs of a whole new SST.