I love the Forgotten World now

I had been doing runs to the first treasure box in grade 1 Forgotten World with my glaive character, but now that I’ve made a wizard character for a change, I see that I was an idiot using a Chinese character in the Forgotten World. It’s too slow.

You just need the bard skill called “Noise” and you can run directly to the first treasure box without bothering to kill a single monster. It took me two minutes with my wizard/bard. It’s no use going past the first treasure box alone if you ask me; it’s too much wasted time.

iBot works on Windows 7 x64!

botters

Goldbots at Hashades/Ishades and Sonars will sometimes auto-invite you to exp share parties. You can just get on a horse, go afk and be a leech off of them for as long as you don't disconnect!

I’ve been using iBot successfully on Windows XP for months, but I had never gotten it to work on Windows 7 x64 until today. Other people seemed to have problems registering the required ocx files in Windows 7, but that was never an issue for me. I didn’t have any of the problems that people seemed to typically report; I simply couldn’t get the bot to run at all.

I would open the bot and click “Run client” and the game would start, but it wouldn’t capture the information from sro_client.exe. It wouldn’t say “Connected to login server” when the game started. I could login successfully through the client, but as soon as I did, I would get disconnected. The bot window would never display any of my character information. It wouldn’t say a thing, not even “Login successful”.

I tried seemingly endless combinations of firewall and antivirus settings, even going so far as to completely turn them both off trying to get this thing to work. Everyone seemed to insist that it does indeed work on Windows 7, so I had no idea why I was having such a ridiculously difficult time getting it up and running. Running it in compatibility mode for Windows XP Service Pack 2 or 3 didn’t work and neither did running the bot as administrator. I really felt I must have been some type of an idiot since, as far as I could tell, no one else was experiencing the same problem I was.

I finally figured it out today, after having given up for some months. The problem was that I had my language for non-Unicode programs set to Japanese, which caused a problem with srodir.ini. I would type in the correct path to either my Silkroad directory or sro_client.exe itself in srodir.ini and it would look correct in Notepad, just like this:

C:\Program Files (x86)\Silkroad

I also tried variations on that, such as adding a trailing backslash or specifying the path to the sro_client.exe itself instead:

C:\Program Files (x86)\Silkroad\

C:\Program Files (x86)\Silkroad\sro_client.exe

So in Notepad it would look just fine to me, the human reader. But it seems that what was getting passed along to iBot was this:

C:¥Program Files (x86)¥Silkroad¥sro_client.exe

Of course, I’m well aware that the backslash displays as the yen symbol in file paths and the like when you’re running a non-Japanese version of Windows in Japanse locale, but I didn’t think it was the problem since I couldn’t actually see anything wrong with the way I was typing in the path. Notepad displayed it correctly, so I thought there was no problem. For the hell of it, I changed the language for non-Unicode programs to English (United States) today and the bot instantly starting working perfectly, just like it does on my XP machine. Turns out the problem had nothing to do with the OS at all; it was just user error. I fail again, it seems.

Success! I fixed my laptop

So I bought this laptop on eBay with a broken screen for virtually zero money. I was sort of vaguely thinking about setting up a dedicated MythTV box or something to leave by my TV but then I got scared since I don’t know how to use MythTV so I decided to use GB-PVR, which I already use but only inconveniently since I need to run a 50 foot cable from my STB to my desktop computer, which is a fire hazard since you’d probably trip over it when trying to leave the apartment. Whew.

Anyway for more or less this reason, as well as the fact that I evaluate my self-worth in terms of the good deals I find on eBay, I was half-heartedly browsing for reasonably priced laptops with cracked or broken screens to set my plan in motion.

A desktop would have worked, I suppose, but I like the idea of giving an abandoned laptop with a cracked screen a nice home and steady work. I also don’t have much space. A desktop needs desk or floorspace but a headless laptop could just sit on top of my standalone DVD/DivX player, which, incidentally, I also procured on eBay.

Among the broken laptops I found on eBay, however, was the one I’m currently using to write this. It was listed as fully working but with a broken screen. The auction even explicitly mentioned that when connected to an external monitor via HDMI it worked fine. So I bought it.

