Afni - Scam?

I got a letter in the mail on Saturday from a company named Afni, Inc., a debt collection company. This letter informed me that my debt of $188 to DirecTV was being collected by them. Of course, I've never had any dealings with DirecTV (aside from interviewing for a job there a couple of years ago), so I knew that this was a bogus notice. Come Monday morning, I called their 1-888 number and, after waiting on hold for 20 minutes, was connected to a bored-sounding agent. She asked me for the last four digits of my social security number, verified that the account wasn't mine, and said that they would stop the collection proceedings.

Now, their customer service, it wasn't bad. Once I got off hold, it took less than five minutes for them to realize that I wasn't the nan that they're looking for. But let's just consider this situation for a moment. I moved to this city a month ago, and somehow it seemed possible to them that I was the man who owed DirecTV $188. They obviously have his social security number, since they could verify that I'm not him, but they sent the bill to me anyhow. Did they just blanket-mail all the people in the city with my name, in the hopes that somebody wouldn't notice that it wasn't their bill and would pay? Is this some kind of a scam to associate my name and address with the last 4 of my social so that if I ever do default on a debt they know where to find me? I don't know, but I'm pretty sketched out by it.

The Internet has lots of stories about Afni trying to collect on bogus debts, and from them, it seems that this is a pretty unscrupulous company. I guess I should take it as a sign that I've moved on into the real world that there are people trying to scam me out of my money now...

An iPad in San Francisco

iPad

So, I've been in San Francisco apartment-hunting for the past couple of days (I found a place!), and the only computers I brought with me are my iPad and my iPhone. It occurred to me that this might be a useful basis for a review, so enjoy. As a reminder, I have the 64GB model with 3G and WiFi.

In brief, I am extremely satisfied. I have been using the iPad to browse Craigslist, listen to music, keep up with my e-mail (including a community-l thread that made me long for the upcoming threaded mail view), and so on. It has excelled at all of these tasks, and done so with battery performance that continues to amaze me.

Web browsing is, of course, the iPad's forte. I've tried both craigsphone and CraigsFish for the iPad, and they are both inferior experiences to just using craigslist in the browser. That is because it is awesome in the browser. Speedy to load (a big plus on AT&T in SF), and easy to interact with via touch. It occurs to me that I could have used Prowl to push phone numbers to my iPhone, but I didn't think of that at the time. I really need bidirectional clipboard sharing between iDevices...

Music and other media consumption is also a pleasure on the iPad. Simply having 64G of space means that I can take all of my AAC music (lots is still in FLAC only, but whatever), some TV, and still have lots of space left. Sound quality isn't great, but it is good enough for these purposes. I had crappy headphones all week anyhow.

E-mail is just okay. The client is good for viewing (except for the aforementioned lack of threading, which is coming in 4.0), and only okay for sending. I really want a way to save emails created in other apps (i.e., PaperDesk) as drafts and edit them from the real app. Good enough to be passable, but plenty of room for improvement.

Navigation was an unexpected benefit. The muni information in Google Maps is decent, and Maps in general is much easier to use on the big screen than on the iPhone. No iBART for iPad yet, but BART is simple enough to not really need it.

Blogging is problematic. I've composed most of this post on the iPad (in my hotel room, actually), but can't post it as I want it from here because I can't add any pictures. The web interface has no way to upload from the iPad's photo library, and the native client is super-crashy. I guess I'll have to add the pictures from another computer, later.

However, actually entering text is pretty great. I've gotten quite fast at typing on the landscape keyboard with the iPad on my lap or a table. I can thumb-type pretty well in portrait mode, and am working to get better. Some of the auto corrects are weird, though. It corrects "ive" to "vie" instead of "I've" unless it's the first word in a sentence, and that seems like a much less likely correction. It also misses some fat-fingers that it should be able to get by key proximity (for example, "grt" instead of "get"). However, it's definitely good enough to write a few hundred words on.

What else...? 3G is awesome. I have had dropped calls on my iPhone in SF, but have had great data access everywhere on my iPad. It's only about 600k/s, but fast enough for craigslist and IM. Oh, also, the official AIM app has been super nice. There's really nothing like being able to IM with a good friend while waiting for a real estate agent who is running late for a showing. I know that Beejive and IM+ are supposedly quite good, but I kind of like the official AIM app more. shrug.

