Sunday, December 22, 2013
Sunday, July 21, 2013
Bits Blog: Following Public Dots to a Missing Phone
In retrospect, I should have checked the cab seat when I got out. I should have taken the receipt. And maybe I should have had more empathy for those people, like my daughters, who have lost their smartphones.
Because there I was, at 1 a.m. on a recent night, just back from the airport with a sinking feeling that I’d left my iPhone in the taxi.
No immediate solution appeared, so after a fitful few hours of sleep, I began my quest to find my phone. Along the way, I was reminded, in this time of debate about how much personal information the government secretly keeps about us, just how much information is already publicly available.
My hunt started with a trip to the Apple store to get into my iCloud account (I didn’t know my password) and use the Find My iPhone service that I had turned on for my iPhone. I learned just how critical it is to have the program activated, although there were still several caveats.
A screen shot of the Find My iPhone app showing location of the writer’s iPhone on Thursday.Because of that feature, locating the phone was the easy step. The trick was getting it back.
The tracker showed the phone at a house at the entrance to a cul-de-sac a little east of Queens in Nassau County. But I didn’t have the house number. The police there told me they could assist me if I showed up at the location, but that they wouldn’t go to the house on their own. I needed to talk to someone in that house.
I initially didn’t have much luck searching online for a free reverse directory, and a librarian at a nearby branch would not give out resident information if they could find it in their reverse directories. But Zillow.com, the real estate site, let me identify the house number, which gave me enough information to look up county records. Those told a lot about the property — Colonial, two-family home, built in 1962, 2,150 square feet, last sold in 2004 for $430,00 — but had no owner information. A call to the assessor’s office turned up the homeowner’s name, and the white pages provided the phone number. It went to a generic voicemail.
While I waited for a call back, I searched the Open Data service on NYC.gov for a taxi driver with the resident’s name. One seemed to show up, though the first name started with a different letter. That gave me a taxi license for that driver, though not the coveted medallion number.
To triangulate, I turned to the Taxi and Limousine Commission. I wasn’t expecting much here, since when I called the night before I heard the after-hours recording, which made it clear that the commission has lots of drivers and lots of lost property reports, and that you have to fill out a form online. I got through to a helpful employee who was soon digging into the case. She took the license number and within a couple minutes had the driver on the line. But the person she had on the phone was not the right one — it was a woman, not a man. So the records showing a slightly different first name were indeed accurate.
But there was another option: because I paid with a credit card, the staffer told me, the medallion number of the driver would show up in that transaction. But it hadn’t yet been fully processed and there was no medallion number, according to my online statement and my credit union. But we did have the amount, $36.43, and the pick up and drop-off locations, so the staffer was going to see what she could do.
In the meantime, I called the house again and a man picked up. Though he wasn’t my driver, he said a taxi driver did live there and he gave me a cellphone number.
When I called that number, a man picked up and he said he had my phone. I got his name and medallion number and called the clerk at the taxi commission. She, too, had come up with a medallion number. They matched.
Less than 24 hours since his cab drove off with my phone on the back seat, the driver was outside our apartment again.
It is said that the chances of getting a phone back are not so good after someone hops into the cab you exited. As a tractor-trailer honked behind the cabby and I gave him $30 bucks for the effort and he handed me the phone, he told me we had been his last passengers after that airport run.
So in the end, it helped to have a little bit of luck, and a lot of data, on my side.
Sunday, June 16, 2013
Bits: Facebook Adds Hashtags to Organize Public Conversations
Facebook users will be able to click on a hashtag and see a feed of what other people and users are saying about that event or topic.4:42 p.m. | Updated Added more explanation of how hashtag searching works.
Facebook has joined the hashtag revolution, introducing a tool on Wednesday that allows users to add the # symbol before a word to signify its topic. The topic would then be easily searchable by other users of the social network.
Of course, anyone who has used the microblogging service Twitter is familiar with hashtags, which have long been used there to organize public conversations. Right now, for example, #manofsteel is a popular hashtag on Twitter because of the coming Superman movie. Search for that hashtag on Twitter and you can see the global conversation about the topic.
Tumblr, Pinterest and other social networks also use hashtags, and Google announced last month that it was adding hashtags to its Google Plus service.
In a blog post, Facebook said it, too, wanted to make it easier for its users to participate in a common conversation.
“Every day, hundreds of millions of people use Facebook to share their thoughts on big moments happening all around them. Whether it’s talking about a favorite television show, cheering on a hometown sports team or engaging with friends during a breaking news event — people on Facebook connect with their friends about what’s taking place all over the world,” Greg Lindley, a Facebook product manager, wrote in the blog post. “To bring these conversations more to the forefront, we will be rolling out a series of features that surface some of the interesting discussions people are having about public events, people and topics.”
Starting Wednesday, users can click on a hashtag in Facebook and see a feed of what other people and organizational users are saying about that event or topic.
Facebook said users would also be able to click on hashtags that originated on other services, like Instagram, a photo-sharing service owned by Facebook that already uses the tool. Searching a hashtag will bring up posts with that tag made by friends and other users who have chosen to make their posts public.
The new hashtag service is immediately available to about 20 percent of Facebook users, with the rest getting it gradually over the coming weeks.
The company said it would roll out additional features, including trending hashtags, in the near future.
Monday, June 3, 2013
DealBook: Nasdaq Is Fined $10 Million Over Mishandled Facebook Public Offering
Bebeto Matthews/Associated PressNasdaq said it has put measures in place to prevent problems like the Facebook I.P.O. last May.Nasdaq’s parent company will pay the largest fine ever levied against an exchange for “poor systems and decision making” both before and after the bungled Facebook initial public offering.
In the minutes after Facebook’s initial public offering spun out of control last year, executives at the Nasdaq stock exchange received an e-mail pleading for a pause.
“We are all trading blind,” said the message, which was sent by the chief executive of the trading firm Knight Capital, according to people briefed on the details of the e-mail. “Should you stop trading for some period of time so we can all catch up and actually understand our exposure?”
The confusion on the morning of May 18, 2012, had been caused by errors in Nasdaq’s computer programming, but executives at the exchange decided to ignore the request for a break and proceed with trading, leading to mounting confusion.
The back-and-forth is one of many details to come out on Wednesday when the Securities and Exchange Commission released the results of its investigation into the bungled Facebook I.P.O. The S.E.C. announced that the Nasdaq OMX Group will pay $10 million, the largest fine ever levied against an exchange, to settle accusations that it had violated numerous rules before and after the I.P.O.
The settlement helps Nasdaq put behind it an episode that hurt its reputation and damaged investor confidence in the stock market. But the investigation also suggests that Nasdaq’s shortcomings were, in some ways, much deeper and more widespread than previously understood.
The head of the S.E.C.’s market abuse unit, Daniel M. Hawke, said in a statement that there has been too much of a tendency to write off incidents like the Facebook I.P.O. as “technical ‘glitches.’ ”
“It’s the design of the systems and the response of exchange officials that cause us the most concern,” Mr. Hawke said.
Robert Greifeld, the chief executive of Nasdaq, wrote in an open letter on Wednesday that the company had put new safeguards in place to prevent future problems. But he also defended the company’s overall performance.
“While we prepared extensively for the Facebook initial public offering, including thorough tests of our systems with member firms, the challenges we encountered that day were unprecedented,” Mr. Greifeld wrote.
The mishandled Facebook I.P.O. was among a series of breakdowns that rocked the United States stock markets last year and led to questions about the safety and soundness of an increasingly complex and computer-driven system.
In addition to the $10 million fine, Nasdaq has already agreed to pay $62 million to the brokers who lost money because of the problems. Even that has not been enough to placate the firm that was hurt the most, UBS, which contends that it lost $356 million because of Nasdaq’s errors. UBS has said it plans to seek more money from Nasdaq through arbitration.
The S.E.C.’s findings could aggravate some of the remaining tensions over the Facebook I.P.O. because it reveals numerous and previously unknown ways that the exchange executives fumbled the incident.
The problems began before the I.P.O. when Nasdaq tested its computer programs, but only on 40,000 orders, according to the S.E.C. When it was time to begin actual trading, at 11 a.m. on May 18, the system was overwhelmed by 496,000 orders.
The deluge of orders sent Nasdaq’s computers into a continuous loop that made it impossible to establish a correct opening price for Facebook stock, which had priced at $38 a share the night before.
Nasdaq executives were immediately aware of the problems and summoned a “Code Blue” conference call, but they decided to proceed with the opening after making a few temporary fixes to the computer code and switching to an untested backup system, the S.E.C. found.
Once Facebook started trading at $42 soon after 11:30 a.m., numerous brokers contacted Nasdaq to complain that they still did not know how many shares of Facebook they had purchased. At 1:50 p.m., Nasdaq executives realized they had failed to execute tens of thousands of orders that had been sent in.
At that point, Nasdaq caused more problems by selling many of these shares into the market, leading to a sharp drop in Facebook’s share price. It closed at $38.23 after Facebook’s bankers stepped in to help support the stock. The company’s stock has never risen above its opening price of $42.05 and was trading down 3.2 percent on Wednesday, at $23.32.
The S.E.C. also reported that shortcomings in Nasdaq’s technology hit the stock of game-maker Zynga on the day of the Facebook I.P.O., causing big price swings in Zynga shares.
The S.E.C. said Wednesday that Nasdaq had broken market rules two other separate times. In October 2011 and August 2012, programming errors caused Nasdaq to mistakenly execute some customer orders below the publicly listed price.
Although the settlement could put to rest some of the speculation surrounding the exchange, it does not shine a positive light on Nasdaq and its management, said Patrick Healy, the chief executive of the Issuer Advisory Group, a capital markets consulting firm.
“It sure looks like the guy who couldn’t shoot straight,” Mr. Healy said. “There’s no question that it’s an embarrassment.”