Dual core 2.0GHz processor, 3.0GB of RAM, expandable to 8GB, 802.11n (which is actually useful to me finally since the Actiontec router Verizon gave me for FiOS supports N), and a CD/DVD±R/RW/BD-ROM drive. That means if I ever brick my PS3, which I also bought broken from eBay and fixed, by neglecting to read the readme before flashing it with some CFW, I’ll still have a working Blu-Ray player.

When I got it though I liked it so much that I decided I should try to get the thing into perfect working condition. It looked completely unused with barely a single blemish on the plastic cover, body or anywhere else. The screen was really beautiful without a single mark on it. There is just one small stain on the left side of the speakers. If it weren’t for that though you’d think this was a brand new computer, so I thought it was a shame that the screen didn’t work.

When I got the laptop I went ahead and turned it on, not expecting to see anything. I did not, in fact, see anything on the screen. I connected it via HDMI to my nice ASUS monitor and it POSTed fine. I was surprised though when I entered BIOS to see that it had an HDD installed. I didn’t realise that it was going to come with one. Not wanting to spend more money than was necessary, I was planning on using a 40GB laptop HDD that wasn’t getting much use, but I was sort of considering buying a larger capacity HDD since 40GB is not much for a PVR system.

That’s why I was happy that the thing came with a 160GB HDD. I tried to format it with gparted but it kept saying it couldn’t find any disks. I tried to use DBAN and got some cryptic error. I tried to format it using an Ubuntu installation disc and got some other error. I tried to use an XP install disc but that just hung indefinitely at the disk partitioner screen. I then boot into BIOS and tried to do some HDD self test diagnostic feature that this laptop seems to have. No problems found. Tried the Ubuntu disc again, got same error. Oddly enough the Windows 7 installation disc didn’t complain at all, so that’s the OS I’ve got on it right now. Don’t torch my house, pl0x.

Anyway, once I had an OS installed I realised eventually that the screen wasn’t broken; it was just really, really, really dark. It was so dark that you really couldn’t tell it was turned on at all unless there were some very high contrast images on the screen at the time. I set the following image as the background and could kinda sorta see Nino’s left eye if I placed my face close enough to the screen so that my nose nearly touched it. If you didn’t get that close, you probably wouldn’t notice that it was displaying anything at all.
Nino

So that was a great discovery. It meant that the screen was probably fine; the backlight was just out. That’s easy. Hell, I thought, it might just be a loose cable somewhere. I open it up and have a look-see. I cut my left thumb trying to open it. The damn inside corners of the screen enclosure are sharp. That was not the encouragement I needed. I disconnected and reconnected everything I could find, reassembled the computer and powered it up, not expecting it to work. It didn’t.

Now I was determined. This was a nice computer. I bought a compatible screen, installed it, tested it and was disappointed. No luck. After installing the new screen I had the same problem as before; image was fine but very, very dark. Being naïve and never having done this before, I thought the screen would come with an inverter, but it didn’t. Since the problem was exactly the same with the new screen as with the old screen I put the old screen back in since it was now pretty clear it was actually perfectly fine.

So I went ahead and bought a new inverter from Hong Kong for USD14, 1/18th of the price some US-based online stores were selling for (I kid you not, one site listed the exact same part number for USD252). I was disappointed since I had spent about the same amount on a new screen as I had on the damned computer. But as I said, I was determined now, having cut both my thumbs by this point.

The inverter arrived surprisingly quickly for Hong Kong Post SAL. On a related note, I bought an item from ShopTemp on November 30, 2010, had it shipped by China Post Registered Airmail and didn’t get it until two days ago. They shipped it within a day or so, so ShopTemp gets all the praise in the world for that. ShopTemp did everything right. I am sad they are no more, since this was the very first purchase I had ever made from them and it was a great experience as far as ShopTemp was concerned. On the other hand, it was a terrible experience with China Post and I would caution said post that they should prepare to feel my wrath. Hell, the tracking number still said it was in Beijing on the day I received it in my mailbox. My experiences with Hong Kong Post have been mostly good though, with items usually arriving within 1 to 4 weeks.