San Francisco has been quite a nice city to use it in. I have felt safe using it pretty much everywhere I have been, including on the bus. And people ask about it pretty much everywhere. I think I convinced a woman in the Starbucks on Powell and Sutter to get one. I don't count myself as much of an Apple Fanboy (I like their products objectively, dammit), but I think I did some good iPad evangelization.

So, that's my review. As you might have expected, I'm pretty happy with it. Feel free to leave comments (or tweet @Roguelazer) with questions or thoughts.

Graduated

So, Sunday was my college graduation. I'm now a college graduate. Wow, that's weird to write. If you're curious about we details, I hold a Bacheleor of Science in Computer Science from Harvey Mudd College with overall academic distinction and with departmental honors in two departments. Woo.

It's really weird to be done. I keep expecting that this will just be a break, that things will be back to normal soon. I'd really gotten used to things at Mudd, I was really happy there. Mudders: I already miss you. In retrospect, there are a lot of things that I should have done and didn't, and a lot of things that I did do and should have done more of. And some things, mostly of the work variety, that I could have stood to do less of. But it was still an awesome time at a great school. Rating: A+++, would study again.

You may ask what I'm doing now. Well, I'll be starting work at Yelp in a couple of weeks. For the time being, I'm hanging out in LA (technically, Calabasas) mooching off of some relatives. It's nice and relaxing but, well, it's not Mudd. I suppose I shouldn't expect that it would be... If anybody is in the area and wants to say hi in the next couple of weeks, let me know. I'll probably be in San Francisco for a couple of days soon to look at apartments. Still trying to sort that out.

By the way, this post was written on my iPad using the software keyboard and Mobile Safari. It's pretty cool.

iPad!

iPad 3G Unboxing

The universe smiles on me today: on the day that I finish all of my work for my undergraduate degree, my new iPad 3G appears. It's currently doing its initial sync (photo "optimization" takes ruddy forever, and I'm only synchronizing 3000 photos). For the time being, here are my unboxing photos.

dnsextd, TCP, and IPv6

Hello interested parties. dnsextd (in my git repository) now supports TCP. It was actually sort of an amusing bug. I guess the dnsextd code must date back to PowerPC, because it had an extra ntoh call which on little-endian systems would cause TCP requests to fail. It's fixed in the "tcp" branch of my git repository. In case you're curious as to how to get that repository, you would use the following:

% git clone //files.roguelazer.com/projects/mDNSResponder-214.git
% cd mDNSResponder-214
% git branch --track tcp origin/tcp
% git checkout tcp

If you need more setup help, Dynamic DNS: Part Two contains all the gory details. If you decide to use mDNSResponder-215 and want to apply the patches, here's a patch you can apply on top of the one from the linked post to add TCP support: dnsextd_posix-215-tcp.patch.

With TCP support comes (sorta) something useful: IPv6 support. dnsextd itself isn't well-designed to handle IPv6, since it'd be a really obnoxious refitting job to get it to listen on those other sockets and understand sockaddr_in6's and what have you. However, DNS-over-TCP can support IPv6 with the following very simple command line:

sudo nc6 -6 --continuous -lp 53 --exec "nc6 -4 localhost 53"

Is it as good a solution as actually listening on IPv6? No. Does it incur the penalty of spawning a new process on every single connection? Yes. Is it good enough for me to be happy with for playing with? Also yes. :-)

As usual, feel free to comment below or e-mail if you have any questions or concerns. Cheers.

wamupd-0.1.1

