Language Selection

English French German Italian Portuguese Spanish

Judge Sets Hearing Date In Google, DOJ Case

Filed under
Legal

A federal judge has scheduled for next month a hearing on Google Inc.'s refusal to hand over information on search results to the Department of Justice, which is looking for evidence to bolster its attempt to revive an anti-porn law rejected by the U.S. Supreme Court.

U.S. District Judge James Ware in San Jose, Calif., set the hearing for Feb. 27. He also gave Google until Feb. 6 to file its reasons for refusing to comply with the DOJ subpoena. The Justice Department has until Feb. 13 to file a response.

Yahoo Inc., Microsoft Corp.'s MSN and America Online Inc., a division of Time Warner Inc., complied with similar subpoenas received from the Justice Department. Google refused, saying the "demand for information overreaches."

Full Story.

In other Google news:

Though it was overshadowed last week by news that Google is going to censor its Chinese search engine and protect the privacy of pedophiles in the United States, another bit of Googlish news caught my eye: The company is funding a big, new academic effort at Harvard and Cambridge to combat spyware and adware, which the new organization has decided to call "badware." Read about it at the new Web site, stopbadware.org.

That Full Story.

More in Tux Machines

today's howtos

GNOME: Mutter, gresg, and GTK

  • Mutter 3.25.2 Has Bug Fixes, Some Performance Work
    Florian Müllner has pushed out an updated Mutter 3.25.2 window manager / compositor release in time for the GNOME 3.25.2 milestone in the road to this September's GNOME 3.26 release. Mutter 3.25.2 has a number of fixes ranging from fixing frame updates in certain scenarios, accessible screen coordinates on X11, some build issues, and more.
  • gresg – an XML resources generator
    For me, create GTK+ custom widgets is a very common task. Using templates for them, too.
  • Free Ideas for UI Frameworks, or How To Achieve Polished UI
    Ever since the original iPhone came out, I’ve had several ideas about how they managed to achieve such fluidity with relatively mediocre hardware. I mean, it was good at the time, but Android still struggles on hardware that makes that look like a 486… It’s absolutely my fault that none of these have been implemented in any open-source framework I’m aware of, so instead of sitting on these ideas and trotting them out at the pub every few months as we reminisce over what could have been, I’m writing about them here. I’m hoping that either someone takes them and runs with them, or that they get thoroughly debunked and I’m made to look like an idiot. The third option is of course that they’re ignored, which I think would be a shame, but given I’ve not managed to get the opportunity to implement them over the last decade, that would hardly be surprising. I feel I should clarify that these aren’t all my ideas, but include a mix of observation of and conjecture about contemporary software. This somewhat follows on from the post I made 6 years ago(!) So let’s begin.

Distro News: Alpine, Devuan, and openSUSE

OSS Leftovers