Anyway, I receive the inverter and install it. Same problem as always. Now I was utterly baffled. I thought this must mean it was a bad CCFL. That’s something I don’t know how to replace. Perhaps it’s easy, but I didn’t feel like learning anything after my ordeal.

Just before giving up I decided to triple check all the connections inside the computer and screen enclosure. While doing so, I noticed this:
backlight cable

THAT’S THE BACKLIGHT CABLE! IT IS COMPLETELY WORN THROUGH! I NEVER NOTICED IT! I MUST BE THE LEAST OBSERVANT PERSON WHO EVER TRIED TO FIX A COMPUTER.

So I bought a replacement cable and the screen works fine now. Beautiful too. Not a single dead pixel. The only thing is that while I was replacing that broken cable with the new one I cut my left thumb again. I suppose the lesson here is that you should buy broken electronics even if you don’t know how to fix them because the solution is often as simple as replacing a broken cable. Whoever sold this laptop really lost an opportunity to make a fair amount of money since, as I said, the thing is basically brand new. The screen and one small brownish stain on the speaker were the only imperfections.

Now I have one brand new screen I’ve got to resell.

FiOS just keeps getting better and better

Firewire card

This firewire card served me loyally since 2004, now it's time for him to meet the great OEM in the sky

That’s my firewire card. Or at least it was. It’s dead now. There’s a connection here between the title of this post and the image, which I’ll get to presently.

Apparently the FCC requires that television service providers offer consumers STBs with active IEEE 1394 ports. I just learned this recently when I was idly wondering whether or not it was possible to copy recorded programs from my Verizon DVR to an external storage device or the hard drive of my computer.

It turns out that you can’t. In the process of confirming that though I found out that Verizon STBs not only have an “active” firewire port but that you can actually capture live television programming by connecting the STB to any computer with a firewire port. You can also play a recorded program on the DVR and capture it as it plays to your computer via firewire.

It’s always been my default position, more or less, to view the FCC as fulfilling some sort of adversarial role with respect to the goals and ideals of the tech crowd, but this development may force me to modify my views. I really don’t understand what purpose such a law could serve other than making life easier for copyright infringers.

Hell, I bought my Hauppauge HD-PVR more or less to exploit its component connections to record whatever I wanted from broadcast TV. That was before I had a DVR though.

Which brings me to the next thing that I’m astounded at: you can record 5C encrypted programming on Verizon DVRs and play it back! Of course, you can’t play it or anything if you record it via firewire, but if you just want to play it back on your DVR then it actually works!

Not that I’m complaining, but that doesn’t make any sense. I figured that with a Verizon DVR you’d be able to record clear QAM channels only. But I can record anything it seems, even premium channels like HBO.

The ability to capture programs via firewire is great though, since I don’t have to spend money on a capture card this way. I don’t get degraded recordings this way either like I do when I resort to using my HD-PVR. The firewire recordings are the actual MPEG transport streams themselves, so you get the untouched video, audio and even closed captions. This is nice for both pirates and honest people like me. Pirates can give the TS to their encoder friends who then share the file. Honest folks like me also benefit though because I can encode the file however the hell I want. I can do a low CRF x264 encode for archival purposes if I don’t care about storage space, I can do an SD XviD encode to play on my hardware player, I can make an iPod or PSP version of the recording, author a Blu-ray disc, video DVD, etc…

One complaint that I have about the firewire recording though is that some of the HD local channels are 5C encrypted even though they’re not supposed to be. For example, CBS HD is 5C encrypted and cannot be played back if recorded via firewire. CBS SD though is not. It’s mildly irritating since I kinda thought that this was illegal. The only HD channels that it seems one can record via firewire and actually play back are NBC, Fox, ABC, 9 (the one that used to be UPN) and 11. Possibly PBS too, I can’t remember. Ultimately it makes the utility of this discovery somewhat limited, but it’s still pretty far out that it was the government that mandated it.