So, some news on the wamupd front. I just released version 0.1.1 (tagged as such in git; also available as a tarball at //files.roguelazer.com/projects/wamupd/wamupd-0.1.1.tar.bz2) which has a lot of new features over the prior, unnamed release.

  • wamupd now stays resident, renewing leases and such
  • It can talk to Avahi over D-BUS and pick up other services registered on the computer (sort of; it's kind of hack-ish)
  • Lots and lots and lots and lots of bug fixes

I've got ideas for the next few releases (still looking into xdg, making this behave like a real daemon, and maybe setting up a Rakefile to build a gem). Exciting times!

Sorry for the brevity of this post, but, well, coding is more interesting than writing, I'm afraid. Feel free to e-mail me or leave a comment here if there are any questions or requests you have about wamupd.

Dynamic DNS: Part Two

This post is a follow-up to Dynamic DNS

Bonjour logo

When last I left you, we had basic updateable DNS running and could update it from OS X. I've been a bit busy since then, but thanks to some prodding from @Loredo, I got back in and started looking at. What follows is the exciting story of how I got things up and running — by the end of this post, you'll have access to a working copy of dnsextd for linux, and a client application that updates SRV and IP (A/AAAA) leases. Woo.

read more

iPad Reactions

iPad

So, yesterday was the big day. The Coming of The Tablet. I'm not exactly a big tech pundit. I've never seen an iPad in person. I haven't even played with the emulator yet. But I thought I'd still post my immediate reactions.

The Name: It's not that bad. It doesn't trigger the same juvenile "feminine products" joke urge in me that that it does with all of the commentators on Slashdot. It kind of reminds me of PADDs from Star Trek, which is a good association for a high-tech device. It's better than "iSlate" would've been. I think "Apple Tablet" would've been better, but I don't know that it'd be trademarkable. Not that "iPad" is exactly easy from a trademark standpoint...

The Hardware: Looks gorgeous. ARM Cortex-A9, which is about what I figured. For you people that have never designed an ARM before: that doesn't mean that ARM designed the chip and Apple/PA Semi just slapped their design down. Given Apple's propensity for attention to detail, I'm sure they didn't just use the synthesizable core from ARM and put it in an SoC — I'm sure that they took the architectural/micro-architectural IP and built their own chip.

The non-ultranerd parts of the hardware look nice, too. People online are complaining about the bezel, but I think it looks about right. John Gruber agrees. The screen isn't OLED, but I have a Sony NWZ-X1061, and I can personally attest that the screen technology is not useful in bright light. OLEDs now are where LCDs were 10 years ago — completely transmissive (well, actually emissive in this case, but it's the same idea). Somebody somewhere will come up with a way to make transflective OLEDs like they did for LCDs, and then we'll have reasonably usable OLEDs. Then the price can come down about 90%, and Apple can put one on an iPad. Until then, a big IPS LED-backlit LCD is the way to go.

The Software Ecosystem: This is the biggest point of contention. It's true: Apple is deploying another closed ecosystem. Like the iPhone, this product will not encourage tinkering. I'm sure somebody will jailbreak it. I'm equally sure that it won't matter. I have a few different responses to this issue:

  1. It's as open as the web. Yes, you can't run native code on it without getting it through a barrage of Apple testers. You have a first-class web browser which seems to be much better at handling multiple open pages than Mobile Safari on the iPhone is. I see this as no different than WebOS or ChromeOS. Apple has no problem making useful APIs available through the browser (like Geolocation). Hell, with things like Bespin, you can even do development through the web.
  2. The iPad isn't going to replace tinkerer's computers. If I could move my parents away from full computers to iPads today, I'd do it. The safety of a managed platform far outweighs anything else, given how much important stuff people are putting on their computers nowadays and how dumb most people using computers are. Yes, I've heard the argument that without being able to tinker with the inner workings of your OS, you can't grow up to be a proper hacker. Well, I never really tinkered with the inner workings of my OS until I was old enough to buy an old desktop and put Red Hat 5.1 on it. That ability won't be going away.
  3. It doesn't matter what I (or anybody else reading this blog post, probably) think. The 3 million people that will buy iPads this year (my personal guess) don't give a crap whether or not you can deploy unsigned applications to it.

The Audience: This is going to be big. Not as big as the iPhone (at least, not right out the gate). But big. It kicks the crap out of Chrome OS and netbooks in general (the idea of a cheap netbook-level device with decent industrial design and fabrication is amazing). I'm going to want one. And you're going to want one, too.

SpamAssassin 2010 Bug

Hey all. One of the sysadmins at Mudd, Claire Connelly, pointed out that there's a widespread bug in SpamAssassin that might cause large numbers of false positives on mail sent after 2010-01-01. Apparently, the "date in future" rule is hardcoded to look for years after 2010. You can read more at LWN; the short of it is that you probably want to add the following to your SpamAssassin config:

score FH_DATE_PAST_20XX 0.0

sa-update may or may not be pulling down updated rules. You can find the relevant bug at the SpamAssassin Bugzilla (#5852). Anyhow, something fun to be aware of.

Happy 2010.