Anyway, as soon as I found this out I started getting cryptic BSODs here and there when starting D-VHS, the program people seem to use for firewire captures. After getting such a BSOD my PC wouldn’t turn back on for quite some time, about thirty minutes to an hour. No beeps, no BIOS splash screen, nothing at all. After leaving the PSU switch off or unplugging the computer for some time it would eventually come back alive and function normally as though nothing had happened.

After a few days of successfully making firewire captures (with progressively more BSODs) I came to the realization that it was my firewire card that was causing the problem. I could use the PC for hours without a BSOD as long as I didn’t open D-VHS. Once I did I was certain to get a BSOD. So I removed the firewire card and now the PC works fine again. I don’t know what the hell happened. I always thought that a PC component either worked or it didn’t work, not that it may sometimes work and other times prevent your PC from turning on at all.

This all happened within a few days of my discovery of the “active” firewire port on the STB. I feel ripped off. As soon as I discover something great that the government has done for me, some unrelated technical issue prevents me from actually taking advantage of the FCC’s goodwill.

I’m now eagerly awaiting my new firewire card to arrive in the mail. In the meantime though I can still record onto my old iBook G4 using some programs included in the Apple Firewire SDK.

I finally got FiOS

I can’t write a review of it yet or anything, but the installers did, in fact, come yesterday and managed, more or less, to complete the installation. I must say that these installers were some of the most professional and friendly people you could every hope to meet. To say they knew exactly what they were doing would be an understatement. I cannot praise them enough. There were four installers, which seemed like a really smart move, since three of them worked on the wiring while one of them worked on mounting and testing the ONT (which turned out to be defective, though they had extras with them).

The installers were scheduled to arrive between 8:00 AM and 12:00 PM. They arrived right on time at about 10:00 AM to look around the apartment before unloading and bringing their equipment inside. Unfortunately, Con Edison was digging up the street for some reason. Meanwhile, some other construction crew was digging up the street for an unrelated reason on the next block. It was bad timing because it meant that the Verizon installers didn’t have anywhere to park their truck. Since all of their equipment was in the truck it ended up taking an hour and a half for them to load it all up onto some handtrucks and wheel the stuff the several blocks from the truck to my building.

So if you include the time it took them to get the equipment from the truck to my place the whole installation took about 8 hours. But that’s not a complaint really, it wasn’t their fault that it took that long.

They actually finished most of what I expected to be the difficult bits of the installation in about an hour or two. That is, they ran fibre from the hole in the wall through which it enters the apartment to the place where they ONT was going to be installed. They finished that in about an hour. This was really where having four installers was a great idea, since three of them worked on running the fibre while one of them mounted the ONT, which presumably sped things up quite a bit.

Of course, I already had coax in all the rooms as well as in the hallway from Earthlink, so that also sped things up considerably (it was also cheaper since they may charge for running coax around an apartment, depending on what exactly they need to do). They actually got me a working Internet connection in only about two hours (four hours if you include the time spent waiting for them to get all their stuff into the apartment).

The rest of the time they spent doing various things, such as finding out that the ONT was somehow defective. I missed exactly how they figured that out, since the Internet connection had, at least, worked using the first one, but the guy said that one of the other installers had told him that he had performed some sort of test and that he had determined the ONT was no good. So they went ahead and got another one from the truck which was apparently working.

Once it was determined that the second ONT was working, it was just a matter of connecting it to the existing coax. Setting up the set top boxes was very easy; as soon as they were connected to the coax they did some sort of automatic activation procedure that took about ten minutes per box (had to restart that procedure for one of the boxes). I wasn’t actually required to do anything for the activation; the STBs just did it automatically without any user interaction being necessary. Afterward they all worked fine.

There are three telephone lines here. Two should be POTS and one should be what I think is called “FiOS Digital Voice”, which, to the extent that I understand it, is similar to VOIP but it never actually leaves the Verizon network, so it’s not exactly ever reaching the Internet. In any case, the digital one worked as soon as they replaced the bad ONT with the good ONT, but that’s the fax line. The two other lines are for voice calls. They didn’t work while the installers were still here. The installers said that it was not a problem with the setup here in the apartment or with the ONT but rather a bureaucratic issue that can only be fixed by someone essentially “turning on” the two telephone lines by changing some records in a database somewhere and that I should more or less just wait and see what happens. Though I was skeptical at first, the installer said to call him directly if the phone lines didn’t start working some time tomorrow (since by that point it was ~5:00 to 6:00 PM) since he could get through to the proper department that could make the fix more easily than I could. Sure enough, the phones did start working this morning. At this point the only thing that is not working is caller ID.

Now for the most important part: the speed tests. When the installer did a test using Verizon servers he got about 42Mbps downstream and I think 40Mbps upstream. Now that’s obviously amazing, but it wasn’t a proper speed test since it never left the Verizon network. Actual tests that I’ve been doing to non-Verizon servers are much lower. I like this website called Speed Guide, since it lets you look at results from other people based on hostname. So, for example, if I wanted to only see speed test results from FiOS customers in and around the New York City area, I could filter the search results to only view speed tests from people with RDNS ending in “nycmny.fios.verizon.net”. It also lets you save your own speed test history, so now I can look back at my results from my ADSL connection and marvel at how I didn’t kill myself. The top six tests below were from yesterday, right after the installers left at around 6:00 PM.

FiOS Speed Test

The nwrknj tests were not done with my connection. They were done elsewhere with a 15Mbps/5Mbps connection.

So I wasn’t getting the best results even when I used the New York test server. At other speed test sites I was getting mixed results, which were often much better than my results at any of the SG servers. I got carried away and ended up taking 40 speed tests at speedtest.net using servers in various places around the world. I was really surprised at the 42Mbps download speed from Nuuk, Greenland.

The router they gave me was an Actiontec MI424 WR Rev. F. It seems fine so far. They even let me keep my old ADSL modem/router that they initially gave me when I got the ADSL connection, not that I have any use for it now.

Torrent upload speeds vary. I have not yet hit 4MB/s, as I should theoretically be able to do based on some of the speed test results I’m getting. I did hit 1.7MB/s upload once though. The fastest I have uploaded to a single peer so far was 800KB/s to another FiOS customer in Syracuse, NY, but I’ve also managed to upload to a few Japanese peers at a sustained ~700KB/s. I still think that I need to do some reconfiguring of my client, such as increasing the maximum number of peers I connect to per torrent and the number of upload slots per torrent.

I’m not sure how uTP will work with this router yet. It always crashed the old Westell ADSL modem/router as well as my Linksys WRT54G with DD-WRT. I haven’t gotten around to trying uTP yet since I tend to have it turned off in uTorrent by habit.

All in all, I’m really very pleased with this.

UPDATE: Oct. 20 at ~4:00 PM caller ID started working. Now there’s not a thing at all that’s not working properly.

Verizon’s TOS kind of suck

I was looking at the Verizon TOS for some reason today, I suppose to psych myself up further about my forthcoming FiOS installation, and I noticed that there are some ridiculously vague (and therefore massively prohibitive) clauses in the agreement.

For example, according to the FiOS Acceptable Use Policy, customers are not allowed to,

post off-topic information on message boards, chat rooms or social networking sites

generate excessive amounts of email or other Internet traffic

use the service in any fashion for the transmission or dissemination of images containing child pornography or in a manner that is obscene, sexually explicit, cruel or racist in nature or which espouses, promotes or incites bigotry, hatred or racism

I agree with some of the terms of that last one. Specifically, I agree that the customer ought to be required to agree not to use the Service to engage in activities of any nature at all that violate a federal, state or local law (but the customer is already made to agree not to violate the law in a different clause, so the child pornography part should have been covered by that). However, most of those things aren’t illegal. In fact, Verizon specifically states in the same agreement that the customer must agree essentially to not be a prude and blame Verizon if they accidentally come across something on the Internet or via FiOS TV that they find offensive:

You acknowledge that the Service will allow access to information which may be sexually explicit, obscene or offensive, or otherwise unsuitable for children. You agree…that Verizon is not responsible for access by you or any other users to objectionable or offensive content.

So it seems like a clear contradiction, if you ask me. On the one hand, you must acknowledge that the Service gives you access to materials that may be “obscene” to some people (which cannot be legally determined until someone actually asserts that something is “obscene”, since something is not “obscene” until it is subjected to the Miller Test, which cannot be done without a jury). Yet on the other hand, you’re not allowed to transmit “obscene” materials. In fact, the TOS are impossible to agree to, since if I agree that the Service gives me access to obscene materials, I cannot also agree that I will not “transmit” any of the “obscene” materials that the Service is giving me access to.

I think FiOS TV has the Playboy Channel if you pay extra for it. If you had a jury full of puritanical zealots from Evangelicalville, TX then I think there’s a pretty good chance they’d call it “obscene” on all three prongs of the Miller Test. They’d consider “community standards” to refer the community standards of Evangelicalville, TX, so of course it violates those. As for depicting sexual conduct in a “patently offensive” way, they’d almost certainly agree that it does (again, since they can be assumed to be a bunch of prudes). Finally, they would most likely quickly agree that it has no artistic merit. Hell, I think that under that last prong at least, most shotacon would stand a better chance than Playboy.

The “excessive amounts of email or other Internet traffic” thing is also irritating. It’s only irritating though because Verizon has this big sparkly announcement on their FiOS front page about how, unlike their nasty competitors, they don’t throttle their customers.
fios home page
But if they reserve the right to arbitrarily impose bandwidth caps on their customers without prior notification, that’s equivalent, abstractly speaking at least, to what their competitors do. At least it’s with the same intention in mind. It wouldn’t be annoying at all if Verizon would come off their high horse and be honest about it. In fact, I would even respect them quite a bit if they came right out on their TV commercials and said, “We currently offer FTTH with no throttling or bandwidth caps so you should sign up today. Be aware though that if you sign up today, we may introduce a 1GB per month transfer cap tomorrow. Then again, we may not. It’s your gamble”.

I guess the lesson here is that TOS are better left unread. Now I know that not only can I not generate “excessive traffic”, download pornography or watch it on TV, post off-topic messages on forums or message boards, or do anything, “harmful to the…Internet generally or other Internet users”, but I’m also not allowed to

exceed the bandwidth usage limitations that Verizon may establish from time to time for the Service, or use the Service to host any type of server. Violation of this section may result in bandwidth restrictions on your Service or suspension or termination of your Service.

How frightening. If I exceed my bandwidth limit the punishment is the imposition of a bandwidth limit!

In all seriousness though, I can’t fucking wait until the installation is complete. This will be one of the best days of my life.

I thought of doing this myself once

When I went ahead and bought this stupid domain name I considered using fake contact details to prevent spam and also avoid paying for “private” registration (where the domain registrar’s contact details are posted in the whois data instead of the registrant’s). But I used my real email address at least. Anyway, I know it’s common to use the postal address of your company headquarters and some email address such as [email protected] for abuse contact, instead of the actual contact information for the person who registered the domain, but I rarely have seen contact information that can properly be called fake.

In any case, this one was downright silly.
usw-dunderhead
Looking at the details for the organization “DUNDER”…
usw-dunderhead

Also, I can’t believe someone else already had taken “smilecitrus.com”. It must have been one of my various nemeses. If only I had had FiOS back then I’d surely have beaten that scoundrel to the punch.

I am finally getting FiOS

FTTH

FTTH

There is now virtually zero doubt about it. I can say with almost complete certainty that I will have FiOS at some point within the next one to three months.

Verizon has been digging the bejesus out of the building, to use what I find to be a surprisingly charming phrase, making a lot of noise and dust while they’re at it. This is, of course, all perfectly fine with me since it means we will all be getting FiOS in the apartment complex soon. At one point they even screwed up the plumbing and broke something, causing the whole building to smell like sewage for a day or so, until the janitor used some powerful air freshener thing that smelled like some kind of scented candle, which was almost as bad. Tenants received notification in July that they’d begin the wiring work at some point in September and that service should be offered soon after that. I was skeptical about taking that at face value, since the last time any upgrade to the building wiring was done were at least eleven or twelve years ago when the place was wired for Time Warner cable TV and Earthlink cable Internet (the only non-ADSL ISP available here for the entire time; not even Road Runner is available).

Anyway, there’s no need to dwell on the miserable Internet situation of the past anymore; it’s in the past. The future is FTTH! This will be almost as good as living inside a datacenter. Or Korea. I just hope that Verizon doesn’t introduce any bandwidth caps. It seems inconceivable to me that they offer a service like this and don’t either have a bandwidth cap or throttle customers who do more than check email once a week. As far as I understand it, most FTTH providers simply have no choice but to have very low bandwidth caps. I know at least that that’s the norm for most ISPs in Japan. It just seems too good to be true that I could have 5Mbps upstream (or, dare I hope, maybe even more?) and be allowed to actually upload at that rate 24 hours a day, 7 days a week. I can understand why my ISP doesn’t currently care that I upload at 384Kbps 24/7, since that’s probably not even making a dent in their network, but 5Mbps is not small potatoes, as it were.

I’m alarmed because I read someone complaining somewhere the other day about a newly-introduced transfer cap for FiOS in his or her service area. He or she didn’t mention what area that actually was though so it was more frightening than actually informative. It was pretty restrictive though if I remember correctly. I don’t recall the actual number, but I do remember that it was significantly less than 200GB (more than 100GB though). The whole point of FiOS is to upload something like 30GB a day, so a 200GB monthly transfer cap (where both uploads and downloads are counted equally) is complete and utter fail. It more or less defeats the purpose of having a fast connection for the end-user, though I don’t deny that it’s most likely completely rational for the ISP. If I were an FTTP provider, I’d probably also use transfer caps and some insane “network management” techniques to prioritize content that my investors had an interest in.

The fact that it may be rational and understandable, however, doesn’t mean I’d be any less devastated if I were affected by these practices as a customer. Of course, the terms of the contract are not yet available for me to read, since the installation is not yet finished and, as such, I’m not technically even a potential customer yet.

I shouldn’t jinx things though. If I just think positively I know they won’t throttle or cap me. I’ll expect the best. Besides, Verizon says right on their website that they don’t throttle, at least:

Some Internet providers will resort to “throttling,” or slowing down your Internet connection if they decide your usage is too heavy. Verizon doesn’t. FiOS is always blazingly fast.

I really hope they offer the 35Mbps/35Mbps plan to me. It’s not listed on the main Verizon web site though, so I’m a bit concerned that maybe it’s discontinued. If it has been discontinued, then hopefully I can get the 25/25 plan. It’s cheaper than the “best” plan, which is 50/20.

One of the biggest questions about FiOS I’ve had though since I first heard about it has been, “How the hell do they install those ONT things?”. Verizon’s goal is to have every single NYC resident (yes, all five boroughs) eligible to receive FiOS service by 2014. Why they would choose a place where so many people live in apartment buildings was a mystery to me though. It seemed like a bad idea as far as I could tell. How do you do that? Do you just drill a hole in the customer’s wall, thread the line in and then mount the ONT in the poor bastard’s living room? Actually, at least in my case, they have a better method. Since I live underground, they just went ahead and put the ONT on the outisde wall of the building. They did drill a small hole above the door from the outside into the building (not the door to my apartment though) and that’s how the ONT is connected to the inside wiring. I already have a hole in my living room wall for cable TV/Internet so presumably that’s how I’ll get connected to the ONT (otherwise it’ll have to be through the window!).

FiOS ONT NYC

This makes some degree of sense I suppose. While the ONT is, in fact, smaller than I thought it would be, it would still be a pain to have this thing in my living room. Of course, even if I did have to have it in my living room it would be a small price to pay for true FTTH, but with it outside, things are even nicer. The downside is that it’s gonna be damned hard to access the ONT. That grid-looking thing above the ONT in the picture is the fire escape for the apartment one floor above me, so it’s quite high up there. I don’t own a ladder either, so that’ll be annoying. Hopefully I won’t have to mess with it myself. This is definite progress though.